Firekeep

MCP文档知识

提供方 未标注

文档知识 未标注 未标注 社区 / 第三方 Claude DesktopClaudeCursorVS Code

源代码可用的、自托管的共享内存、工作上下文、协调与证据,适用于Claude Code、Codex、Kiro、OpenCode及MCP客户端。

一句话选型结论

按资料字段整理

Firekeep 属于文档知识类 MCP 服务器,传输方式未标注,鉴权方式未标注,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类文档知识 传输方式未标注 鉴权未标注 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

文档知识
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

记忆

安装与配置

未标注 未标注
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
文档检索问答

在你的文档库里按问题找答案。

知识库读写

把新资料写进知识库,随用随取。

内容整理

把零散资料归纳成结构化笔记。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在文档知识场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Firekeep当前 未标注 未标注 未标注 无 未标注
dify 未标注 stdio · 本地进程 本地部署 有 2026-04-11
open-webui 未标注 stdio · 本地进程 本地部署 有 2026-04-11
JeecgBoot 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Cherry Studio 未标注 未标注 未标注 无 2026-05-17
mempalace 未标注 stdio · 本地进程 本地部署 有 2026-04-11

服务器档案

文档知识
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类文档知识本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

40.7 KB
来自项目仓库与上游目录的原文,未做删改

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```mermaid

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**.```bash
curl -fsSL &#x27;https://firekeep.ai/latest/install?src=github&#x27; | sh    # macOS / Linux
irm &#x27;https://firekeep.ai/latest/install.ps1?src=github&#x27; | iex      # Windows PowerShell

The server runs on linux/amd64 or linux/arm64 (server releases after v1.6.2;
v1.6.2 and earlier are amd64-only) and needs Docker Compose v2, two 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

  • Client Kit: configures Claude Code, Codex, Kiro, and OpenCode together;
    Claude Desktop is added when its config directory exists. Other MCP clients
    can use the generic path.
  • Claude Code: managed MCP, instructions, and lifecycle hooks. Its supported
    pre-tool hook can hard-block an edit, write, or shell action.
  • Codex: managed MCP plus AGENTS.md guidance. Codex exposes no native hooks,
    so lifecycle automation and pre-edit enforcement are not implied.
  • Kiro CLI: a named Firekeep agent with MCP, steering, and lifecycle hooks.
    On the validated Kiro CLI 2.12.1 surface, its pre-edit hook is advisory.
  • Firekeep Studio: runs Codex, Claude Code, Kiro CLI, and Grok in one desktop
    workspace. The direct Grok adapter has no Keep memory, hooks, or briefing;
    Studio reports that boundary instead of inheriting another runtime’s status.

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

Measured retrieval, with the method attached

On the accepted 2026-08-28 LongMemEval-S run, Firekeep achieved 97.7% Evidence
Recall@10
: at least one labeled evidence session appeared in the first ten
results for 459 of 470 scored questions. The measurement covers retrieval,
not generated-answer accuracy; it is one corrected deterministic run rather
than a multi-run confidence interval.

Methodology · Result data

The problem Firekeep solves

People do not build professional judgment by rereading every email, document,
ticket, or source file from the beginning. They remember what happened, why a
decision worked, how a failure was diagnosed, and which procedure held up in
practice. That experience changes how they approach the next problem.

Agents should improve the same way. Firekeep connects the knowledge, working
state, coordination, and evidence behind the work so the next agent can begin
with the experience the last one earned.

Detailed capability map

