# Use MapMap from any AI assistant

MapMap's hosted [MCP server](/docs/mcp) speaks streamable HTTP at
`https://mcp.mapmap.ai/mcp` — no key needed to connect, fair use applies.
That one URL is the integration for nearly every assistant and agent
platform in 2026. This page is the recipe book: the exact steps for each
surface, in the order people ask for them.

Everything here works today. Where a surface needs a paid tier or an
admin setting, the recipe says so plainly.

## ChatGPT

ChatGPT connects to remote MCP servers through **developer mode**
(Plus/Pro/Business/Enterprise):

1. Settings → **Apps & Connectors** → **Advanced** → enable **Developer
   mode**.
2. **Create** a connector: name it `MapMap`, URL
   `https://mcp.mapmap.ai/mcp`, authentication **None**.
3. In a chat, enable the MapMap connector and ask:
   *"Route a 4.2 m tall truck from Bristol to Leeds and tell me which
   restrictions applied."*

Business/Enterprise admins can publish the connector workspace-wide, so a
whole ops team gets truck routing in ChatGPT at once.

Anonymous connections run under fair use. To bill calls to your own
account instead — and to lift the limits — [get a free key](/signup?src=chatgpt)
and send it as `Authorization: Bearer snk_…` where your client supports
custom headers, or use the API directly from a Custom GPT action.

## Claude

**Claude Code** (terminal or IDE):

```bash
claude mcp add --transport http mapmap https://mcp.mapmap.ai/mcp
```

Or install the full plugin — MCP tools plus ten
[agent skills](/docs/skills) (truck/ADR know-how, web SDK, map design,
fleet VRP, Mapbox/Google migration):

```bash
claude plugin marketplace add Mapmapai/mapmap-agent-skills
claude plugin install mapmap@mapmap
```

**Claude Desktop / claude.ai**: Settings → Connectors → **Add custom
connector** → `https://mcp.mapmap.ai/mcp`. Once added, it also works from
Claude in Slack and on mobile.

## Cursor

[**Add to Cursor**](cursor://anysphere.cursor-deeplink/mcp/install?name=mapmap&config=eyJ1cmwiOiAiaHR0cHM6Ly9tY3AubWFwbWFwLmFpL21jcCJ9) — one click on a machine with Cursor
installed. Or Settings → **MCP** → **Add new MCP server** with:

```json
{
  "mcpServers": {
    "mapmap": {
      "url": "https://mcp.mapmap.ai/mcp"
    }
  }
}
```

Then ask the agent to geocode, route or check an ADR tunnel code from
inside your editor. The [agent skills](/docs/skills) work in Cursor too —
they follow the open skills standard.

## Grok

Grok supports bring-your-own MCP connectors on paid tiers:
[grok.com](https://grok.com) → Settings → **Connectors** → add
`https://mcp.mapmap.ai/mcp`. Authentication: none.

## Perplexity

Pro/Max/Enterprise: Settings → **Connectors** → **Add connector** →
custom MCP, URL `https://mcp.mapmap.ai/mcp`. Works in Comet with the same
connector.

## VS Code / GitHub Copilot

```bash
code --add-mcp '{"name":"mapmap","url":"https://mcp.mapmap.ai/mcp"}'
```

Or add the server from the MCP registry view. Windsurf, JetBrains AI and
any other MCP-capable client take the same URL.

## Your own agent (any framework)

OpenAI Agents SDK, LangChain/LangGraph, LlamaIndex, CrewAI, Pydantic AI
and the Vercel AI SDK all consume remote MCP servers natively — point
them at `https://mcp.mapmap.ai/mcp`. Or skip MCP and call the
[REST API](/docs/api-reference) with the [OpenAPI spec](https://api.mapmap.ai/openapi.json).

An agent can mint its own key mid-task, no human in the loop:

```bash
curl -X POST https://api.mapmap.ai/v1/keys \
  -H "Content-Type: application/json" \
  -d '{"email": "you@example.com", "accept_tos": true, "source": "agent-recipe"}'
```

The returned `snk_` key works immediately (provisional, 1,000 calls);
clicking the emailed verification link lifts it to **50,000 calls a
month, free, commercial use allowed, no card**. Machine-payment types can
also pay per call with [x402](/docs/x402) — no account at all.

## Fair use, keys and attribution

- **Anonymous** MCP/demo usage is rate-limited per IP and capped daily;
  premium truck/ADR routing on the raw keyless API always needs a key
  (the `401` carries this exact recipe).
- **Keyed** usage bills to your account: present `snk_…` on the MCP
  endpoint or the REST API.
- The `source` field on key issuance (`"chatgpt"`, `"cursor"`,
  `"agent-recipe"`, …) is optional attribution — it helps us see which of
  these recipes people actually use, and changes nothing about the key.