Neotoma is cross-platform by design. This page is the single canonical index of every host, harness, and framework Neotoma integrates with, and the status of each integration.
The public-facing version of this page lives at neotoma.io/integrations.
Source of truth for installable targets:
src/cli/setup.ts(theharnessMapingetSkillsTarget). If this matrix disagrees with the CLI, the CLI wins.
- Stable — supported in production; covered by setup docs and (where applicable)
neotoma setup --tool <name>. - Preview — works end-to-end but the install path is manual or partially documented.
- Experimental — early integration; expect rough edges.
- Not yet supported — see the roadmap section below.
MCP is the primary integration protocol. Every host below speaks MCP either over local stdio, remote HTTP, or both.
| Host | Modes | Install | Setup guide | Status |
|---|---|---|---|---|
| Cursor | stdio, remote HTTP | neotoma setup --tool cursor --yes |
mcp_cursor_setup.md | Stable |
| Claude Code | stdio, remote HTTP | neotoma setup --tool claude-code --yes or npm run sync:mcp |
mcp_claude_code_setup.md | Stable |
| Claude Desktop | local, remote MCP, desktop connector | neotoma setup --tool claude-desktop --yes |
neotoma-with-claude-connect-desktop, remote MCP | Stable |
| ChatGPT | MCP App (connector), Custom GPT Actions (OpenAPI) | Manual HTTPS + OAuth | chatgpt_apps_setup.md, chatgpt_actions_setup.md | Stable |
| Codex CLI | stdio, remote HTTP (OAuth) | neotoma setup --tool codex --yes |
neotoma-with-codex, stdio, remote | Stable |
| OpenClaw | Native plugin (kind: memory) + MCP |
neotoma setup --tool openclaw --yes |
mcp_openclaw_setup.md, openclaw.md | Stable |
| IronClaw | MCP | neotoma setup --tool ironclaw --yes |
mcp_ironclaw_setup.md | Stable |
| Smithery | External URL registry | Manual registration | smithery_external_url.md | Stable |
| Windsurf | MCP | neotoma setup --tool windsurf --yes |
mcp_windsurf_setup.md | Stable |
| Continue | MCP | neotoma setup --tool continue --yes |
mcp_continue_setup.md | Stable |
| VS Code (Copilot Chat) | MCP | neotoma setup --tool vscode --yes |
mcp_vscode_setup.md | Stable |
| Letta | MCP (streamable HTTP, SSE, stdio) | Manual SDK setup | mcp_letta_setup.md | Stable |
Hooks are the reliability floor — guaranteed capture, retrieval injection, compaction awareness, and persistence safety nets that compose with MCP. MCP remains the quality ceiling for agent-driven structured writes.
| Harness | Package | Guide | Status |
|---|---|---|---|
| Claude Code | packages/claude-code-plugin |
hooks/claude_code.md | Stable |
| Cursor | packages/cursor-hooks |
hooks/cursor.md | Stable |
| OpenCode | packages/opencode-plugin |
hooks/opencode.md | Stable |
| Codex CLI | packages/codex-hooks |
hooks/codex_cli.md | Stable |
| Claude Agent SDK | packages/claude-agent-sdk-adapter |
hooks/claude_agent_sdk.md | Stable |
For applications that embed Neotoma directly (no host/harness in the loop):
| Language | Package | Source |
|---|---|---|
| TypeScript | @neotoma/client |
packages/client |
| Python | neotoma-client |
packages/client-python |
The hosts and frameworks below are commonly requested or named by competing memory products. They are not yet supported. The "What it would take" column is descriptive — actual prioritization depends on engineering capacity.
| Host / framework | Why it matters | What it would take |
|---|---|---|
| LangGraph | Common agent-graph orchestration framework | Either an MCP-compatible memory node, or a Python adapter on top of packages/client-python. Likely a small wrapper plus an example notebook. |
| CrewAI | Multi-agent orchestration | A Python adapter that exposes Neotoma store / retrieve_* actions as CrewAI tools. Same shape as the OpenClaw native plugin. |
| Hermes | Named by competing memory products | Confirm the specific framework being referenced (the name is overloaded) before scoping. |
Want one of these prioritized? Open an issue at github.com/Lemonbrand/neotoma-feedback describing your use case.
A new host integration usually needs three things:
- A setup path. For MCP hosts that use stdio or remote HTTP, this is typically an entry in
src/cli/setup.ts(harnessMap) plus adocs/developer/mcp_<host>_setup.mdguide. For hosts that use lifecycle hooks, this is a new package underpackages/(mirroringpackages/cursor-hooksorpackages/opencode-plugin). - A public setup page. Add
docs/site/pages/en/neotoma-with-<host>.mdxwith a sidecar.meta.jsonmatching the format used by existingneotoma-with-*pages. - A row in this matrix. Update both this file and
docs/site/pages/en/integrations.mdx.
The CLI's harnessMap is the source of truth for supported --tool targets. Keep this matrix synchronized with it.
- Public integrations page — buyer-facing version
- MCP specification — protocol details
- CLI reference —
neotoma setup,neotoma mcp config,neotoma cli config - Hooks index — hooks contract and per-harness guides