Capability · What it means
Memory · Agents remember what worked, what failed, and what matters across sessions. Semantic + graph retrieval, confidence scoring, contradiction handling, four memory types (reference / procedural / episodic / transient) with type-aware recall decay, recoverable archive-first aging, and token-conscious recall with optional LLM synthesis. Recall is re-ranked by recorded session outcomes (outcome-weighted memory) and by agent feedback on knowledge that was actually acted on (memory_feedback).
Knowledge Autopilot · The knowledge base maintains itself without deciding anything on its own. When two unconfirmed memories genuinely conflict, neither is silently dropped — both stay recallable, marked contested, until a human verdict (/memory/contested/resolve). A session reaper closes out crashed/walked-away sessions so failures count in outcome scoring. Every review queue (draft skills, stale skills, procedure proposals, contested pairs, eval dead letters) lands in one inbox with a weekly digest, and /memory/{id}/evidence shows every signal behind a memory's rank in one read.
Fleet-as-GPU (Night Shift) · The connected agents' own machines do the knowledge base's homework overnight, against a local model, and only ever produce drafts. The session-end hook queues a distill job per session; the server's nightly passes queue one job per stale skill (re-author it) and per contested memory pair (propose a verdict); firekeep night-shift drains the queue — started for you at session start whenever LM Studio or Ollama is listening. A human still activates every draft and resolves every pair, and an approval-rate ledger per job type on the Autopilot tab says whether the fleet's work is worth keeping.
Team Continuity · Memories carry verified workspace/member provenance plus an untrusted runtime agent_id label and project. Per-contributor activity reports and LLM-synthesized handoff briefs let one agent pick up where another left off.
Session Continuity · Plans, decisions, and progress recorded through the session tools survive context compression. Crashed sessions are auto-detected on next start and offered for resumption with a periodic workspace snapshot (git branch, recent commits, diff stats) embedded in the shadow.
Environment Awareness · Configured Docker, git, and file collectors monitor operational state instead of relying only on prompts. Container restarts, new commits, and file changes flow into a replayable event stream.
Agent Coordination · Shared channels, bulletin board, structured task queue, resource leases with monotonic fencing tokens, presence registry, and direct messages. Concurrent agents can assign work, track progress, and use leases to prevent overlapping edits; hook-enabled clients block an edit when another agent already holds the file lease.
Predict-then-Act Gateway · Agents declare intent before consequential actions (action_before → allow · rethink · block), then reconcile outcomes (action_after). Combines a runtime policy engine (lease, file risk, path deny, session health, recent failure) with a fast-path cache for repeated low-risk actions.
Skills · Agents author reusable "what to do when X happens" playbooks via the skill_create tool (client-side, with full session context); a docs→skills pipeline drafts more from wikis/runbooks under human review. Top matches are injected into the next session's briefing. (Server-side auto-synthesis exists behind SKILL_SYNTHESIS_ENABLED but is off by default — the CPU-only deploy can't run the generation LLM in workable time.)
Enforced Runbooks · A skill whose steps carry command matchers is a runbook a human can arm: advise (round-1 advisories), require_ack (a matched command is challenged and proceeds only after an audited acknowledgement — one-use permit bound to workspace, member, session, command hash, step, bundle version and execution), or block (fails closed, with a server receipt the client requires before honoring an allow). Evidence is scored by success — a step counts only when its command exits 0 — and every enforcement event lands in a deviation ledger (dashboard + inbox), storing command hashes, never command text. Modes are set by a human on an admin-only route; agents can propose runbooks, never arm them. Opt-in via PROCEDURE_ENABLED, currently being dogfooded on our own deploys — see docs/guides/living-procedures.md.
Decision Board · When a clarification needs more than a couple of questions, the agent opens a local browser board pre-populated with evidence retrieved from team memory — better questions, informed by what the team already learned. The local gateway fronts the Decision Board process and Cortex /decision/synthesize.
Living Instructions · The instruction layer measures itself: a per-instruction compliance table computed deterministically from replay (did sessions recall before answering, record as they went, declare consequential actions), with trend over time, per-runtime slices, and exposure receipts — sessions carry a content hash of the instruction text that actually reached them, and anything unverifiable reports as unknown rather than counted. Honest about its limits by construction: it measures behavior, not whether the behavior helped. Fleet-drafted rewrites under human verdict and A/B validation are roadmap.
Trust Ledger · A per-agent employment record built from the declarations agents already make through the gateway (action_before/action_after): declared-action count, reconciliation rate, prediction-match calibration (Brier over stated confidence vs reconciled outcome), reversals, sessions, first/last seen. Visibility only — it reports, it never gates. Honest by construction: calibration is behavior not competence, only declared actions are seen, agent_id is a self-reported label so the record is per declared identity, and calibration reads not enough signal below a threshold rather than inventing a number. The enforcing half (a capability broker turning the record into earned autonomy) is roadmap.
Auto-Evals + Pattern Discovery · Quality metrics computed from replay traces on session completion. Pattern detection is enabled; automated promotion/validation and A/B experiment endpoints are implemented but disabled by default until a deployment has enough session volume to use them responsibly.
Replay & Explainability · Every memory read/write, session lifecycle event, environment change, coordination action, and gateway decision is recorded as a structured trace. Inspect, narrow, and reconstruct context at any prior event.
Encrypted Secrets · Fernet-backed vault for infrastructure credentials, API tokens, and connection strings. Distinct from memory — secrets never appear in recall.
Business Knowledge · Ingest company documents (wiki pages, tickets, API docs) — manually, or via scheduled Confluence collectors. Chunks land in the vector store and surface naturally during memory recall alongside operational memories.
Code Intelligence · Tree-sitter-based symbol search, caller graphs, architecture maps, and impact analysis that returns symbol slices instead of whole files — runs client-side through the local gateway (firekeep-symdex is installed with the kit). 38 MCP tools (8 analytics tools hidden by default behind SYMDEX_ANALYTICS_ENABLED).

