Give any AI assistant real architectural understanding of a codebase — local, private, zero-config MCP server.
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":"mcp-architect","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.
# 🏛️ mcp-architect > **Stop pasting your file tree into Claude.** Give any AI assistant *real* architectural understanding of a codebase — **local, private, zero‑config.** [](https://pypi.org/project/mcp-architect/) [](LICENSE) [](https://www.python.org/) [](https://modelcontextprotocol.io/) <p align="center"> <img src="docs/demo.svg" alt="mcp-architect — Claude analyzing a repository's architecture, dependency graph, and hotspots" width="680"> </p> AI coding assistants are great at *files* but blind to *architecture*. Every session you re‑explain the structure, paste the file tree, and hope it guesses your module boundaries right. **mcp-architect** is an [MCP](https://modelcontextprotocol.io/) server that hands your assistant a structured map of any codebase — tech stack, dependency graph, hotspots, and module summaries — computed **100% locally** with **no API keys and no model required**. It works with **Claude Desktop, Cursor, Windsurf, Cline**, or any MCP client. --- ## Why | Without mcp-architect | With mcp-architect | |---|---| | "Here's my file tree, please figure out the structure…" | `architecture_overview` → stack, entry points, structure in one call | | AI guesses how modules relate | `dependency_graph` → real import graph + circular‑dependency detection | | "Which files matter?" | `hotspots` → largest, most complex, most‑changed, highest‑risk | | Re‑explaining a package every time | `explain` → classes, functions, and deps of any folder | Everything runs on your machine. Your code never leaves it. --- ## Quickstart ### Install ```bash pip install mcp-architect ``` …or skip the install entirely and let your MCP client fetch it on demand with `uvx` (shown below). ### 1. Ad…
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.