Felt for AI agents
Felt is a modern GIS platform for creating, editing, and sharing interactive maps, used across teams that need geographic collaboration. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Felt.
Add a location to a map
Create a new map element marking a location once a team member confirms its coordinates.
Check a map's layers
List the layers on a map to confirm which data sources are currently shown.
Confirm before deleting a map
Require approval before deleting a map, since it removes every layer and element built on it.
15 Felt actions, graded by risk.
Every Felt action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
7Look things up. Allowed by default.
- felt.list_layersList Layers
- felt.list_sourcesList Sources
- felt.list_elementsList Elements
- felt.list_projectsList Projects
- felt.get_map_detailsGet Map Details
- felt.get_user_detailsGet User Details
- felt.list_element_groupsList Element Groups
write
4Create and change things. Allow, or ask the user first.
- felt.create_projectCreate Project
- felt.update_projectUpdate Project
- felt.create_or_update_elementsCreate or Update Elements
- felt.duplicate_mapDuplicate Map
destructive
4Delete, cancel or archive. Ask first, or deny outright.
- felt.delete_mapDelete Map
- felt.delete_layerDelete Layer
- felt.delete_elementDelete Element
- felt.delete_projectDelete Project
Felt in three steps.
- 01Your users connect FeltThey add their Felt api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Project” can wait for the user, and “delete Map” can be denied outright.
- 03Any agent can actYour agent calls Felt through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('felt', { read: 'allow', write: 'ask', // create_project destructive: 'deny', // delete_map }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Felt connects.
Users add their Felt api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Felt connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Felt from any agent.
Felt and Arc0, answered.
Can I use Felt with Claude, ChatGPT or Cursor?
Yes. Connect Felt to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Felt actions you allow.
How do users connect Felt?
Users add their Felt api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Felt actions can my agent take?
15 in total: 7 read, 4 write and 4 destructive, such as “create Project”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Felt?
Yes. Actions like “delete Map” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Felt too?
Yes. The same Felt connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Felt into your agent.
Your users connect Felt once, under your brand. Your agent gets 15 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan