MCP connector for Snipara, the Project Brain for AI coding 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":"snipara-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.
# snipara-mcp [](https://pypi.org/project/snipara-mcp/) [](https://www.python.org/downloads/) [](https://opensource.org/licenses/MIT) [](https://github.com/alopez3006/snipara-mcp/actions/workflows/ci.yml) `snipara-mcp` is the lightweight stdio MCP connector for the Snipara Project Brain. **Snipara is the Project Brain for AI coding agents.** Use it when an MCP client needs a local stdio process that talks to Snipara's hosted Project Intelligence APIs. Snipara gives Claude Code, Cursor, Codex, and other MCP clients the decisions, active work, code impact, proof, and handoffs they need before they edit. If your client supports streamable HTTP MCP directly, prefer the hosted endpoint and skip the local process. ## What Is Snipara? Snipara is the shared Project Intelligence layer for AI-assisted software work. It gives Claude Code, Cursor, Codex, OpenAI Agents, and other MCP-compatible clients project context that survives sessions, users, tools, and model switches. Your agent still uses its own LLM. Snipara gives it the right project context: source-backed docs, reviewed memory, shared guidance, workflow continuity, and code graph structure. In category terms, it is an AI coding agent context, memory, and continuity platform. ## Why MCP? MCP is becoming a standard adapter layer for agent tools. `snipara-mcp` makes Snipara available through that layer without forcing developers into a specific IDE, model, or orchestration framework. The integration should feel small: ```bash uvx snipara-mcp ``` The impact is larger: agents can retrieve durable project context instead of starting cold every session. ## What It Unlocks | Need | Snipara MCP tool group…
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.