MCP server for AI agents to manage project execution context
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"ccontext-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ccontext-mcp — Execution Context for AI Agents **English** | [中文](README.zh-CN.md) | [日本語](README.ja.md) Local-first MCP server that gives agents a **shared, durable “execution context”** across sessions: **Vision** (why) · **Sketch** (static blueprint) · **Milestones** (timeline) · **Tasks** (deliverables) · **Notes/Refs** (knowledge) · **Presence** (who’s doing what). **🧠 Persistent agent memory** • **📋 Agent-native task tracking** • **🧹 Built-in hygiene (diagnostics + lifecycle)** • **⚡ Batch updates (one call)** • **🔒 Local files, zero infra** [](https://pypi.org/project/ccontext-mcp/) [](https://pypi.org/project/ccontext-mcp/)  --- ## 🖼️ ccontext at a Glance ### Files on disk (portable, git-friendly) ``` your-project/ └── context/ ├── context.yaml # vision, sketch, milestones, notes, references (+ embedded contract) ├── tasks/ │ ├── T001.yaml # deliverable tasks with steps │ └── T002.yaml ├── presence.yaml # runtime status (recommend gitignore) ├── .ccontext.lock # lock file (recommend gitignore) └── archive/ # auto-archived notes/refs/tasks (optional gitignore) ``` ### One call to “load the brain” `get_context()` returns **version + now + diagnostics** so agents can quickly orient: ```jsonc { "version": "abc123def456", "now": { "active_milestone": { "id": "M2", "name": "Phase 2", "description": "...", "status": "active" }, "active_tasks": [{ "id": "T001", "name": "Implement auth", "milestone": "M2" }] }, "diagnostics": { "debt_score": 2, "top_issues": [{ "id": "NO_ACTIVE_MILESTONE", "severity": "info", "message": "No active milestone." }] }, "context": { "...": "vision/sketch/milestones/notes/references/tasks_summary" } } ``` --- ## Why ccontext? (Pain → Payoff…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.