Firekeep MCP server

Firekeep

Your agents shouldn’t work like strangers.

Connect Claude Code, Codex, Kiro, OpenCode, and other MCP clients through one shared, self-hosted Keep.

Every solved problem should make the next one easier. Firekeep preserves the experience behind the work — durable knowledge, working state, procedures, coordination, and inspectable evidence — and puts it back to work in the next session, tool, or machine.

Use it for your own continuity on one workstation. Add teammates when you need them without starting the team’s context over.

Website · Install · Product tour · Firekeep Studio · Evidence · Privacy · Support

One Keep, across runtimes

flowchart LR
    A["Claude Code<br/>stores a proven fix"] --> K[("your self-hosted<br/>Keep")]
    K --> B["Codex<br/>recalls the fix + evidence"]
    K --> C["Kiro<br/>reuses the procedure"]
    K --> D["OpenCode / MCP client<br/>continues informed"]

Agents keep their native interfaces and provider-owned sessions. What carries forward is the Firekeep context they explicitly record and recall through the same local MCP gateway. That means one person can switch tools without losing the thread, and a team can earn context once and carry it forward.

See Claude Code and Codex share one Keep →

Install Firekeep

The installer configures Claude Code, Codex, Kiro, and OpenCode together (plus Claude Desktop when its config directory exists), then asks where your Firekeep server should live. The full setup flow is in the install guide.

curl -fsSL 'https://firekeep.ai/latest/install?src=github' | sh    # macOS / Linux
irm 'https://firekeep.ai/latest/install.ps1?src=github' | iex      # Windows PowerShell

The current server targets linux/amd64 and needs Docker Compose v2, two x86-64 CPU cores, and Git; 16 GB RAM is recommended for the default stack. It binds to 127.0.0.1 by default. See the requirements and sizing notes before choosing a host.

Trying Firekeep for the first time? Share what worked and where you got stuck →

Runtime coverage

Claude Desktop is added when its config directory exists. Other MCP clients can use the generic path.

• Client Kit: configures Claude Code, Codex, Kiro, and OpenCode together;

pre-tool hook can hard-block an edit, write, or shell action.

• Claude Code: managed MCP, instructions, and lifecycle hooks. Its supported

so lifecycle automation and pre-edit enforcement are not implied.

• Codex: managed MCP plus AGENTS.md guidance. Codex exposes no native hooks,

On the validated Kiro CLI 2.12.1 surface, its pre-edit hook is advisory.

• Kiro CLI: a named Firekeep agent with MCP, steering, and lifecycle hooks.

workspace. The direct Grok adapter has no Keep memory, hooks, or briefing; Studio reports that boundary instead of inheriting another runtime’s status.

• Firekeep Studio: runs Codex, Claude Code, Kiro CLI, and Grok in one desktop

See the integration guide and Studio runtime matrix for the maintained details.

Measured retrieval, with the method attached

Shortened. The full README is on GitHub.