Deterministic repo architecture maps: auth coverage, blast radius, readiness score, diagrams
Archiet MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. Deterministic repo architecture maps: auth coverage, blast radius, readiness score, diagrams.
X-Ray extracts the actual architecture of any repo — deterministically, no LLM, code never leaves your machine — and gives it to both you (an interactive map) and your AI agent (an MCP server + context pack).
Once Archiet is connected, these are the calls the assistant has available:
Findings — hardcoded secrets, raw SQL bypassing the ORM, auth tokens inGraph — module dependency edges, fan-in/fan-out, blast-radius hotspotsThird — party sharing: none.** X-Ray makes zero network calls (stdlib-only,Contact — ** aniekan.okono@archiet.dev — or open an issue on this repoFile — What it isARCHITECTURE.md — Human-readable map: module dependency graph (Mermaid), domain model, every route with auth status, dependency hotspots, risk findingsAGENT_CONTEXT.md — Drop into your CLAUDE.md / rules file — makes Claude Code, Cursor, and Windsurf respect your architecture todayarchitecture.json — The machine-readable model (the "repo genome")Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Among the database access options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Archiet's toolset — Findings, Graph, Third and 5 more — is a fair guide to whether it matches your workflow. It is maintained by Anioko; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Findings | hardcoded secrets, raw SQL bypassing the ORM, auth tokens in |
| Graph | module dependency edges, fan-in/fan-out, blast-radius hotspots |
| Third | party sharing: none.** X-Ray makes zero network calls (stdlib-only, |
| Contact | ** aniekan.okono@archiet.dev — or open an issue on this repo. |
| File | What it is |
| ARCHITECTURE.md | Human-readable map: module dependency graph (Mermaid), domain model, every route with auth status, dependency hotspots, risk findings, production-readiness scorecard |
| AGENT_CONTEXT.md | Drop into your CLAUDE.md / rules file — makes Claude Code, Cursor, and Windsurf respect your architecture *today* |
| architecture.json | The machine-readable model (the "repo genome") |
{
"mcpServers": {
"archiet-xray": {
"command": "uvx",
"args": ["archiet-xray"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.