Developer · Local MCP server
Context Foundry
Recursive Claude spawning for autonomous project builds with self-healing test loops.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.context-foundry/context-foundry- Version
- 2.2.1
- Status
- Active
- Category
- developer
- Transport
- stdio (local process)
- Package
- PyPI
- Published
- 2025-11-25
- Updated
- 2025-11-25
- Publisher
- context-foundry (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/context-foundry) · how
- Repository
- github.com/context-foundry/context-foundry
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| PyPI | context-foundry | 2.2.1 | stdio |
How to connect Context Foundry
Context Foundry runs locally from a Python package published to PyPI: context-foundry version 2.2.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx context-foundry. It reads the environment variable ANTHROPIC_API_KEY (required, secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"context-foundry": {
"command": "uvx",
"args": [
"context-foundry"
],
"env": {
"ANTHROPIC_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Context AutopilotMines your Claude Code and Cursor sessions into evidence-based CLAUDE.md / AGENTS.md rules. | Local · stdio |
| Context CloudPersistent AI memory with shared team workspaces, typed knowledge chunks, and cross-tool support. | Remote & Local · SSE, stdioLive check: sign-in required |
| Context EngineCompress logs, retrieval chunks, and code context into structured LLM-ready signal. | Local · stdio |
| Context FirewallLocal MCP proxy: collapses N servers' tools into 4 meta-tools and compresses large tool outputs. | Local · stdio |
| Context ProxyMCP proxy that lazy-loads tool schemas to cut context token overhead by 6-7x. | Local · stdio |
| context-doctorProfile LLM context: token breakdown, wasted-context findings and fixes for chats and agents. | Local · stdio |
| Context7docs MCPA paid remote MCP for Context7 MCP docs, built to return verdicts, receipts, usage logs, and audit-r. | Remote · HTTPLive check: ✗ no handshake |
| ContextaPersistent memory and knowledge graph for AI assistants - keyword + vector + graph search. | Remote · HTTPLive check: sign-in required |