KIP MCP server

KIP 2.0 — Cognitive State Protocol for Agent Memory

English | 中文

Status

Default development version: KIP 2.0 — normative draft. The repository root contains the current protocol and tooling. KIP v1.0-RC11 is frozen for historical reference and migration; changing the default does not upgrade existing deployments or declare the 2.0 protocol stable.

The 2.0 scope is frozen. This revision made the draft a better memory rather than a larger contract: a world change is one Assertion (temporal succession), coarse dates are time bounds instead of invented instants, preferences change within their kind, a standard policy (kip:memory-default) resolves everyday conflicts the same way on every engine, a Brain can add a relation it meets through the Space's draft vocabulary (DEFINE), retrieval composes with belief in one query (the Search Pattern), and fired Watches reach the business Agent through attention recall. It also took things away: draft packages are not retained (one cognitive-memory@2.0.0), writable caches became computed views, the Cognitive Consistency companion was folded into the Specification, trials and durable workers moved into optional brain/ companions, and the Preference type is gone — a preference is a claim. A second review pass closed the edges of the new semantics: a claim with no stated start began no later than it was made, asserted_at is when the claim was made rather than when it was recorded, two inferences never succeed one another, and the standard policy decides remaining conflicts by recency. See the revision record.

The Rust and Cloudflare Durable Object engines target KIP 2.0 drafts. Their shared suite now lives here as the executable engine suite; both pass every case of the current suite, including the draft vocabulary, supersession scope, computed strength and ingestion batch fixtures (anda-db 985451b), so no fixture is pending_engine. The protocol remains 2.0-draft, independently of tooling versions, and no real Brain learning result is claimed by structural tests.

Start here

• Agent integration: Memory Interface and the Agent memory card.
• Protocol implementation: Specification, syntax reference, and conformance checks.
• Developer tools: TypeScript language toolkit and VS Code extension, both targeting KIP 2.0.
• Existing v1 users: frozen archive, deployment migration, and repository path changes.

The archived MCP server and Skill implement v1 interfaces; native v2 integration starts with the current Interface and wire contracts above.

An interactive version — pan, zoom, relationship tracing, five guided views — is a self-contained file: download it and open it in a browser.

Shortened. The full README is on GitHub.