atomicmemory-integrations

Plugins, adapters, and the shared MCP server that expose AtomicMemory to coding agents and AI frameworks.

What's inside

packages/
└── mcp-server/              # @atomicmemory/mcp-server — the spine
                             # exposes memory_search / memory_ingest / memory_package
                             # over MCP, wraps @atomicmemory/atomicmemory-sdk

plugins/                     # coding-agent wrappers
├── claude-code/             # Claude Code plugin (plugin.json + SKILL.md)
└── openclaw/                # OpenClaw plugin (openclaw.plugin.json + skill.yaml)

examples/                    # runnable examples (coming soon)

Framework adapters (adapters/vercel-ai-sdk, adapters/langchain-js, adapters/mastra, adapters/openai-agents, adapters/langgraph-js) are tracked as planned work — see the docs site at https://docs.atomicmemory.ai/integrations/ for status.

Architecture

All coding-agent plugins are thin wrappers over the same @atomicmemory/mcp-server process. A plugin's job is:

1. Ship the agent-facing skill/manifest in the shape that agent expects.
2. Tell the agent how to spawn the MCP server with the user's config.
3. Nothing else.

Memory semantics live in @atomicmemory/atomicmemory-sdk; storage and retrieval live in atomicmemory-core. Plugins in this repo do not re-implement memory — they adapt the surface.

Develop

pnpm install
pnpm build
pnpm test

License

MIT.