Why Firekeep Is Different

Firekeep is not another chatbot wrapper or prompt orchestration layer.

It is an operating layer for connected AI agents — infrastructure that sits behind your existing tools and makes them better.

  • Self-hosted by default. The server, datastores, embeddings, and default generation model run on your infrastructure. Third-party egress occurs only when you opt into a connector or external Symdex AI provider.
  • Deep where the work happens. Coding is the strongest shipped workflow, with Symdex for code intelligence. It is not the product boundary: Docdex brings selected document folders into the same Keep, Maildex brings a member's email (read-only IMAP, always member-private, firekeep maildex add), and the shared continuity, coordination, governance, and evidence layers are domain-independent.
  • Persistence + observability. Most agent tools focus on making the agent smarter in the moment. Firekeep focuses on what happens between sessions and after things go wrong.
  • MCP-native. Four remote services and two client-local backends expose Model Context Protocol tools through one local firekeep stdio gateway. Shipped adapters configure Claude Code, Claude Desktop, Codex, Kiro, and OpenCode; other MCP clients can be configured manually.
  • Agent-agnostic. Swap the agent client without rebuilding the underlying memory and coordination layer. Cursor has a documented manual MCP path; Aider does not currently have a shipped adapter.
  • A2A-discoverable. Relay publishes an Agent-to-Agent agent card at /.well-known/agent.json for capability discovery. This is discovery-only, not an A2A task-execution endpoint.

Installation and operations details

One command, two required questions: the agent identity every memory, session and
replay event is attributed to, and where your Firekeep server is — set one
up on this machine with Docker, redeem a join code, point at one that is
already running, or decide later (firekeep doctor then tells you how to
finish). Setting one up here runs firekeep init for you; that installer asks
nothing, and the machine enrols itself once the stack is up, so firekeep doctor is green with no dashboard, no tunnel, and no pasted key. It prints the
paste-ready command for your second machine when it finishes.

The installer then offers one skippable prompt for another MCP client's rules
file; the four shipped adapters are rendered either way.

Server images after v1.6.2 are published for linux/amd64 and linux/arm64, so
an x86-64 or ARM64 Linux host (e.g. AWS Graviton, Ampere) or Docker
Desktop on an Apple-silicon Mac runs them natively; v1.6.2 and earlier are
amd64-only. The client bootstrap is exercised in CI on
Ubuntu, Debian, Alpine, Fedora, Rocky, Arch and openSUSE (x86_64 and aarch64);
macOS runs the same script but is not covered by CI.

  • Requirements and sizing — firekeep.ai/docs.html#requirements
  • Server install — firekeep.ai/docs.html#server
  • Connecting agents and teammates — firekeep.ai/docs.html#connect
  • Troubleshooting — firekeep.ai/docs.html#troubleshooting

From this checkout```bash

bash install.sh # build the server from source
bash install.sh --pull # the same installer against the published images
cd client && ./install # the kit from this checkout (.\install.ps1 on Windows)
firekeep install # re-render the runtime adapters only


`install.sh` prompts for nothing: the host address is detected and the Neo4j
password generated (`--ip` / `--neo4j-password`, or `FIREKEEP_VPS_IP` /
`FIREKEEP_NEO4J_PASSWORD`, override either). It returns as soon as the stack is
up rather than blocking on the ~3.3 GB model pull — until that finishes, memory
writes return `status=&quot;partial&quot;` (stored and queued for backfill, not yet
searchable) and `firekeep doctor` carries an `embeddings` WARN row saying so.
`bash install.sh --wait-for-models` blocks instead.

Operating the server afterwards — access and authentication, the dashboard,
backups, updates, exposing ports deliberately — is
**docs/DEPLOYMENT.md**.

### Removing it```bash
firekeep uninstall            # remove the client kit from this machine
firekeep uninstall --server   # also tear down the server + ALL its data

