MCP server

The tools: get_memory_context (hybrid, planned recall), search_memory, list_memories, explore_entity, explore_memories (how memories connect), save_memory, learn_from_conversation, manage_goal, record_decision, record_lesson, relate_entities, update_memory and delete_memory. Start the server with --intelligence and learn_from_conversation also updates goals and decisions, keeps task details in working memory and forgets on request. Read-only tools are annotated, and --read-only exposes only those. The user whose memory the tools use is set by the server (--user, or the X-Kioko-User header over HTTP). The model can never choose it, so a prompt injection can't reach another user's memories. Protocol revisions 2024-11-05 to 2025-11-25 are supported.

Desktop hosts (stdio). For Claude Desktop (claude_desktop_config.json), Cursor (~/.cursor/mcp.json) and similar hosts:

{
  "mcpServers": {
    "kioko": { "command": "kioko", "args": ["mcp", "--user", "kumar"] }
  }
}

With no --db, memories go to ~/.kioko/memory.db. Use --url http://memory-service:8765 (plus KIOKO_API_KEY in env) to share a central service. For Claude Code: claude mcp add kioko -- kioko mcp --user kumar.

VS Code / GitHub Copilot (HTTP), in .vscode/mcp.json:

{
  "servers": {
    "kioko": {
      "type": "http",
      "url": "http://localhost:8765/mcp",
      "headers": { "X-Kioko-User": "kumar", "Authorization": "Bearer ${input:kioko-key}" }
    }
  },
  "inputs": [{ "type": "promptString", "id": "kioko-key", "description": "Kioko API key", "password": true }]
}

Copilot Studio and other remote clients. Use the Streamable HTTP endpoint https://<your-host>/mcp, with API-key authentication as Authorization: Bearer <key> or X-API-Key, served by kioko serve behind HTTPS. The server answers with JSON, keeps no sessions, and returns 405 to GET.