Architecture governance for AI agents: query the live model, get target patterns, check files.
Architecture governance for AI agents: query the live model, get target patterns, check files. The archsteer mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 11 defined tools rather than through you.
AI agents now write code faster than any architect can review, document, or govern it. Docs rot instantly, the real architecture is invisible, structural decisions get made silently, and intended architecture drifts with every edit. ArchSteer is the always-current architecture system of record + governance plane: it derives the real architecture from code, keeps living docs and ADRs auto-built, surfaces every major decision for the architect to ratify, enforces declared intent as code-level fitness functions, and steers AI agents to conform instead of replicating local slop.
Everything the assistant can do here goes through one of these:
current_architecture — component/layer counts, conformance/drift, the declared targetget_target_pattern — the invariants that apply to a file, before you write to itcheck_file — whether a file you just edited conforms, without waiting for CIShipped — cloud control plane (Next.js + Supabase): multi-repo situation room withLater — a VS Code extension (inline diagnostics, status-bar score — the CLI/MCPPack — Detected byjava-spring — pom.xml / build.gradlesalesforce — sfdx-project.json / force-apppython-service — pyproject.toml / requirements.txtnextjs-app-router — package.json has next, an app/ dir, no expressexpress-to-next — package.json (fallback, or express present)Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Archsteer's toolset — current_architecture, get_target_pattern, check_file and 8 more — is a fair guide to whether it matches your workflow. It is maintained by einvoice-dev1; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| current_architecture | component/layer counts, conformance/drift, the declared target. |
| get_target_pattern | the invariants that apply to a file, *before* you write to it. |
| check_file | whether a file you just edited conforms, without waiting for CI. |
| Shipped | cloud control plane (Next.js + Supabase): multi-repo situation room with |
| Later | a VS Code extension (inline diagnostics, status-bar score — the CLI/MCP |
| Pack | Detected by |
| java-spring | pom.xml / build.gradle |
| salesforce | sfdx-project.json / force-app |
| python-service | pyproject.toml / requirements.txt |
| nextjs-app-router | package.json has next, an app/ dir, no express |
| express-to-next | package.json (fallback, or express present) |
Or in JSON config directly:
```json
{ "mcpServers": { "archsteer": { "command": "uvx", "args": ["archsteer", "mcp"] } } }Configuration as documented by the project. Restart the client after saving.
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.