Archprint — TypeScript MCP server: architecture rules with evidence
Scans a TypeScript repo, finds the architecture rules the code already follows, and shows evidence for each one. Turns trusted rules into ESLint and dependency-cruiser checks.
claude mcp add archprint -- npx -y archprintWhat Archprint does
Archprint reads a TypeScript project and extracts the rules its code actually obeys. Each rule comes with proof: how many files follow it, which ones break it, and how confident the inference is. A rule like "routes never touch the database directly" gets backed by the list of offending files.
The init, wire, and eject commands convert found rules into ESLint and dependency-cruiser checks. wire adds one line to the ESLint config, so a violation gets caught on the next lint run. eject restores the project exactly as it was.
The MCP server only reports. Enforcement stays in the linter. An agent like Claude Code or Cursor can ask Archprint for project rules with evidence before writing code. On a 70-file demo repo, asking for rules through Archprint cost $0.037 versus $0.083 without it, and the answer took 10 seconds instead of 17 — the agent reads ready-made rules rather than the whole repository.
Node.js with npx is required. The server runs locally and works with Claude Code, Codex, Cursor, GitHub Copilot, Windsurf, Cline, Zed, and Gemini CLI.
What it helps with
- find unwritten architecture rules in a TypeScript codebase
- attach evidence to every rule: follower count, breakers, confidence
- generate ESLint rules from patterns the code already demonstrates
- catch rule breaks in a pull request, not weeks later in review
- let AI agents fetch project rules with evidence before writing code
Example prompts for the agent
- Ask Archprint what architecture rules this repo follows
- List the enforced and held-for-review rules
- Check my change against the rules with Archprint
How to install Archprint
Platform CLI
claude mcp add archprint -- npx -y archprintPlatform CLI
codex mcp add archprint -- npx -y archprintConfig file
{
"mcpServers": {
"archprint": {
"command": "npx",
"args": [
"-y",
"archprint"
]
}
}
}Config file
{
"servers": {
"archprint": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"archprint"
]
}
}
}Platform CLI
gemini mcp add archprint npx -y archprintStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about Archprint
How do I install Archprint in Claude Code?
Run claude mcp add archprint -- npx -y archprint. The agent can then call Archprint tools over MCP.
What does Archprint do?
It scans a TypeScript project and finds the architecture rules the code already follows. Every rule comes with evidence: how many files follow it, which break it. Found rules can be turned into ESLint and dependency-cruiser checks.
How is Archprint different from CLAUDE.md instructions?
CLAUDE.md is guidance; lint rules are enforcement. Archprint generates enforcement from patterns the codebase already shows, instead of hand-authoring rules.
