Kit Memory Demo MCP Server

by peteratpondo Your server? Claim it

answering

Kit Memory Demo is answering right now. Last checked 13 min ago. It exposes 8 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 91 days of history · worst day 99%

91 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

451 ms

Response time

average over 24h

Stars

last commit 27 Jul 2026

What changed 44

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 18 August 2026. No other catalogue keeps this.

14 Oct a tool description was rewritten recall

13 Oct a tool changed the parameters it asks for remember

7 Oct a tool appeared systems

30 Sep 2 tool descriptions were rewritten recall, wake

30 Sep 2 tools changed the parameters they ask for recall, remember

11 Sep 7 tools changed the parameters they ask for areas, focus, presence and 4 more

9 Sep 4 tools disappeared capture, commit, handoff and 1 more

9 Sep a tool appeared ranking_compare

9 Sep a tool changed the parameters it asks for presence

27 Aug 2 tools changed the parameters they ask for commit, note

and 22 more, back to 18 August 2026

Tools have disappeared from this server

A tool that vanishes takes a piece of your agent with it, and the change arrives silently. Watch this server and every such change lands in your inbox.

Connect this server

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

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add kit-memory-demo --transport http https://demo-mcp.kit-project.com/mcp

Settings → Connectors → Add custom connector, then paste this address

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

{
  "servers": {
    "kit-memory-demo": {
      "type": "http",
      "url": "https://demo-mcp.kit-project.com/mcp"
    }
  }
}

Available tools 8

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 Lady Whiskerdown.

focus

focus

Set this operator's write focus: the knowledge area new memories are stored under, and optionally the project being worked on. The wake card's chips call this; it is also callable directly. Holds until changed or idle past the TTL; explicit area/project args on commit/note/handoff still win.

presence

presence

Read live Lady Whiskerdown facet presence within the requested window.

ranking

ranking_compare

Compare search ranking for a query with and without the recently learned boost. Returns every row whose rank or score changes, with baseline rank, boosted rank, position delta, score delta, sample source, boost window, and units.

recall

recall

Search Lady Whiskerdown's archive. Use it first for anything Lady Whiskerdown should know. Returns the most relevant entries this key can read; cite each one you use as (Lady Whiskerdown:m#N) with its title.

remember

remember

Read a single Lady Whiskerdown memory by id (as returned by recall). No graph or entity enrichment: the receiver endpoint returns the memory itself, scoped to this key.

systems

systems

Ask the business systems Kit is connected to (accounting, HR, a shop) live: its own and those of Kits linked to it. Kit's memories hold the history, decisions and who owns what; a system holds today's records. For a question about a customer, a person or an order, recall first, then ask the system for the current figures; recall names the record to ask for when Kit knows them. With nothing it lists the systems; with system, a tool's arguments; with system and tool, it runs that tool. Say when the answer was asked, and never save it as a memory: it will change.

wake

wake

Open Lady Whiskerdown, an archive you can question. Call this first in every new chat (VS Code/Copilot, Cursor, Claude Code, Codex), before the first substantive answer. It returns what Lady Whiskerdown is (`you_are`), which knowledge areas this key can see, which tools this key may use, and any rules its keeper has set. Lady Whiskerdown has no persona: keep your own identity and refer to it in the third person. For anything Lady Whiskerdown should know, call recall first instead of using general model knowledge.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

capture

removed 9 Sep 2026

commit

removed 9 Sep 2026

handoff

removed 9 Sep 2026

note

removed 9 Sep 2026

Endpoints

URL	Transport	State	Latency	Checked
https://demo-mcp.kit-project.com/mcp	streamable-http	answering	356 ms	13 min ago

Alternatives to Kit Memory Demo

same job, measured the same way

LLMSlim memory

by thanatos9404

Long-term memory and context fitting for agents, with no LLM in the loop. Local SQLite.

1 008 installs/wk local only

Reef

by reefwith

Shared, living memory for you and your people — coves your AI assistant can read and write.

answering

LogRack

by lograck

Shared memory for your AI tools: tasks, notes and context every tool can read and write over MCP.

answering

Agent Memory MCP

by xultrax-web

Markdown memory for AI agents. Files you can read, edit, grep, and commit. Not a database.

191 installs/wk local only

AgentContinuity

by agentcontinuity

Private memory, scratchpads, context export/restore and task handoff for AI agents.

55 tools answering

Cuemap MCP

by cuemap-dev

Local memory and context retrieval for AI agents through CueMap.

87 installs/wk local only

Agent Memory MCP

by ipiton

Memory, docs, and repo context layer for engineering agents.

local only

DJ Claude

by p-poss

Agents can now live code music for you, themselves, and each other while they work.

127 installs/wk local only

Kit Memory Demo — questions

Answers built from our own checks of this server.

What can Kit Memory Demo do?

It exposes 8 tools, read directly from the server on our last check. Among them: areas, focus, presence, ranking_compare, recall, remember and 2 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 451 ms. The bar chart above shows every period we have measured.

Did Kit Memory Demo ever remove tools?

Yes. capture, commit, handoff, note are no longer exposed — we recorded the date each one disappeared. A tool vanishing usually means a breaking change for anything that depended on it.

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 in the form 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 8 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 451 ms on average, which is faster than 28% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Kit Memory Demo open source?

The code is open source: it is published under the MIT licence and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at demo-mcp.kit-project.com, which runs on its operator's own terms.