firekeep uninstall removes only what the kit installed — the Firekeep blocks
in each runtime's config (your own settings stay intact), the launcher and its
PATH entry, and ~/.firekeep — and asks first (--yes skips the prompt). It
never touches a server you set up. --server additionally runs docker compose down -v on the stack this machine provisioned, deleting the Neo4j/Qdrant/Redis
volumes — every memory, session and secret, permanently — behind a separate
data-loss confirmation that a plain uninstall or --yes can never trigger. Back
up first (docs/DEPLOYMENT.md) if you
might want the data back.

Firekeep Studio

Download for Windows · Download universal macOS · Explore Studio →

studio/ is a separate desktop client for people who want Firekeep to be the
only agent application they open. It gives Codex, Claude Code, Kiro CLI, and Grok one
runtime-neutral conversation surface: any supported runtime can be the explicit primary,
other runtimes can review it in fresh read-only contexts, and /compare, /consensus,
an explicit shared workspace, Windows voice input and system voice output, cache-aware token guards, named and color-coded local sessions,
live provider model/reasoning discovery, and typed Client Kit controls are built in. The
selected runtime is visually explicit, the full inspector can be hidden, and Studio links
to the dashboard from the existing Client Kit connection without exposing its credentials.
Fenced Mermaid responses render as native zoomable diagrams, and the existing Firekeep
Decision Board opens as a native question/evidence/action panel inside Studio. Its local
authenticated push preserves the original long poll, avoiding an extra agent turn merely to
discover that the board is ready.
The primary runtime picker shows live readiness and transport context, response scrolling
respects readers who move away from the tail, and copy/paste uses bounded text-only native
clipboard operations. Completed answers lead each run while detailed working events fold into
a Work log. A runtime-neutral Agents view tiles Codex, Claude, Kiro, Grok, or any future
chat-capable adapter into selectable panes with independent native continuations; the shared
composer targets the selected pane, and active runs remain serialized for workspace safety.
Mission Mode adds an outcome-bounded harness: one primary
writer, deterministic local checks, bounded repair, independent review evidence, explicit
human acceptance, and a task result stored separately from every agent's prose.

Studio consumes provider-supported structured boundaries rather than scraping TUIs, keeps
provider authentication provider-owned (except OS-encrypted API keys), and continues to use
the existing Python Client Kit wherever a runtime's native configuration provides Keep memory,
hooks, policy, and connectivity. Runtime cards report that evidence explicitly; the direct xAI
Grok adapter is clearly marked as having no Keep memory rather than inheriting another runtime's
claim. The preview
build and installer commands, security boundaries, runtime matrix, and full / command
inventory are in the Studio README.

Studio 0.5 ships an x64 Windows installer and a universal macOS installer from an isolated,
signed release channel. Packaged builds check for Studio updates shortly after launch; Windows
downloads and installs a verified update on restart, while macOS uses native automatic updates
only when the release is Apple-signed and notarized. The current release page, checksums, and
both installers are published under
Firekeep Studio releases.

A Real Workflow

Here's what happens when an agent uses Firekeep:

1. Session starts. On runtimes with lifecycle hooks, the client fetches Cortex's aggregated GET /briefing first, including relevant memories, tasks, environment state, and skills. The agent then calls ctx_start_session(&quot;fix auth middleware bug&quot;); Bridge creates the durable session and the shim ties it to that briefing.

2. Code exploration. Instead of reading every file, the agent calls search_symbols(&quot;auth middleware&quot;) and get_callers(&quot;require_scope&quot;) on Symdex. It gets a targeted list of files and callers in milliseconds.

3. Environment check. Sentinel has been watching Docker. It detected that the cortex-api container restarted 3 times in the last hour and pushed an alert to Relay's #alerts channel. The agent sees this in its context.

