Mapulus for AI agents
Mapulus lets teams create and analyze interactive maps, pulling location data into other applications and workflows without building custom mapping infrastructure. 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 Mapulus.
Look up a map's details
Pull a map's configuration and layers before embedding it elsewhere, a read-only check on its current setup.
Find a location by external ID
Look up a specific location record using an external identifier to sync data.
List available maps
List the maps in a workspace to find the right one for a project, read-only.
3 Mapulus actions, graded by risk.
Every Mapulus action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
3Look things up. Allowed by default.
- mapulus.list_mapsList Maps
- mapulus.get_map_detailsGet Map Details
- mapulus.find_location_with_external_idFind Location by External ID
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Mapulus in three steps.
- 01Your users connect MapulusThey add their Mapulus api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Mapulus through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('mapulus', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Mapulus connects.
Users add their Mapulus 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 Mapulus 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 Mapulus from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Mapulus and Arc0, answered.
Can I use Mapulus with Claude, ChatGPT or Cursor?
Yes. Connect Mapulus 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 Mapulus actions you allow.
How do users connect Mapulus?
Users add their Mapulus 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 Mapulus actions can my agent take?
3 in total: 3 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Mapulus?
Yes. Allow read actions and deny writes in the Mapulus policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Mapulus too?
Yes. The same Mapulus connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Mapulus into your agent.
Your users connect Mapulus once, under your brand. Your agent gets 3 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan