দূরবর্তীভাবে সংযুক্ত করুন
Every hosted Neotoma instance—the public 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 instead—stdio is faster and needs no tunnel. See Hosted Neotoma for the flavor comparison.
Pick your harness
Desktop app—add a stdio server or remote MCP endpoint.
ChatGPT developer mode—add Neotoma as a remote MCP server.
OpenAI Codex—add an `[mcp_servers.neotoma]` block to ~/.codex/config.toml.
OpenCode—add @neotoma/opencode-plugin to opencode.json and keep MCP configured.
OpenClaw agents—install via clawhub or add manual MCP config.
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) renders harness-specific connect snippets with its own URL prefilled. The per-harness docs linked above mirror that content with placeholders you substitute manually.