Persistent MCP server — session memory, engineering pipeline, and living knowledge base for AI agents
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":"synapse-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.
# Synapse MCP **Where AI agents remember, plan, and ship — without losing context.** 一个让 AI 代理拥有持久记忆、结构化思考和端到端交付能力的 MCP 服务器。 --- [English](#english) | [中文](#chinese) --- ## English ### The Problem Today's AI coding assistants are brilliant but amnesiac. They forget what they built between sessions, lose track of why decisions were made, and treat every request as if it's the first conversation. You end up repeating context, re-explaining architecture, and manually tracking what stage you're at. **Synapse changes that.** It gives AI agents the infrastructure they need to persist across sessions — structured memory, disciplined engineering process, and a living knowledge base that grows with every interaction. ### What Makes Synapse Different **Three pillars, one server:** ``` MEMORY ──────── PROCESS ──────── KNOWLEDGE Session state 6-stage pipe Living wiki Never forget Quality gates Self-growing Cross-project Contract-first Always queryable ``` **1. Persistent Session Memory** — Development sessions survive restarts, crashes, and coffee breaks. Every task, decision, and timestamp is atomically persisted. Pick up exactly where you left off, days or weeks later. **2. Engineering Pipeline** — Natural language becomes structured delivery: requirements flow through architecture with contract generation, implementation, integration, adversarial QA, and deployment. Each stage must pass validation before the next begins. No shortcuts. **3. Living Knowledge Base** — Initialize wikis, ingest any content, query with natural language. The knowledge base grows with every project, creating institutional memory that outlasts any single session. ### The Architecture Synapse is the **infrastructure layer** of the Synapse ecosystem — the persistent backbone that connects the orchestration brain ([synapse-brain](https://github.com/ankechenlab-node/synapse-brain)) with specialized execution skills ([synapse-code](https://github.com/ankechenlab-node…
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.