Skip to main content
Crosmos MCP is an optional service for AI clients that support the Model Context Protocol. It gives agents callable tools to search memories, add memories, list spaces, and check API health. Use MCP when you want callable Crosmos memory tools in an AI client such as Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, opencode, Cline, Roo-Cline, Zed, or Kimi CLI. Use the automatic-context plugins when you want memory to run through a host’s lifecycle, or use the SDKs when you are building Crosmos into an application or backend service.

​
Interactive setup

The setup command authenticates with your Crosmos API key, detects installed MCP clients, writes their configuration, and can install the Crosmos skill for supported AI editors. It detects Claude Desktop, Claude Code, opencode, Cursor, VS Code, Windsurf, Cline, Roo-Cline, Zed, and Kimi CLI when they are installed.

​
Authenticate manually

Generate an API key from Settings → API Keys in the Crosmos Console. Keys use the csk_ prefix.
The login command validates the key and saves credentials to ~/.crosmos/credentials.json with restricted file permissions.
CROSMOS_API_KEY overrides saved credentials. Use environment variables for CI, containers, or client configuration that should not read from ~/.crosmos.

​
Configure a client manually

If you do not use setup, point your MCP client at npx -y @crosmos/crosmos-mcp.
Restart the client after changing its MCP configuration.

​
Install the skill

The setup wizard can install the Crosmos skill for supported AI editors. To install it manually:
See the skill guide for supported targets and locations.

​
Next steps

Tools

See tool inputs, behavior, and examples.

Configuration

Configure credentials, default spaces, timeouts, and deployment settings.

GitHub repository

Browse the source code, releases, and issues.