GitHub
by github
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Computer or cloud★ 34,245MITUpdated 4 days ago
Install
Archprint
Overview
Description from the maker (original English)
Mine the architecture rules your TypeScript repo already enforces, with the evidence attached.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Developer tools
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"archprint": {
"command": "npx",
"args": [
"-y",
"archprint",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add archprint -- npx -y archprint mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"archprint": {
"command": "npx",
"args": [
"-y",
"archprint",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"archprint": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"archprint",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Tommkruix, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Developer toolsi
- More stars than 0% of the other 4907 servers in this category
- Published to the registry more recently than 93% of the other 4907 servers in this category
- Basic checks equal to or better than 100% of the other 4907 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Archprint safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.18.1) reached the registry 2 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Desktop Commander
by wonderwhy-er
MCP server for terminal commands, file operations, and process management
Runs on your computer★ 10,225MITUpdated 16 days ago
Install
Cloudflare MCP
by cloudflare
Cloudflare MCP servers
Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Archprint
Mine the architecture rules your repo already enforces, with the evidence attached.
[Try it in your browser](https://stackblitz.com/github/Tommkruix/archprint-demo), nothing to install · Quick start · Use in CI · Use with AI agents · Docs
What it does, in plain words
Every codebase has unwritten rules. "Pages never talk to the database directly." "Shared code never reaches back into the app." Nobody wrote them down, but the code follows them, until one day someone (or an AI assistant) breaks one without noticing.
Archprint reads a TypeScript project, finds the rules its code already follows, and shows you the proof for each one: how many files follow it, which files break it, and how sure it is. The rules you trust become automatic checks in the tools your team already runs, so a break is caught the next time lint runs (in your editor, a pre-commit hook or CI), not weeks later in review.
Think of it as a building inspector who surveys the house first and writes down how it was actually built, instead of handing you a rulebook from somewhere else.
- For developers and tech leads: inferred, evidence-backed lint rules for ESLint and dependency-cruiser, generated with
init, connected withwire, and removed witheject. - For reviewers:
archprint checkflags only the rule breaks a pull request introduces, inline on GitHub, never the existing backlog. - For teams using AI coding agents: Claude Code, Cursor and other agents can ask Archprint for the project's rules, with the evidence, before they write code.
- For anyone evaluating a codebase: a quick, honest picture of how a project is actually structured.
Your CLAUDE.md is guidance. Your lint rules are enforcement. Archprint closes the gap by generating the enforcement from patterns your codebase already demonstrates, so you adopt rules you can trust instead of authoring them by hand.
See it in action
The recordings below use archprint-demo, a small Next.js API whose routes reach the database only through a service layer.
1. Find the rules your code already follows. Each rule comes with its evidence.
2. See why one rule is trusted. The confidence check, step by step.
3. Turn the rules on, watch a break get caught, and remove it all again. Archprint writes its files, adds one line to your ESLint config, lint flags a route that imports the database directly, and eject restores your project exactly.
Try it yourself, nothing to install: open the demo in StackBlitz. The scan runs as soon as it opens, and the demo's README walks through enforcing a rule in ESLint, breaking it, and asking for the rules over MCP.
Use it with AI coding agents
AI coding agents can ask Archprint for a project's rules through MCP, an open standard that lets agents use outside tools. You ask in plain words; the agent calls Archprint on its own and answers with the evidence. Archprint only reports. Enforcement still runs in your linter.
Claude Code lists the rules with what is enforced and what is held for review, then adds a route and checks its own change with archprint before it reports back:
Cursor works the same way. In these recordings Cursor was set to Grok 4.7, not Claude. In the desktop app's chat, its agent called Archprint's scan tool on its own; this screenshot shows the tool result and the answer:
In the terminal (cursor-agent), it does the same: lists the rules, then adds the route and checks it with archprint_check:
Measured: the same question with and without Archprint
We asked Claude Code (Opus 5.5) "What architecture rules does this repo already follow?" on the demo app (70 files), five runs each way. Median [range]:
| Without Archprint | With Archprint | |
|---|---|---|
| Tokens read | 81k [58k to 96k] | 52k [52k to 52k] |
| Tokens written | 1.1k [1.1k to 1.4k] | 0.6k [0.6k to 0.6k] |
| Cost per question | $0.083 [$0.078 to $0.153] | $0.037 [$0.032 to $0.076] |
| Time | 17 s [15 to 19] | 10 s [9 to 31] |
| Tool calls | 5 [4 to 10] | 2 [2 to 2] |
What the answers showed:
- Both found the main rule: routes reach the database only through
lib/services/. - With Archprint, every run gave the evidence for each rule and named the one file that breaks one (
lib/db.tsreadsprocess.envoutside the config layer). No run without it noticed that. - Without Archprint, Claude also described naming conventions Archprint does not check.
Read these numbers with care: about 50k of the tokens read in both columns are Claude Code's own system prompt, and this is one small repo; larger ones are not measured yet. Method, harness and every answer.
Setup for Claude Desktop, Claude Code, Cursor and other clients is in MCP setup.
Quick start
Requires Node 20 or newer. Run these in a folder with a tsconfig.json. In a monorepo, scan and recommend also accept the root and cover every app, while init and generate work on one app at a time (for example apps/web); at a root with several apps they stop, list the apps, and ask you to rerun with one.
# 1. See the rules your code already follows, with the evidence. Changes nothing.npx archprint scan .
2. Ask why one rule is trusted (use a rule label from the scan)
npx archprint explain AP-001 .
3. Set up enforcement for the rules your code already follows cleanly,
and record what to review or adopt next in .archprint/config.json
npx archprint init .
4. Connect the generated rules to your ESLint / dependency-cruiser config (one managed line)
npx archprint wire
5. Run your linter as usual. Your code passes today; a new import that breaks a rule fails.
npx eslint .
To undo everything, exactly:
npx archprint eject
The rules you already wrote down
Your CLAUDE.md or AGENTS.md probably states rules already ("never call fetch in a component", "packages/ui must not import the app"). Agents read them as guidance. archprint gap-report checks them against the code: your agent maps each rule-like sentence to one of a few fixed templates, quoting it, and Archprint verifies the mapping and measures it. Ask your agent "Which of the rules in our CLAUDE.md does the code actually follow?", or give the CLI the mapping file your agent wrote:
{"rules": [ { "source": { "file": "CLAUDE.md", "quote": "Never call fetch directly in a component" }, "name": "no-fetch-in-components", "template": "forbid-usage", "files": ["src/components/**"], "usage": ["fetch"] } ] }
Each sentence comes back as enforce now (nothing breaks it today), enforce with a baseline (broken today, with the files and lines), already an archprint rule, check the mapping (the quote is not in the file, or the mapping matches no code), or guidance only. Archprint never calls a model: the agent only maps prose to a template, and every number in the report is computed from your code. Adopt the ones you approve with archprint generate --declare mapping.json (add --baseline for those the code breaks today): each becomes an ESLint rule whose error is your team's sentence, with its line in CLAUDE.md, and archprint check enforces it in pull requests. See the gap report for the templates.
See it catch something. After step 4, break a rule on purpose: for example, make a route file import your database client directly, then run your linter. That is the whole loop the demo walks through in the browser.
To keep it in the project instead of using npx: npm install --save-dev archprint.
More commands for a deliberate, step-by-step setup:
# Inspect the evidence behind one rulearchprint explain AP-002 apps/web
Write the auto-trusted (mechanical) rules to .archprint/, only for the linters your repo uses.
Structural-inference rules are held for review; add --include-structural to emit them too.
archprint generate apps/web
Confirm the generated rules pass on your repo before wiring (on its own, --check writes nothing)
archprint generate apps/web --check
Generate a single rule by id after reviewing it (including a SUGGEST rule)
archprint generate apps/web --rule AP-001
Adopt only the rules you choose, including reviewed layer boundaries
archprint generate apps/web --include-structural --rules AP-002,no-utils-to-app
Recommend a rule set from the evidence and the detected stack (fresh repos too)
archprint recommend apps/web
Check the rules your CLAUDE.md or AGENTS.md states against the code, from a mapping your agent wrote
archprint gap-report mapping.json .
Enforce the ones you approve (with --baseline, also those the code breaks today)
archprint generate apps/web --declare mapping.json
Upgrading from 0.5.x? Move an older archprint-rules/ setup to the .archprint layout
archprint migrate
Or build from source:
git clone https://github.com/Tommkruix/archprintcd archprint npm ci npm run build node dist/cli.js scan
How it decides what to trust
Archprint is deliberately cautious: one wrong rule hurts more than no rule. Every candidate rule passes two checks before it is turned on for you.
1. Is there enough evidence? Seeing 5 of 5 files follow a pattern is not proof; 40 of 40 is. Archprint scores each rule with a Wilson score lower bound, a standard statistical measure that combines how often the rule holds with how many files it was checked on. Each rule lands in one of three groups:
- AUTO (enforceable): the 95% lower bound on conformance is at least 90%, with at most 3 exc
Only the beginning is shown; read the rest in the repo