Integrations matrix
Compare Neotoma connection paths and their verification requirements across documented hosts.
Neotoma setup behavior was checked against published v0.25.0 (8ca1f0a) and main (4779784). Vendor documentation was checked on 2026-10-24; host runtime and Windows compatibility remain unverified.
This is the canonical index of Neotoma's documented host paths. The CLI target list is based on the setup implementation and human connection index; host runtime compatibility, particularly on Windows and remote authentication flows, has not been smoke tested for every host. “Documented” means a path exists in source and guides, not that an installed host passed an end-to-end test. Check the connection guides before configuring a host.
| Host | Neotoma path | Transport / requirement | Verification and current limit |
|---|---|---|---|
| Claude Code | setup --tool claude-code |
Local stdio; remote HTTP configured separately | Check Claude Code /mcp and read-only retrieval; hooks separate. |
| Cursor | setup --tool cursor |
Local stdio; remote HTTP configured separately | Inspect .cursor/mcp.json or user config and tool list; hooks separate. |
| Codex CLI | setup --tool codex |
Local stdio; remote HTTP/OAuth configured in Codex | Check codex mcp list and read-only retrieval. |
| OpenClaw | Native plugin first; setup --tool openclaw handles Neotoma setup layers only |
Plugin local; remote MCP manual | Confirm plugin load separately from any MCP tool list. |
| Claude Desktop | setup --tool claude-desktop --install-scope user |
Local stdio; remote connector is separate | Inspect Desktop config; default project scope can target Cursor config. |
| ChatGPT | Manual MCP connector; Custom GPT Actions are a separate OpenAPI route | Reachable authenticated HTTPS; no local stdio | Check host feature availability and read-only retrieval or Actions operation list. |
| Windsurf | Manual MCP | Local stdio; remote HTTP conditional on host | setup --tool windsurf can report success while writing Cursor config. |
| Continue | Manual MCP | Local stdio or supported remote transport | Current Continue guide uses YAML or .continue/mcpServers/; setup can write Cursor config. |
| VS Code / Copilot Chat | Manual MCP | Local stdio or HTTP; host-specific config schemas | servers in .vscode/mcp.json, mcpServers in portable format; setup can write Cursor config. |
| IronClaw | Manual host registration | Remote MCP path documented; local stdio conditional | Not a setup --tool target; verify with IronClaw's tools. |
| Letta | SDK session configuration | External Neotoma MCP endpoint | Current Agent SDK tools are session-scoped; older V1 registration guide differs. |
| OpenCode | Plugin/hooks; MCP configured separately | Local Neotoma API for capture | Hook event readback and MCP retrieval are distinct checks. |
| Claude Agent SDK | In-process adapter hooks | Consumer application provides endpoint | Verify captured event; adapter does not register MCP. |
| Smithery | External URL registry | Existing HTTPS /mcp endpoint |
Read back registry target and make a read-only MCP call. |
Scope and provenance
The CLI recognizes five setup --tool targets; OpenClaw’s primary path is the native plugin, leaving four direct setup commands in this matrix. Some other names are accepted by the argument parser but fall through to a Cursor config writer; that is tracked separately as the setup fallback defect (issues 2691 and 2681). A successful CLI exit is not evidence that a Windsurf, Continue, or VS Code config was written. The guides use manual paths until the writer and tests are fixed. Remote HTTP requires an authenticated reachable instance and the host's current transport/auth support; no guide assumes a local stdio entry reaches remote data.
The connection guide index and each guide distinguish Neotoma source support from host vendor behavior. The MCP overview explains transport; the CLI reference defines Neotoma commands. The human connection index gives the install prerequisite.
Hooks and client libraries
Hooks capture lifecycle events; MCP supplies agent-driven structured calls. They may coexist but one does not verify the other. Source guides: Claude Code, Cursor, Codex CLI, OpenCode, and Claude Agent SDK. Applications can use the TypeScript client or Python client without a host harness.
Adding a host
Confirm the host's primary documentation and a live configuration path, then add a connection guide with its setup kind, prerequisites, verification, and failure path. Update src/shared/harness_connections.ts and the install entries in frontend/src/site/docs_viewer_manifest.ts with the same ID. Add a setup --tool claim only after the CLI writer targets that host's actual config and an effect-level test proves it.
Install
MCP
CLI