Kit Memory Demo

io.github.PeterAtPondoPublished by GitHub account PeterAtPondov1.0.1Updated Nov 2, 2026

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

The publisher's own server: demo.st

VerifiedStreamable HTTPWeb executableKnowledge & MemoryAI & ML

Overview

AI-generated overview

Hosted, read-only demo MCP server exposing a fictional regency archive ("Lady Whiskerdown") that an assistant can search, cite and question.

What you can do
  • Open the archive and see what it is, which knowledge areas the key can read and which tools it may use
  • Search the archive and read individual memories by id, citing each as (Lady Whiskerdown:m#N)
  • List the knowledge areas available in this archive
  • Set a write focus (knowledge area and project) that holds until changed or idle past a TTL
  • Check live facet presence within a time window
  • Query connected business systems (accounting, HR, a shop) for current records
When to use it
Useful for trying out agent memory and citation workflows against a small, deliberately fictional corpus that no model was trained on, so a correct citation proves retrieval. Also handy for demonstrating scoped read access and for replayable memory benchmarks.
Requirements
A remote streamable HTTP endpoint; no local install or package. A bearer token in the Authorization header is required; the README says the keys are deliberately public and rotate without notice, with the current value printed in each kit's llms.txt map. No signup or environment variables.
Before you install
The README publishes bearer keys in plain text and states they rotate without notice, so calls may start failing until the key is re-read. The servers are described as read-only museum copies, yet tools such as focus and remember are exposed, so confirm what actually writes before relying on it. Queries and content go to a third-party hosted service.

Installation

In SourceWeft

  1. Open Kit Memory Demo in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.PeterAtPondo%2Fkit-memory-demo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "kit-memory-demo": {
      "type": "http",
      "url": "https://demo-mcp.kit-project.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

Kit memory demo · hosted MCP servers

Three live, public, read-only MCP servers, each backed by a running Kit. Kit is an identity substrate for AI agents: not another agent, not a memory API, but the durable, local-first self beneath your tools, holding memory with provenance and context that outlives any context window, consolidating while it dreams. It has no chat window of its own; it lives under the ones you already use. Point your agent at them and ask questions the model cannot answer from training. No signup; the bearer keys below are deliberately public.

serverendpointwhat it holds
Lady Whiskerdown (the Society Papers)https://demo-mcp.kit-project.com/mcpAn invented regency world seen from the ballroom. 118 memories. Half of a mystery.
The Area Cat (The Mews)https://mews-mcp.kit-project.com/mcpThe same town from below stairs. 88 memories. The other half.
The ballast case filehttps://real-mcp.kit-project.com/mcpA real five-year engineering decision (OpenTelemetry Collector's memory ballast), every entry with its GitHub source URL. 65 memories.

Why fiction: none of it exists in any training corpus, so a correct citation is provably retrieval. Why the two archives are separate servers: the central mystery (who leaked the Fluffington affair?) was split across them on purpose; no single entry states the answer, the full corroborated case assembles only across both, and your agent is the bridge. Why the real one: so the same machinery is checkable against the living public record.

Quickstart

Claude Code:

bash
claude mcp add --transport http kit-papers https://demo-mcp.kit-project.com/mcp \  --header "Authorization: Bearer kbr_live_Kh9eO_ZfLldveFf1KXJEEvepfOpdgRqf7KoDDU3rB18"claude mcp add --transport http kit-mews https://mews-mcp.kit-project.com/mcp \  --header "Authorization: Bearer kbr_live_UN8-2LUlKmP2uxWQB5vpn-fzkJIuRb5zmq-apQeTU7U"claude mcp add --transport http kit-case-file https://real-mcp.kit-project.com/mcp \  --header "Authorization: Bearer kbr_live_ISWsqW39NkqT659FEkQjv0OjJDmyD4O3wx3wcCfA03c"

Any MCP client: see examples/mcp.json.

Then tell your agent: "Call wake on each server, then work out who leaked the Fluffington affair, and cite every step." Or the real-world flagship: "Should we still use the memory_ballast extension, and why did the recommendation change?"

Keys rotate without notice. The authoritative copy of each key is printed in that kit's own map: demo llms.txt, mews llms.txt, real llms.txt. If a call starts failing, re-read the map.

No MCP client? No problem

Every kit also serves keyless HTTP GETs (search, read, graph pivot), documented in its llms.txt. A browser-only version of the whole exam runs at demo.kit-project.com/investigate.

Scoped access, demonstrated

The papers kit also publishes the apprentice key, a deliberately narrowed credential (allowed_areas: columns): the same kit through a smaller window. Run the same leak query with the full key and with the apprentice key and watch the private journals vanish from the answers. That mechanism, a company kit sharing one knowledge area with a contractor's agent, is enforced in the read path, not in copy. Current apprentice key, same rotation rule:

kbr_live_FoAauFWl7_IoDswh8rJrFvCw2qnblQTOF8DuSBkbj7A

What these servers are, honestly

Read-only museum copies of Kit substrates: hybrid semantic + keyword recall, typed knowledge graphs (including supersedes edges that keep replaced truth citable), source artifacts with real URLs, and honest empty results when nothing is held. They demonstrate read-time behavior; a full Kit also writes, consolidates while it sleeps, and hands off between sessions on your own machine. There is a replayable benchmark built on these exact servers: kit-memory-eval.

The build story: kit-project.com/blog, note No. 022 in particular. The product: kit-project.com, local-first, invite beta.

License

MIT (code and examples in this repo). The demo worlds themselves are licensed with the benchmark: see kit-memory-eval's DATA-LICENSE.

Source: README.md at commit f8e833b

Tools

8

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.

Parametersareaprojectkit_session_id

presence

Reading presence

Read live Lady Whiskerdown facet presence within the requested window.

Parameterstoscopemessagekit_session_idwindow_minutes

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.

Parameterstoolsystemargumentskit_session_id

ranking_compare

kit_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.

Parameterstierlimitqueryrequiredprojectsurfacecategorykit_session_id

recall

Finding things

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.

Parameterslimitqueryrequiredkit_session_id

remember

Reading a memory

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.

Parametersidrequiredkit_session_id

areas

List the knowledge areas in this Lady Whiskerdown.

Parameterskit_session_id

wake

Getting up to speed

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.

Parametersscopekit_session_id

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Demo integrations