<!--
  Full-page Markdown export (rendered HTML → GFM).
  Source: https://neotoma.io/neotoma-with-claude-connect-remote-mcp
  Generated: 2026-05-04T09:50:40.900Z
-->
# claude.ai remote MCP setup

[Neotoma with Claude](/neotoma-with-claude) · Remote setup for connecting Neotoma to claude.ai.

Looking for Claude Desktop (local stdio) instead? See [Claude Desktop local setup](/neotoma-with-claude-connect-desktop).

* * *

## Setup

claude.ai connects to MCP servers over the network. Start with local install, then configure remote access:

1.  **Start Neotoma with a tunnel:** follow the [tunnel guide](/tunnel) to expose your local Neotoma instance over HTTPS. The quickest path:
    
    Code snippet
    
    Copy the exact snippet shown below.
    
    ```
    neotoma api start --env prod --tunnel
    ```
    
2.  **Connect in claude.ai:** go to Settings → MCP Servers and add your tunnel URL (for example `https://<tunnel-host>/mcp`). Claude authenticates via OAuth; the Neotoma API supports the [MCP OAuth authorization flow](https://modelcontextprotocol.io/specification/2025-03-26/basic/authorization).

**Use the tunnel URL, not a custom domain.** When you run with `--tunnel` (Cloudflare or ngrok), set the MCP server URL in Claude to the *exact* tunnel URL printed at startup (e.g. `https://<tunnel-host>/mcp`). Do not use a custom domain that points elsewhere (e.g. your own HTTPS host). Traffic must hit the same process that is serving the tunnel; otherwise Connect will fail and you will not see requests in `neotoma api logs`.

[Back to Neotoma with Claude](/neotoma-with-claude) · [Install guide](/install) · [MCP reference](/mcp)