# 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](https://neotoma.io/install/); 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](https://neotoma.io/install/) before configuring a host. | Host | Neotoma path | Transport / requirement | Verification and current limit | | ------------------------------------------------------------- | ------------------------------------------------------------------------------ | --------------------------------------------------- | ------------------------------------------------------------------------------------------------ | | [Claude Code](../guides/connections/claude-code.md) | `setup --tool claude-code` | Local stdio; remote HTTP configured separately | Check Claude Code `/mcp` and read-only retrieval; hooks separate. | | [Cursor](../guides/connections/cursor.md) | `setup --tool cursor` | Local stdio; remote HTTP configured separately | Inspect `.cursor/mcp.json` or user config and tool list; hooks separate. | | [Codex CLI](../guides/connections/codex.md) | `setup --tool codex` | Local stdio; remote HTTP/OAuth configured in Codex | Check `codex mcp list` and read-only retrieval. | | [OpenClaw](../guides/connections/openclaw.md) | 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](../guides/connections/claude-desktop.md) | `setup --tool claude-desktop --install-scope user` | Local stdio; remote connector is separate | Inspect Desktop config; default project scope can target Cursor config. | | [ChatGPT](../guides/connections/chatgpt.md) | 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](../guides/connections/windsurf.md) | Manual MCP | Local stdio; remote HTTP conditional on host | `setup --tool windsurf` can report success while writing Cursor config. | | [Continue](../guides/connections/continue.md) | 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](../guides/connections/vscode.md) | 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](../guides/connections/ironclaw.md) | Manual host registration | Remote MCP path documented; local stdio conditional | Not a `setup --tool` target; verify with IronClaw's tools. | | [Letta](../guides/connections/letta.md) | SDK session configuration | External Neotoma MCP endpoint | Current Agent SDK tools are session-scoped; older V1 registration guide differs. | | [OpenCode](../guides/connections/opencode.md) | Plugin/hooks; MCP configured separately | Local Neotoma API for capture | Hook event readback and MCP retrieval are distinct checks. | | [Claude Agent SDK](../guides/connections/claude-agent-sdk.md) | In-process adapter hooks | Consumer application provides endpoint | Verify captured event; adapter does not register MCP. | | [Smithery](../guides/connections/smithery.md) | 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](https://neotoma.io/install/) and each guide distinguish Neotoma source support from host vendor behavior. The [MCP overview](../developer/mcp_overview.md) explains transport; the [CLI reference](../developer/cli_reference.md) defines Neotoma commands. The [human connection index](https://neotoma.io/install/) 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](hooks/claude_code.md), [Cursor](hooks/cursor.md), [Codex CLI](hooks/codex_cli.md), [OpenCode](hooks/opencode.md), and [Claude Agent SDK](hooks/claude_agent_sdk.md). Applications can use the [TypeScript client](../../packages/client) or [Python client](../../packages/client-python) 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.