Integrations
Neotoma is cross-platform by design. One memory graph across every agent host you use — no platform lock-in, no separate state per tool.
This page is the single index of every host, harness, and framework Neotoma integrates with today, and the status of each.
Supported via MCP
MCP is the primary integration protocol. Every host below speaks MCP over local stdio, remote HTTP, or both.
| Host | Modes | Install | Setup guide |
|---|---|---|---|
| Cursor | stdio, remote HTTP | neotoma setup --tool cursor --yes | neotoma-with-cursor |
| Claude Code | stdio, remote HTTP | neotoma setup --tool claude-code --yes | neotoma-with-claude-code |
| Claude Desktop | local, remote MCP | neotoma setup --tool claude-desktop --yes | desktop · remote MCP |
| ChatGPT | MCP App, Custom GPT Actions | Manual HTTPS + OAuth | neotoma-with-chatgpt · remote MCP · custom GPT |
| Codex CLI | stdio, remote HTTP (OAuth) | neotoma setup --tool codex --yes | neotoma-with-codex · stdio · remote HTTP |
| OpenClaw | Native plugin + MCP | neotoma setup --tool openclaw --yes | neotoma-with-openclaw · stdio · remote HTTP |
| IronClaw | MCP | neotoma setup --tool ironclaw --yes | neotoma-with-ironclaw |
| Windsurf | MCP | neotoma setup --tool windsurf --yes | neotoma-with-windsurf |
| Continue | MCP | neotoma setup --tool continue --yes | neotoma-with-continue |
| VS Code (Copilot Chat) | MCP | neotoma setup --tool vscode --yes | neotoma-with-vscode |
| Letta | MCP (streamable HTTP, SSE, stdio) | Manual SDK setup | neotoma-with-letta |
Supported via hooks
Hooks integrate with harnesses that expose lifecycle events. They provide guaranteed capture, retrieval injection, and persistence safety nets — the reliability floor that composes with MCP's quality ceiling.
| Harness | Setup guide |
|---|---|
| Claude Code | neotoma-with-claude-code |
| Cursor | neotoma-with-cursor |
| OpenCode | neotoma-with-opencode |
| Codex CLI | neotoma-with-codex |
| Claude Agent SDK | neotoma-with-claude-agent-sdk |
Client libraries
Embed Neotoma directly in your application:
| Language | Package |
|---|---|
| TypeScript | @neotoma/client |
| Python | neotoma-client |
Not yet supported
These hosts are commonly requested. They are not yet supported. The "What it would take" column is descriptive, not committal — open a feature request if you want one prioritized.
| Host / framework | What it would take |
|---|---|
| LangGraph | A Python adapter on top of the Neotoma Python client, exposing store and retrieve_* as LangGraph memory nodes. |
| CrewAI | A Python adapter that exposes Neotoma actions as CrewAI tools, similar in shape to the OpenClaw native plugin. |
| Hermes | 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.
Related
- MCP reference — protocol details and transport modes
- CLI reference —
neotoma setup,neotoma mcp config - Install — get started