<!--
  Full-page Markdown export (rendered HTML → GFM).
  Source: https://neotoma.io/ru/connect
  Generated: 2026-04-24T09:10:57.194Z
-->
# Connect a remote Neotoma

Every hosted Neotoma instance - the [public sandbox](/sandbox), a personal tunnel, or a self-hosted deployment - exposes an MCP endpoint at `/mcp`. This page points you at the per-harness doc for connecting to it over HTTP without installing Neotoma locally.

Installing Neotoma on the same machine as your agent? Use the [install guide](/install) instead - stdio is faster and needs no tunnel. See [Hosted Neotoma](/hosted) for the flavor comparison.

## Pick your harness

-   [Claude Code](/neotoma-with-claude-code)
    
    CLI agent - register with \`claude mcp add --transport http\`.
    
    [Remote MCP setup](/neotoma-with-claude-code)
    
-   [Claude Desktop](/neotoma-with-claude-connect-remote-mcp)
    
    Desktop app - add a stdio server or remote MCP endpoint.
    
    [Remote MCP setup](/neotoma-with-claude-connect-remote-mcp) · [Local / stdio setup](/neotoma-with-claude-connect-desktop)
    
-   [claude.ai (remote MCP)](/neotoma-with-claude-connect-remote-mcp)
    
    Web Claude with remote MCP support.
    
    [Remote MCP setup](/neotoma-with-claude-connect-remote-mcp)
    
-   [ChatGPT (remote MCP)](/neotoma-with-chatgpt-connect-remote-mcp)
    
    ChatGPT developer mode - add Neotoma as a remote MCP server.
    
    [Remote MCP setup](/neotoma-with-chatgpt-connect-remote-mcp) · [Local / stdio setup](/neotoma-with-chatgpt-connect-custom-gpt)
    
-   [Codex](/neotoma-with-codex-connect-remote-http-oauth)
    
    OpenAI Codex - add an \`\[mcp\_servers.neotoma\]\` block to ~/.codex/config.toml.
    
    [Remote MCP setup](/neotoma-with-codex-connect-remote-http-oauth) · [Local / stdio setup](/neotoma-with-codex-connect-local-stdio)
    
-   [Cursor](/neotoma-with-cursor)
    
    Cursor IDE - add a \`mcpServers\` entry to .cursor/mcp.json.
    
    [Remote MCP setup](/neotoma-with-cursor)
    
-   [OpenClaw](/neotoma-with-openclaw-connect-remote-http)
    
    OpenClaw agents - install via clawhub or add manual MCP config.
    
    [Remote MCP setup](/neotoma-with-openclaw-connect-remote-http) · [Local / stdio setup](/neotoma-with-openclaw-connect-local-stdio)
    

* * *

## What you need from the host

Each per-harness doc above expects you to know two things about the Neotoma you want to talk to:

-   **MCP URL.** e.g. `https://sandbox.neotoma.io/mcp` for the sandbox, or `https://your-tunnel.example.com/mcp` for a personal tunnel.
-   **Auth posture.** The sandbox is unauthenticated. Personal tunnels and self-hosted instances typically require OAuth or a bearer token for writes; discovery endpoints (`/server-info`, `/.well-known/*`) stay public.

Tip: the root page of any hosted Neotoma (e.g. [sandbox.neotoma.io](https://sandbox.neotoma.io)) renders harness-specific connect snippets with its own URL prefilled. The per-harness docs linked above mirror that content with placeholders you substitute manually.

* * *

## Related

[Install Neotoma locally](/install) · [Hosted flavors overview](/hosted) · [Public sandbox](/sandbox) · [MCP reference](/mcp)