Resources · Claude connector

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

Overview

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.

Vocabulary

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

Connect Felt Maps to Claude in three steps

  1. 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.

  2. 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.

  3. 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.

Tools

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

What Claude reads (15)

15 tools

Fifteen 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.

When it helps
you have several Felt workspaces and want to be sure Claude is looking at the right one, before asking it to look for a map or a dataset.

Sourcehelp.felt.com · October 1, 2026 ↗

get_map

Returns a map's metadata: title, location, basemap and layer count.

When it helps
you want to know what a map a colleague shared is made of before you build on it, including its basemap and how many layers it already holds.

Sourcehelp.felt.com · October 1, 2026 ↗

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.

When it helps
you are hunting for the flood zone map made in the spring but cannot recall its exact name.

Sourcehelp.felt.com · October 1, 2026 ↗

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.

When it helps
before asking for an analysis, you want to see which layers the map really contains.

Sourcehelp.felt.com · October 1, 2026 ↗

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.

When it helps
you want to understand why a layer renders in bright red before asking for another palette.

Sourcehelp.felt.com · October 1, 2026 ↗

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.

When it helps
after a heavy import, Claude checks the layer is ready before carrying on.

Sourcehelp.felt.com · October 1, 2026 ↗

browse_data_source_tables

Lists the tables and saved queries inside a database connected to the Felt workspace, without their column schemas.

When it helps
you want to know which warehouse tables could feed a map, including the saved queries your team already wrote.

Sourcehelp.felt.com · October 1, 2026 ↗

inspect_data_source_table_columns

Gives the column names and types of one table in a connected database.

When it helps
before a spatial query, Claude checks that a table actually has a geometry column, and which column holds the geometry, before a layer is built from it.

Sourcehelp.felt.com · October 1, 2026 ↗

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.

When it helps
a city planner wants building permits counted by district before mapping anything at all.

Sourcehelp.felt.com · October 1, 2026 ↗

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.

When it helps
your database runs on an engine that needs a particular syntax.

Sourcehelp.felt.com · October 1, 2026 ↗

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.

When it helps
you want a readable heatmap of store locations without crafting any style by hand.

Sourcehelp.felt.com · October 1, 2026 ↗

browse_felt_library

Lists data in Felt's public library (boundaries, demographics, infrastructure and more) that can be added to maps.

When it helps
you need county boundaries to put your customer locations in context, boundaries or demographics included, without hunting for an outside file.

Sourcehelp.felt.com · October 1, 2026 ↗

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.

When it helps
you want to review every note left on a field survey map, before the map goes to the client.

Sourcehelp.felt.com · October 1, 2026 ↗

list_projects

Lists every project in the Felt workspace.

When it helps
you just joined a team and want an overview of its mapping projects, to see which maps live in which project before opening any of them, all from one list.

Sourcehelp.felt.com · October 1, 2026 ↗

get_project

Returns a project's details, including the maps it contains.

When it helps
you want all the maps from the city's mobility study project gathered in one answer, without searching map by map when you already know the exact project name.

Sourcehelp.felt.com · October 1, 2026 ↗

What Claude creates, edits or deletes (16)

16 tools

Sixteen tools that touch your maps, layers and annotations. No source describes their confirmation, so the general rule below applies.

create_map

Approval: see the rule

Creates a new map in your Felt workspace, optionally with a title, basemap style, center point and zoom level.

What Claude asks for
no source describes a confirmation specific to creating a map, so the general approval rule covers it.
When it helps
an analyst wants a blank map centered on her region to kick off a study.

Sourcehelp.felt.com · October 1, 2026 ↗

update_map

Approval: see the rule

Changes a map's title, basemap style, zoom level or whether basemap labels show.

What Claude asks for
nothing specific is documented for this setting; the default rule is what applies.
When it helps
you want to rename a map and switch to a dark basemap before a presentation.

