Architecture Check MCP
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
Architecture Check MCP
English · Русский
A local stdio MCP server that runs the architecture rules defined by your project. It works with MCP clients such as Codex and Claude and requires Node.js 22 or newer. Each project owns its rules and can use its preferred analysis libraries or build tools.
Quick start
git clone https://github.com/hram/architecture-check-mcp.git
cd architecture-check-mcp
npm ci
npm testConfigure your MCP client to launch the server. Use an absolute path to the entry point:
[mcp_servers.architecture-check]
command = "node"
args = ["/path/to/architecture-check-mcp/src/mcp-server.js"]For clients that accept an mcpServers JSON object:
{
"mcpServers": {
"architecture-check": {
"command": "node",
"args": [
"/path/to/architecture-check-mcp/src/mcp-server.js"
]
}
}
}Restart the MCP client and call architecture_check:
{"project_path":"/path/to/architecture-check-mcp/examples/layered-project"}The same server can check another project on the next call. The example
should return pass. To see a finding, add
"dependencies": { "@example/infrastructure": "*" } to
examples/layered-project/packages/domain/package.json and call the tool again.
Related MCP server: ml-skills-mcp
Use it with your project
Copy the example .architecture directory
into your project, adapt its manifest and rules, and pass your checkout as
project_path. Or implement the same JSON protocol with your own
checker. Only run the server against projects whose checker code you trust: it
executes .architecture/cli.cjs with your local permissions.
The checker runs against the working tree, including uncommitted files. Each rule reports what it covered. The example checks the domain package's declared dependencies; it does not inspect JavaScript imports or transitive dependencies.
You can optionally narrow the returned findings to selected files or lines. This leaves the overall status and check statuses unchanged:
{
"project_path": "/absolute/path/to/project",
"report_filter": [
{ "path": "packages/domain/package.json", "lines": [[1, 10]] }
]
}Optional access scope
--allow-root /absolute/pathrestricts checks to that directory and its descendants. Repeat it for several directories.--project-manifest /path/to/projects.jsonrestricts checks to the exact directories in{"projects":[{"path":"/absolute/path/to/project"}]}.--project-path-env VARIABLErestricts checks to the exact directory in that variable when it is set. All configured restrictions apply together.
For meta-agent, add one custom stdio entry per space and pass --project-manifest with that space's space.json path and --project-path-env PROJECT_PATH. The same project_path tool argument applies to every client.
Direct invocation
The project checker itself can also run directly. From the example project root:
printf '%s\n' '{"protocol_version":1,"request_id":"manual-1","scope":"project"}' |
node .architecture/cli.cjsIt prints one JSON report. Exit codes are 0 for pass, 1 for violations,
and 2 for an incomplete check.
License
ISC.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Automated architecture sanity check: 19 rule-cited checks, verdict report. Paid runs US$99.
Statically audits MCP tool surfaces for token cost, schema quality, and design issues.
Scan iOS and Android project files for common App Store and Play review issues over MCP.
Check AI work against requirements and return structured verdicts, findings, and repair steps.
Related MCP Servers
- FlicenseAqualityBmaintenanceEnables local auditing of trading strategies through MCP checkers for point-in-time data provenance, pre-trade order validation, and regime-fragility testing, while deferring promotion verdicts to a hosted service.1465 PyPI-
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to enforce architecture standards by checking repositories against overridable rules and adapter results over MCP.14 npmMIT
- AlicenseAqualityBmaintenanceEnables agents and CI pipelines to audit MCP servers and agent tool-chains by statically scanning repositories, local checkouts, tools/list exports, or live endpoints for risks such as destructive actions without confirmation, mismatched safety annotations, injection surfaces, credential or PII exposure, and unguarded command, path, or URL sinks. All checks are read-only and never execute the scanned code or call tools/call.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to run deterministic, read-only local repository audits for risky GitHub workflows, undocumented environment variables, possible credentials, and conflicting dependency configuration, returning structured findings without sending source code to a service.58 npmMIT