sibyl-memory-mcp

MCP server for Sibyl Memory Plugin. Exposes the local SQLite + FTS5 memory engine to any MCP-compatible agent: Claude Code, Codex CLI, Cursor, Continue, anything that speaks Model Context Protocol.

Install

pip install sibyl-memory-mcp

You also need an activated Sibyl Memory account. If you haven't already:

sibyl init

This creates ~/.sibyl-memory/credentials.json (server-issued, HMAC-signed) and a local SQLite database at ~/.sibyl-memory/memory.db. The MCP server reads both automatically.

Add to Claude Code

Edit ~/.claude/settings.json (global) or .mcp.json (project-local):

{
  "mcpServers": {
    "sibyl-memory": {
      "command": "sibyl-memory-mcp"
    }
  }
}

Restart Claude Code. The 8 memory tools (prefixed memory_*) become available immediately.

Add to Codex CLI

Edit ~/.codex/config.toml:

[[mcp_servers]]
name = "sibyl-memory"
command = "sibyl-memory-mcp"

Restart Codex.

Run with Docker

A first-party image is provided at the repo root (Dockerfile, docker-compose.yml, .dockerignore). The image is non-root, runs on a pinned slim Python base, and bakes in no secrets. Memory lives on a mounted volume so it survives container recreation.

The MCP server speaks stdio, not HTTP. It is not a daemon you leave running. Run it attached to an MCP client's stdin, or via docker compose run.

Build:

docker build -t sibyl-memory-mcp:local .

First, activate on the host so the mounted volume carries your credentials:

sibyl init

Run attached, mounting your host ~/.sibyl-memory for memory.db and credentials.json:

docker run -i --rm \
  -v "$HOME/.sibyl-memory:/home/app/.sibyl-memory" \
  sibyl-memory-mcp:local

Note the -i (keep STDIN open) and the absence of -t (no TTY): the MCP client drives stdin programmatically.

Wire it into Claude Code by pointing the command at the container:

{
  "mcpServers": {
    "sibyl-memory": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-v", "/absolute/path/to/your/.sibyl-memory:/home/app/.sibyl-memory",
        "sibyl-memory-mcp:local"
      ]
    }
  }
}

Using Compose (note run, not up, because it is a stdio server):

docker compose run --rm sibyl-memory-mcp

Environment overrides (SIBYL_MEMORY_DB, SIBYL_CREDENTIALS, SIBYL_TENANT_ID) are passed through when set on the host. No secret is ever written into the image or the compose file. Credentials arrive only through the mounted volume.

Tools exposed

Full docs at docs.sibyllabs.org/memory/integrations.

Environment overrides

Tier behavior

• Free tier: 8 tools work. Hard-capped at 2 MB of local storage. Writes that would push past the cap return CAP_EXCEEDED with an upgrade_url. Self-learning and memory-check-up tools are not exposed on free tier.
• Paid tiers (Sync / Stake / Lifetime / Enterprise): cap removed. All tools enabled.

The cap-gate runs against the server-authoritative tier (verified via HMAC-signed credentials): the MCP server can't bypass it by editing the local file.

License

MIT: same as the rest of the sibyl-memory-* family.