> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mapping.travel/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your client

> Set up Claude Desktop, Cursor, or Continue with mapping.travel MCP.

## Get a key

<Steps>
  <Step title="Sign in to the app">
    Go to [app.mapping.travel](https://app.mapping.travel) and sign in.
  </Step>

  <Step title="Open Developers → MCP">
    The Developers section is in the sidebar between System and Settings.
  </Step>

  <Step title="Create a key">
    Click **+ New Key**, give it a name, and copy the plaintext value. You won't see it again.
  </Step>
</Steps>

## Configure your client

<Tabs>
  <Tab title="Claude Desktop">
    Claude Desktop currently spawns MCP servers over stdio, so we bridge through the [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) shim. Edit `~/Library/Application Support/Claude/claude_desktop_config.json`:

    ```json theme={null} theme={null}
    {
      "mcpServers": {
        "mapping-travel": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote@0.1.37",
            "https://mcp.mapping.travel/mcp",
            "--header",
            "X-API-Key: mt_mcp_live_..."
          ]
        }
      }
    }
    ```

    Restart Claude Desktop. The tools appear under the wrench icon.

    <Note>
      If you see `npm ERR! code EACCES` in `~/Library/Logs/Claude/mcp-server-mapping-travel.log`, your npm cache has root-owned files from a previous `sudo` install. Run `sudo chown -R $(id -u):$(id -g) ~/.npm` once and restart Claude Desktop.
    </Note>
  </Tab>

  <Tab title="Cursor">
    Cursor supports the Streamable HTTP transport natively. Edit `~/.cursor/mcp.json`:

    ```json theme={null} theme={null}
    {
      "mcpServers": {
        "mapping-travel": {
          "url": "https://mcp.mapping.travel/mcp",
          "headers": { "X-API-Key": "mt_mcp_live_..." }
        }
      }
    }
    ```

    Restart Cursor → **Settings → MCP** should show the server connected with 18 tools.
  </Tab>

  <Tab title="Continue">
    Continue's MCP support lives under `experimental` for now. Edit `~/.continue/config.json`:

    ```json theme={null} theme={null}
    {
      "experimental": {
        "modelContextProtocolServers": [
          {
            "transport": {
              "type": "streamable-http",
              "url": "https://mcp.mapping.travel/mcp",
              "headers": { "X-API-Key": "mt_mcp_live_..." }
            }
          }
        ]
      }
    }
    ```
  </Tab>

  <Tab title="MCP Inspector">
    For a quick visual sanity check without permanently configuring a client, use Anthropic's reference [MCP Inspector](https://github.com/modelcontextprotocol/inspector):

    ```bash theme={null}
    npx @modelcontextprotocol/inspector
    ```

    In the browser UI, pick **Streamable HTTP**, enter `https://mcp.mapping.travel/mcp` as the URL, add header `X-API-Key: mt_mcp_live_...`, and click **Connect**. You'll see all 18 tools with input forms and can invoke any of them manually.
  </Tab>
</Tabs>

## Verify

Ask your agent: *"What mapping tools do you have available?"* — it should list around 18 tools. If not, see [Troubleshooting](/mcp/troubleshooting).