Integration · Claude Desktop

A persistent memory for Claude Desktop

Claude's context window resets every chat. Kiomon gives Claude a brain that survives: connect over native MCP and Claude can read, search, and write to your workspace seamlessly.

Connect in 2 steps

  • Get your token. Create a workspace in the Kiomon dashboard and copy your API token.
  • Add the MCP server. Register the server in Claude Desktop's claude_desktop_config.json: 
    {
  "mcpServers": {
    "kiomon": {
      "command": "npx",
      "args": ["kiomon-mcp", "--token", "<your-kiomon-token>", "--url", "<your-kiomon-url>"]
    }
  }
}

Restart Claude Desktop and start a new chat. Claude can now call search_memory, get_memory, draft_memory, and the rest of the memory-native toolset.

Why it matters for Claude

  • Continuity: Every conversation starts with the context of previous sessions.
  • No reprompting: Preferences, project facts, and architecture decisions stay stored in your knowledge graph.
  • Built-in guardrails: Memory writes land in the Review Inbox as pending drafts, approved by you before they activate.
  • Traceable recall: Responses can cite the exact memory nodes they were grounded on.

Ready

Create your free workspace, or skim the protocol docs first. Running a different agent? See Cursor or Ollama.