Sourcehelp.felt.com · October 1, 2026 ↗

delete_map

Approval: see the rule

Deletes a map from your Felt workspace. Everything on that map goes with it, so Claude should name the map clearly before you approve.

What Claude asks for
the source describes no dedicated check for deletion; the general rule applies, so read the map name carefully.
When it helps
you are clearing out draft maps nobody uses anymore.

Sourcehelp.felt.com · October 1, 2026 ↗

share_map

Approval: see the rule

Sets a map's public access level (private, view only, view and comment, or view, comment and edit) and returns its share link.

What Claude asks for
no dedicated step is described for sharing; rely on the general rule and check the access level.
When it helps
you want to send a client a view-only map without letting them edit it.

Sourcehelp.felt.com · October 1, 2026 ↗

update_layer_properties

Approval: see the rule

Changes a layer's name, caption or style. Only the fields supplied change; the rest stays as it was.

What Claude asks for
Felt documents no confirmation for this style change; the default rule covers the action.
When it helps
you want to apply the style Claude just generated to a layer.

Sourcehelp.felt.com · October 1, 2026 ↗

delete_layer

Approval: see the rule

Removes a layer from a map.

What Claude asks for
no dedicated check is described for removing a layer; the general rule from the approvals section applies.
When it helps
a test layer is still sitting on the final map and has to go before it is shared.

Sourcehelp.felt.com · October 1, 2026 ↗

duplicate_layer_to_map

Approval: see the rule

Copies a layer or layer group onto a map, from the same map, the Felt library, a Felt Server layer or another map.

What Claude asks for
copying a layer has no documented confirmation; the general rule is what applies here.
When it helps
you want to reuse the sales territories layer in a new map.

Sourcehelp.felt.com · October 1, 2026 ↗

upload_contents_to_map

Approval: see the rule

Adds 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.

What Claude asks for
no source spells out a request specific to adding this content; the default rule applies.
When it helps
Claude produced a short list of coordinates and you want to see them on the map.

Sourcehelp.felt.com · October 1, 2026 ↗

prepare_file_upload

Approval: see the rule

Gets an upload slot for adding a local file to a map as a new layer, or for refreshing a file-backed layer in place.

What Claude asks for
the upload slot has no described confirmation; the general approval rule covers it.
When it helps
you want to load a parcel file too large to pass as text.

Sourcehelp.felt.com · October 1, 2026 ↗

import_layer_from_url

Approval: see the rule

Adds a layer to a map by fetching data from a URL. Felt lists ArcGIS services, WMS, GeoJSON and Shapefiles among supported formats.

What Claude asks for
no dedicated check is described for importing from a URL; the general rule holds.
When it helps
a public agency publishes transit data online and you want it on your map.

Sourcehelp.felt.com · October 1, 2026 ↗

refresh_url_layer

Approval: see the rule

Fetches a URL-backed layer's source again to pick up the latest data. Processing happens asynchronously.

What Claude asks for
refreshing a web layer has no rule of its own on record; the default rule applies.
When it helps
the public source was updated and your map has to reflect the new numbers.

Sourcehelp.felt.com · October 1, 2026 ↗

add_data_source_table_to_map

Approval: see the rule

Adds an entire table from a connected database to a map as a new layer.

What Claude asks for
adding a whole table has no described confirmation; rely on the general rule.
When it helps
you want every warehouse location stored in the company data warehouse on the map.

Sourcehelp.felt.com · October 1, 2026 ↗

create_layer_from_data_source

Approval: see the rule

Creates a layer from a SQL query against a connected database. The query must return a geometry column.

What Claude asks for
the source documents nothing specific to building from a query; the general rule applies.
When it helps
you only want stores opened in the last two years, filtered right in the database.

Sourcehelp.felt.com · October 1, 2026 ↗

refresh_data_source_layer

Approval: see the rule

Reruns a database-backed layer's query, or rereads its table, to pick up the latest data. Processing happens asynchronously.

