Claude Desktop Integration

Claude Desktop supports MCP servers through a JSON config file. Connecting Kiomon gives Claude a persistent brain: it can search your saved library, answer grounded questions with citations, and write learnings back as reviewable memory drafts.

Configure the MCP server

1. Open your Claude Desktop config file:
   • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
   • Windows: %APPDATA%\Claude\claude_desktop_config.json
2. Add the kiomon entry under mcpServers:

{
  "mcpServers": {
    "kiomon": {
      "command": "npx",
      "args": ["-y", "@kiomon/mcp-server"],
      "env": {
        "KIOMON_TOKEN": "your-key",
        "KIOMON_URL": "https://api.kiomon.com"
      }
    }
  }
}

3. Restart Claude Desktop completely (quit and reopen — not just a new chat).
4. Look for the hammer/plug icon in the bottom toolbar, then the Kiomon server with its tools enabled.

Getting your API key

1. Open the dashboard → Settings → API Keys.
2. Click Generate Key and copy it (shown only once).
3. Paste it into the config’s KIOMON_TOKEN field.

You can also grab a ready-made config from the dashboard’s Settings → Agents & MCP tab, which fills in your key and URL automatically.

Using Kiomon with Claude

Grounded research

“Search my library for what I saved about vector search. Summarize the key concepts with citations.”

Claude runs search_memory (hybrid search) and get_memory for the strongest hits, then answers from the retrieved content.

Workspace briefing

“Get context for my ‘Product’ workspace and tell me what I should know before working on the pricing page.”

Claude calls get_workspace_context, loading your pinned memories, routines, and topic facts — a true pre-flight brief.

Memory capture

Claude doesn’t remember anything between sessions — that’s exactly what Kiomon fixes. At the end of a session:

“Save what we decided about the onboarding flow as memories for my approval.”

Claude drafts the decisions as pending memories in your Review Inbox (via draft_memory or reflect_session). Approve them in the dashboard and they become permanent, retrievable knowledge — with derived_from edges back to the source documents.

Troubleshooting

Symptom	Fix
“Server failed to start”	Config JSON syntax error — validate with npx -y @kiomon/mcp-server --token x (a plain run prints errors)
Tools show but calls 401	Key is wrong/revoked — regenerate and update KIOMON_TOKEN
Connected to the wrong environment	KIOMON_URL must match the environment your key was issued against (dev vs prod)
Nothing in the library	Point Claude at list_workspaces first to discover which workspace holds your content