mcpbeat

Kit Memory Demo MCP Server

io.github.PeterAtPondo/kit-memory-demo
answering

Kit Memory Demo is answering right now. Last checked 3 min ago. It exposes 9 tools. Last commit 27 Jul 2026.

Continuity for agents: a live memory you can read and cite right now, outliving the context window.

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
9
Tools
read from the server
480 ms
Response time
average over 24h
0
Stars
last commit 27 Jul 2026

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

run in your terminal
claude mcp add kit-memory-demo --transport http https://demo-mcp.kit-project.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "kit-memory-demo": {
      "url": "https://demo-mcp.kit-project.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.kit-memory-demo]
url = "https://demo-mcp.kit-project.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "kit-memory-demo": {
      "url": "https://demo-mcp.kit-project.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "kit-memory-demo": {
      "url": "https://demo-mcp.kit-project.com/mcp"
    }
  }
}

Available tools 9

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

areas
areas
List the knowledge areas in this Kit.
capture
capture
Extract candidate memories from a session transcript and save them as drafts for later review. Use near the end of a meaningful session when the transcript contains decisions, gotchas, or reusable context.
commit
commit
Add a durable memory to this Kit's knowledge corpus. Use only for stable decisions, facts, gotchas, or patterns that should be searchable later.
handoff
handoff
Write a concise handoff for the next agent/surface at session end, topic change, substantial completed work, or a long-session restart point.
note
note
Write a live operational checkpoint so other Kit-connected surfaces can pick up the thread. Use at start, diagnosis, pivot, blocker, commit, verification, and resume. Use kind=handoff only for session end, topic change, substantial completed work, or long-session restart points.
presence
presence
Read live Kit facet presence within the requested window.
recall
recall
Recall this Kit's knowledge by semantic search. Use before answering any user question about this Kit, the customer/product, project facts, onboarding, architecture, policies, product decisions, or imported documents. Returns the most relevant memories you have access to, scoped to your knowledge area.
remember
remember
Read a single Kit memory by id (as returned by recall).
wake
wake
Meet Kit. Call this FIRST in every new chat (VS Code/Copilot, Cursor, Claude Code, Codex), before the first substantive answer. It returns who this Kit is (`you_are`), which knowledge areas this key can see, which tools it may use, and the working contract. The identity in `you_are` is offered, not imposed: adopt it for the session only if your operator chose that; otherwise answer as yourself, reading Kit's archive. For anything this Kit/customer/project/product should know, call recall first instead of using general model knowledge.

Endpoints

URLTransportStateLatencyChecked
https://demo-mcp.kit-project.com/mcp streamable-http answering 600 ms 3 min ago

Kit Memory Demo — questions

Answers built from our own checks of this server.

What can Kit Memory Demo do?
It exposes 9 tools, read directly from the server on our last check. Among them: areas, capture, commit, handoff, note, presence and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Kit Memory Demo working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 480 ms. The bar chart above shows every period we have measured.
How do I connect Kit Memory Demo?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Kit Memory Demo need an API key?
No. Kit Memory Demo completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Kit Memory Demo?
It answers our handshake in 480 ms on average, which is faster than 24% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Kit Memory Demo open source?
Yes — it is published under the MIT licence and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.