What Claude asks for
rerunning a layer's query has no documented confirmation; the default rule covers the action.
When it helps
sales figures moved in the database and Monday's map needs to follow.

Sourcehelp.felt.com · October 1, 2026 ↗

upsert_annotations

Approval: see the rule

Creates or updates annotations on a map: leave out the ID to create one, include it to edit an existing annotation in place.

What Claude asks for
no dedicated request is described for placing or editing an annotation; the general rule applies.
When it helps
you want Claude to drop pins on the three shortlisted sites for a site visit.

Sourcehelp.felt.com · October 1, 2026 ↗

delete_annotation

Approval: see the rule

Deletes a single annotation from a map.

What Claude asks for
removing an annotation has no documented check; the general rule from the approvals section holds.
When it helps
a working note must not show up on the version shared with the client.

Sourcehelp.felt.com · October 1, 2026 ↗

Undocumented (3)

3 tools

Three 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.

Approvals

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.

Plans

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.

Limits

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.

Two official sources disagree

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

Need help connecting Felt Maps to Claude?

A person reads every message.

FAQ

Claude Felt Maps connector FAQ

01What can Claude do with the Felt Maps connector?
Claude can build and maintain Felt maps while it answers you. On the read side, it browses your projects, maps, layers and annotations, explores connected databases and runs read-only queries. On the write side, it creates, renames, shares or deletes maps, adds layers from a database, a URL, a file or the Felt library, styles them and manages annotations. Three tools on the sheet remain undocumented, so the page assigns them nothing.
02Can Claude delete or share my Felt maps?
Yes. Three tools delete a map, a layer or an annotation, and share_map sets a map's public access, from private all the way to view, comment and edit, then returns the link. No source describes a confirmation specific to these tools, so the default rule applies: Claude asks before each action. Take a moment to check the proposed sharing level before you accept it. Deleting a map, a layer or an annotation removes it from your Felt workspace.
03Does Claude ask before it changes a map?
By default, yes: Claude asks for confirmation before each action it takes on an account on your behalf. No source describes a rule specific to Felt's sixteen write tools, so that default covers creating, styling, importing, sharing and deleting. On Team and Enterprise, owners decide whether members can let some actions through, and they can shut off writing for everyone. For deletions and public sharing, reading each request is worth the few seconds.
04Which Claude plans include the Felt Maps connector?
No official source publishes plan availability for a specific connector, and none of the 819 directory sheets displays it. The general rule is that remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, with an Owner or Primary Owner enabling the connector first on Team and Enterprise. Only the connector's directory sheet shows its current status for your account, so that is the place to check before relying on it. Any change in availability would show up there first.
05Can Claude see my team's entire Felt workspace?
Claude works with your permissions and nothing more. Felt says permissions are inherited from your workspace: Claude only sees the maps and projects you can open, and whatever it produces is shared under the access you already have. For connected databases, it only queries sources linked to the workspace, and the tabular query tool is read-only. Per the directory sheet, those sources can include Databricks, Snowflake, BigQuery, PostgreSQL and S3.
06Why are the Felt tools unavailable in Claude?
The cause Felt documents is the subscription on your side. Felt reserves this feature for certain customers and asks you to get in touch for access. Without it, a connected agent can only answer questions from Felt's documentation, and every other tool stays unavailable. So check your Felt subscription first, before looking for a connection problem on Claude's side. Felt adds that, once access is in place, you click Connect in Claude's directory and complete the OAuth login in your browser.
07Claude or an automation tool for Felt?
They do different jobs, so it depends on the use case. Claude fits when you explore a spatial question in conversation and want a map built and styled from your data, then adjusted as you go. An automation tool fits when a layer has to refresh on its own according to a fixed rule. This connector never fires by itself: it acts while Claude is answering you. Many teams use Claude to explore and an automation tool for routine refreshes.