4. Work happens. The agent edits files, runs tests, and records important progress with ctx_update. Bridge persists what was explicitly recorded. When the context window compresses, the agent calls ctx_get_shadow and gets that durable working state back — plans, decisions, progress, and file knowledge.

5. Session completes. The agent calls ctx_complete_session, optionally passing a structured self-grade — task_result (&quot;success&quot; / &quot;partial&quot; / &quot;failure&quot;, the TASK's outcome, not the RPC's) plus up to 10 short task_evidence claims backing it. The grade is accepted only from the session's verified owner and stored as that session's one authoritative, never-overwritten result. Bridge atomically marks the session complete and queues background distillation into episodic memory; failures retry and eventually move to a visible dead-letter queue. Auto-evals compute quality metrics from the replay trace — a session with no recognized grade reads as unknown rather than a guessed success, so outcome-driven scoring (Outcome-Weighted Memory, quality trends) never counts silence as a win. Next time someone works on auth middleware, the memories are there once distillation succeeds.

6. Something went wrong? Open the Replay tab in the dashboard. Load the session. See every action, every memory read, every decision point. Click on a failure event and run narrowing — it walks back through the causal chain to help identify the root cause.

Architecture```

Local Machine VPS
┌──────────────────────────┐ ┌────────────────────────────────────┐
│ Claude / Codex / Kiro / │ │ FirekeepCortex — Memory & RAG │
│ OpenCode / MCP client │ │ FirekeepBridge — Sessions │
│ │ │ │ FirekeepSentinel — Monitoring │
│ one firekeep gateway │◄──── MCP ───►│ FirekeepRelay — Coordination │
│ ├─ symdex (local) │ │ Dashboard — Web UI │
│ └─ decision (local) │── Browser ──►│ Neo4j · Qdrant · Redis · Ollama │
└──────────────────────────┘ └────────────────────────────────────┘
```

Symdex and the Decision Board run client-side as stdio-local MCP servers (installed with the kit) — Symdex must be local to the working tree it indexes, so it is no longer a VPS container.

The two arrows crossing that boundary are not publicly reachable by default.
Out of the box the VPS side listens on loopback and requires an API key, so the
local-machine half reaches it over an SSH tunnel, a private network, or an HTTPS
front end you deliberately configure. See
docs/DEPLOYMENT.md → Access and authentication.

Service What it does
FirekeepCortex Long-term memory. Semantic + graph RAG, archive/restore lifecycle, sleep-cycle consolidation, four memory types with type-aware decay, versioned memories with confidence scoring, automatic contradiction supersession, agent-authored skills (skill_create) + a docs→skills pipeline, and the Agent Gateway (predict-then-act surface).
FirekeepBridge Session persistence. Preserves working context (plans, decisions, progress, file knowledge) through context compressions. Auto-distills to Cortex on completion. Crashed-session detection with workspace-snapshot resumption. A session reaper abandons sessions idle past 72h so walked-away sessions register as non-successes in outcome scoring. Emits session lifecycle events to the replay stream.
FirekeepSentinel Environment observer. Docker health, git commits, file changes. Broadcasts alerts to Relay on errors. Container restarts, new commits, and file changes flow into a replayable event stream.
FirekeepRelay Agent coordination. Real-time pub/sub channels, persistent bulletin board, structured task queue, resource leases with monotonic fencing tokens, presence registry, direct messages, and an A2A agent card endpoint for external discovery.
Dashboard Web UI covering coordination, memory, diagnostics, devices, members, policy, vault, and operations.
Firekeep Studio Optional local desktop console and Mission harness for primary agents, deterministic verification, independent reviewers, Windows dictation, system voice replies, cross-runtime comparison, and Client Kit control. It is not a VPS service.

Code intelligence (FirekeepSymdex — 38 MCP tools, 8 analytics hidden behind a flag) and the Decision Board (firekeep-decision) run client-side as stdio-local MCP servers installed with the kit, not as VPS containers.

