- Home
- Resources
- Integrations
- Felt Maps
Claude Felt Maps connectorWhat Claude can do in your Felt Maps account.
The Claude Felt Maps connector exposes 34 tools: 15 read, 16 write and 3 undocumented. Claude explores your maps and databases, builds and styles layers, annotates, shares or deletes. On Felt's side, a specific subscription is required. Here is what that changes.
Verified Trustpilot reviews · AI, automation & growth agency
What the Claude Felt Maps connector changes
Building an analysis map usually means writing spatial SQL, importing layers and tuning their style by hand. With the connector, you describe the map you want to Claude: it queries your connected databases, builds the layers, styles them and hands back a link, when you ask.
Go from a question to a map. Ask where your customers cluster: Claude reads the table structure with inspect_data_source_table_columns, builds the layer through create_layer_from_data_source and styles it using generate_fsl and then update_layer_properties.
Add context. Claude pulls administrative boundaries or demographics found via browse_felt_library, then brings in a public service with import_layer_from_url.
Deliver the map. Claude drops pins with upsert_annotations and sets view-only access through share_map before giving you the link.
What it will not do with this sheet: bulk-edit features with SQL or rework a layer's columns. Felt documents those tools, but they are not on the sheet. Nothing fires on its own either: Claude only acts while it answers you. Other platforms covered on the site sit on the Integrations hub. It does not read anything outside the workspace either: the databases it queries are the ones connected to Felt.
Five words before you connect
The Claude vocabulary around this connector, in a minute.
- Connector
- The link you set up once between Claude and a service you already use, so Claude can work with it while it answers you.
- Tool
- One named capability the connector opens to Claude. Claude picks which ones to call on its own, and the directory sheet lists them.
- Authorization
- Felt's own sign-in screen, where you hand Claude the access it will use afterwards. Granted once per person, and revocable.
- Approval
- The confirmation Claude waits for before an action that changes an account, shown right in the conversation when it matters.
- MCP
- The shared standard connectors are built on. It is what lets an assistant like Claude talk to an outside service such as Felt.
Connect Felt Maps to Claude in three steps
- 01
Find it in your connectors
Open Claude's settings, go to Customize, then Connectors, and look for Felt Maps. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it before members can sign in individually.
- 02
Start the connection
Click Connect on its row and sign in through the window Felt opens itself. If the link ever breaks, use Disconnect and connect again: that is the documented fix.
- 03
Read the authorization screen
Go through Felt's authorization screen before you approve it. The service decides what the access covers, not Claude. You can also revoke that access later from your Felt account.
The 34 tools, sorted by what they do
Felt Maps gives Claude 34 tools: 15 that read your account, 16 that change something in it, and 3 no official source describes.
Thirty-one tools are described in Felt's published reference; three are not. Names stay exactly as Claude shows them.
- 15 read
- 16 write
- 3 not documented
Tools index
What Claude reads (15)
15 toolsFifteen tools that read your maps, layers and databases without changing anything.
who_am_i
Tells Claude which user is signed in and which Felt workspace they belong to.
get_map
Returns a map's metadata: title, location, basemap and layer count.
list_maps
Lists the maps you can access, most recently visited first, with a fuzzy filter on the title. Claude can narrow the list down from a partial title or a keyword you remember.
get_map_layers
Lists a map's layers grouped by layer group, with names, IDs, visibility and geometry types. Think of it as a map's table of contents.
get_layer_properties
Returns a layer's name, caption, geometry type and style. Felt suggests checking it before touching any styling. Claude can then explain the current styling in plain words.
poll_layer_processing_status
Waits for a layer to finish processing and reports its state: processing, completed or failed, with a configurable maximum wait of 5, 10 or 30 seconds.
browse_data_source_tables
Lists the tables and saved queries inside a database connected to the Felt workspace, without their column schemas.
inspect_data_source_table_columns
Gives the column names and types of one table in a connected database.
get_tabular_data_from_data_source
Runs a read-only SELECT against a connected database and returns a table of results, without drawing anything on the map. Claude can then summarize the figures in plain language.
get_sql_guidance
Loads the SQL dialect rules for a data source or set of layers before Claude drafts its query. The right dialect is picked automatically. It saves Claude from guessing at syntax differences between engines.
generate_fsl
Produces Felt Style Language JSON for a layer, ready for review: colors, classes, labels, popups, filters and icons. Given a layer ID, it inspects the data to pick a fitting style. It does not apply the style itself.
browse_felt_library
Lists data in Felt's public library (boundaries, demographics, infrastructure and more) that can be added to maps.
list_annotations
Returns the editable annotations on a map: places, rectangles, circles, text, notes, links and lines. Other types drawn in the interface are left out.
list_projects
Lists every project in the Felt workspace.
get_project
Returns a project's details, including the maps it contains.
What Claude creates, edits or deletes (16)
16 toolsSixteen tools that touch your maps, layers and annotations. No source describes their confirmation, so the general rule below applies.
create_map
Approval: see the ruleCreates a new map in your Felt workspace, optionally with a title, basemap style, center point and zoom level.
update_map
Approval: see the ruleChanges a map's title, basemap style, zoom level or whether basemap labels show.
delete_map
Approval: see the ruleDeletes a map from your Felt workspace. Everything on that map goes with it, so Claude should name the map clearly before you approve.
share_map
Approval: see the ruleSets a map's public access level (private, view only, view and comment, or view, comment and edit) and returns its share link.
update_layer_properties
Approval: see the ruleChanges a layer's name, caption or style. Only the fields supplied change; the rest stays as it was.
delete_layer
Approval: see the ruleRemoves a layer from a map.
duplicate_layer_to_map
Approval: see the ruleCopies a layer or layer group onto a map, from the same map, the Felt library, a Felt Server layer or another map.
upload_contents_to_map
Approval: see the ruleAdds inline text content (CSV, TSV, GeoJSON, KML, GPX) to a map as a new layer, or refreshes an uploaded one, with no separate file upload. Felt says it suits small data.
prepare_file_upload
Approval: see the ruleGets an upload slot for adding a local file to a map as a new layer, or for refreshing a file-backed layer in place.
import_layer_from_url
Approval: see the ruleAdds a layer to a map by fetching data from a URL. Felt lists ArcGIS services, WMS, GeoJSON and Shapefiles among supported formats.
refresh_url_layer
Approval: see the ruleFetches a URL-backed layer's source again to pick up the latest data. Processing happens asynchronously.
add_data_source_table_to_map
Approval: see the ruleAdds an entire table from a connected database to a map as a new layer.
create_layer_from_data_source
Approval: see the ruleCreates a layer from a SQL query against a connected database. The query must return a geometry column.
refresh_data_source_layer
Approval: see the ruleReruns a database-backed layer's query, or rereads its table, to pick up the latest data. Processing happens asynchronously.
upsert_annotations
Approval: see the ruleCreates or updates annotations on a map: leave out the ID to create one, include it to edit an existing annotation in place.
delete_annotation
Approval: see the ruleDeletes a single annotation from a map.
Undocumented (3)
3 toolsThree tools the sheet lists but no official source describes: whether they read or change anything is unknown.
inspect_layer_columns
This tool is on the directory sheet, but Felt's tool reference does not list it under that name and no other source describes it. This page therefore assigns it no effect. The general rule in the approvals section covers it.
browse_data_sources
No official source describes this tool: the sheet only publishes its name, and Felt's documentation has no entry that matches it exactly. Without a description, its role is not guessed here. The general approvals rule is what applies. No action is attributed to it.
browse_workspace_library
Listed on the directory sheet, this tool has no description in the Felt documentation that was read, or anywhere else. What it actually does is unknown, and this page leaves that gap open. For any action, the general approvals rule holds.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you.
For the sixteen tools that create, edit, share or delete, no source describes a dedicated confirmation, so the default rule covers them. On Team and Enterprise, owners decide whether members can let certain actions through without being asked again, and they can restrict the connector for the whole organization. Felt adds that permissions come from your workspace, so whatever Claude produces is shared under the access controls you already have.
Which plans include it
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. It is a real gap in the catalog.
What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization before members connect. For this one's current status, check its sheet in the official directory. Worth knowing: only Felt documents this connector, and no Claude help article covers it.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, and no layer refreshes by itself when your database changes.
Felt's reference and the directory sheet do not list exactly the same tools: three names on the sheet have no description, and Felt documents tools that are not on the sheet. The directory badge is not a security audit, and Anthropic notes that it does not vouch for how a publisher's tools behave. Among them is a bulk feature-editing tool that, per Felt, offers no undo; it is not on the connector's sheet.
Which Claude plans can use the Felt Maps connector?
- Claude Help Center, general connector rule ↗2026-09-18Web connectors are open to all users on Claude, Cowork, Claude Desktop and mobile; on Team and Enterprise, an Owner or Primary Owner enables them first.
- Felt documentation ↗undated, read 2026-10-01Connectors require a Claude Free, Pro, Max, Team, or Enterprise plan; on Team and Enterprise, an Owner may need to enable the connector first.
What this page followsThe two texts point the same way, but Felt's sentence comes from the publisher and carries no date. Neither settles it for your account: check the directory sheet on your own account. And do not confuse this with the subscription Felt requires on its side, which is a separate condition.
Need help connecting Felt Maps to Claude?
A person reads every message.