Claude Code and Desktop

These examples connect Claude to the standalone local MCP demonstration. The current binary uses an in-memory backend, so records are tied to that process. A dedicated Mind requires the HTTP integration or a verified remote-backed MCP adapter.

Claude Code

After building akasha-mcp, add it as a stdio server:

claude mcp add --transport stdio minds-local-demo -- \
  /absolute/path/to/akasha-mcp \
  --transport stdio --namespace local-demo --agent-id claude

Claude options precede the server name; arguments after -- belong to the server. Use claude mcp list, claude mcp get minds-local-demo, and the in-session /mcp view to inspect the connection. The current official Claude Code MCP guide explains configuration scope and server management.

Claude Desktop

The repository's Desktop configuration helper targets ~/Library/Application Support/Claude/claude_desktop_config.json on macOS and the corresponding Claude configuration directory on supported platforms. Merge this server entry with existing entries rather than overwriting the file:

{
  "mcpServers": {
    "minds-local-demo": {
      "command": "/absolute/path/to/akasha-mcp",
      "args": ["--transport", "stdio", "--namespace", "local-demo", "--agent-id", "claude"]
    }
  }
}

Use the installed Desktop client's developer/MCP settings to confirm its current configuration location and reload the server. The path above is source-backed by the Minds helper; host configuration can change between releases.

Test and troubleshoot

Check the executable path and launch errors first. Then inspect actual tool discovery and a recall result. If a saved test record disappears after a restart, that matches the current standalone backend; it is not proof that a dedicated Mind lost data.

Do not use cogs mcp setup-claude as an authoritative setup command in this snapshot: it emits akasha mcp serve, which the CLI parser does not implement. The direct binary invocation above avoids that mismatch.