Claude Session Continuity MCP Server

Session continuity and persistent memory for Claude Code, OpenAI Codex CLI & Google Gemini CLI. Auto-injects past context on start, hands over hot

Local serverstdio

What is the Claude Session Continuity MCP MCP server?

Connect Claude Session Continuity MCP to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Session continuity and persistent memory for Claude Code, OpenAI Codex CLI & Google Gemini CLI. Auto-injects past context on start, hands over hot files + build status across compaction, shares one local db across all three. Every feature. The claude session continuity mcp mcp server is what makes that connection.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Setup — npm i -g → hooks auto-install
  • Trigger — 5 automatic hooks (no commands)
  • Storage — 100% local SQLite
  • Latency — < 5ms (on-device)
  • Privacy — Never leaves your machine
  • Search — FTS5 + local semantic, KO/EN/JA cross-lingual
  • Sessions — The Sessions tool exposed by this server
  • Memories — The Memories tool exposed by this server
  • Solutions — The Solutions tool exposed by this server

Installation

passbaton-hooks on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Credentials and setup notes

Configuration is passed through the environment: MCP_HOOKS_DISABLED. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Claude Session Continuity MCP's toolset — Setup, Trigger, Storage and 6 more — is a fair guide to whether it matches your workflow. It is maintained by leesgit; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 9 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Claude Session Continuity MCP.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
Setupnpm i -g → hooks auto-install
Trigger5 automatic hooks (no commands)
Storage100% local SQLite
Latency< 5ms (on-device)
PrivacyNever leaves your machine
SearchFTS5 + local semantic, KO/EN/JA cross-lingual
SessionsThe Sessions tool exposed by this server.
MemoriesThe Memories tool exposed by this server.
SolutionsThe Solutions tool exposed by this server.

How to install the Claude Session Continuity MCP MCP server

{
  "mcpServers": {
    "claude-session-continuity": {
      "command": "npx",
      "args": ["-y", "passbaton-hooks"],
      "env": {
        "MCP_HOOKS_DISABLED": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
MCP_HOOKS_DISABLEDConfiguration value read at startup.Optional

Example prompts to try

  • Use Claude Session Continuity MCP to Setup.
  • Use Claude Session Continuity MCP to Trigger.
  • Use Claude Session Continuity MCP to Storage.

Frequently asked questions

It connects Claude Session Continuity MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 9 tools (Setup, Trigger, Storage, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Claude Session Continuity MCP directly.