Shared modules (no extra containers): Replay Engine (structured trace log across all services), Auth (API key scopes), Vault (Fernet-encrypted secret storage), Corpus (business document ingestion → vector chunks; scheduled Confluence collectors), Auto-Evals (10 Tier-1 quality metrics + trend tracking + regression detection), Pattern Engine (strategy detection; promotion validation and A/B experiments are feature-flagged off by default), Policy Engine (compound pre-edit safety checks — lease, file risk, path deny, session health, recent failure), Agent Gateway (predict-then-act surface with fast-path cache for repeated low-risk actions), Skills (agent-authored via skill_create + docs→skills drafts under human review; server-side synthesis off by default), Memory Improvements (archive-first composite aging with preview/audit/restore, token budgets, LLM synthesis pass, embed input capped + shrink-to-fit).

> For the full design specification, see docs/DESIGN.md.

Dashboard

Access at http://localhost:8040 on the host, or through a tunnel from
elsewhere (docs/DEPLOYMENT.md → Reaching the dashboard).
It has its own basic-auth login (user
admin; the password is written once to dashboard/.htpasswd.cred). Behind
that, nginx injects the dashboard's API key on every backend call, so the SPA
works against the auth-gated stack without you pasting a key into the browser.

Tab What it shows
Overview Service health, quick stats, recent events and memories
Sessions Active/paused/completed/abandoned sessions, shadow context inspector
Events Sentinel event feed with source and severity filters
Relay Task queue, channels, bulletin board, direct messages, active claims/leases
Scope FirekeepScope clarification sessions — active screens, answer prompts
Memory Recall search, active/archive browsers, one-click restore, maintenance preview/audit, store form, contributors, namespace/tag stats
Skills Agent-authored + doc-derived skill cards — review, activate, edit, retire — plus the Living Procedures runbook cards: enforcement-mode badge and admin mode control, per-step observation stats, deviation view, and a NOT ACTIVELY ENFORCED warning when an armed runbook has no session holding the current bundle
Knowledge Docs→skills ingestion (paste / URL) + the draft-skill approval queue
Autopilot The review inbox (draft/stale/re-review skills, procedure proposals, runbook deviations, contested memory pairs with the fleet's proposed verdicts, eval dead letters), the "what changed this week" digest, the Living Instructions compliance table (per-instruction rates, trend, per-runtime slices, exposure states), the Trust Ledger card (per-agent declared/reconciled/calibration/reversals), and a Fleet table of per-job approval rates — read-only; it proposes and reports, never mutates
Patterns Discovered strategy cards; promotion validation and experiment controls when their feature flags are enabled
Ops Workers, queue depths, active agents, vector store info, Discipline counter (untagged memory calls)
Policy Runtime policy rules for pre-edit safety checks, toggle per rule
Vault Encrypted secret management (Fernet-backed, Redis DB 7)
Replay Session trace timelines, event inspector, root cause narrowing
Evals Aggregate quality metrics, per-session scorecards, quality trends
Devices Device credentials and single-use enrollment commands
Members People and single-use member invites

The dashboard is a zero-dependency static SPA. No build step, no npm, no framework.

Documentation

Document Contents
docs/DEPLOYMENT.md Running a server: access and authentication, updating, backups, troubleshooting, local development (installing is firekeep.ai/docs.html)
docs/CONFIGURATION.md All environment variables, Redis DB allocation, intelligence features
docs/MCP-TOOLS.md Complete MCP tools reference across the server and registered client-local backends; visible inventory varies by dex registration and feature flags
docs/DESIGN.md Full architecture specification, service contracts, integration points
docs/COMPARISON.md Feature-by-feature comparison vs. base Claude Code
docs/SETUP-CODEX.md Codex integration guide
docs/SETUP-CLAUDE-CODE.md Claude Code integration guide
docs/MULTI-AGENT.md Agent intelligence: pre-flight briefing, session debrief, multi-agent coordination
studio/README.md Firekeep Studio runtime matrix, commands, security model, development, and packaging

Tech Stack

Python 3.11 server services (client supports Python 3.10+) / FastAPI / FastMCP / Neo4j / Qdrant / Redis / Ollama / Docker Compose / tree-sitter / TypeScript / Electron / React

Server-side embeddings and generation default to local Ollama, so the default

…(正文过长,页面只展示前面部分,完整内容见仓库)

常见问题

6 问
答案由本站依据条目字段整理,不引用上游原文
Firekeep 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Firekeep 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Firekeep 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Firekeep 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

Firekeep 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Gemini CLI、Codex;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Firekeep 能提供哪些能力?

资料显示能力标签包括 记忆。具体工具清单以官方文档为准。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。