A side-by-side look at the Architecture Intelligence Platform and MCP Architect MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Architecture Intelligence Platform for developer tools work over a hosted endpoint; choose MCP Architect for developer tools as a local process. You can also run both side by side in one mcpServers block.
architecture_overview, dependency_graph, impact_analysis.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 39/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | No auth required |
| Pricing | Free | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 8 | 3 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 5 |
| Full listing | View Architecture Intelligence Platform | View MCP Architect |
No tool names declared yet. Check the project README from the listing page.
architecture_overviewLanguages, frameworks, ecosystems, size, top‑level structure, entry pointsdependency_graphInternal import graph, architectural hubs, **circular dependenciesimpact_analysisWhat breaks if you change X** — direct importers + transitive blast radius, hub riskhotspotsLargest / most complex / most‑changed (git) / highest‑risk filesexplainDeep‑dive a folder or file: classes, functions, external depsPaste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"architecture-intelligence-platform": {
"url": "http://localhost:8000/mcp"
}
}
}
{
"mcpServers": {
"kannajune-mcp-architect": {
"command": "uvx",
"args": [
"mcp-architect"
]
}
}
}