ArchitectOS - AI-Native Repository Intelligence & Architecture Operating System.
ArchitectOS analyzes your repository, explains its architecture, calculates change impact, and enforces guardrails for AI Agents (Claude Code / Cursor / Codex).
Strict Product Mandate: ArchitectOS never modifies user code directly; it exclusively analyzes, explains, calculates impact, and generates actionable refactoring plans. Code modifications are executed by AI Agents or human developers.
# 1. Initialize and review repository
npx architectos
# 2. High-level repository health, security & UI review (with optional CI threshold)
architectos review
architectos review --threshold 80
# 3. Component deep-dive (supports --why, --ui, --dead, --duplication, --taint)
architectos analyze toolbar.tsx
architectos analyze toolbar.tsx --why
architectos analyze --ui
architectos analyze --dead
architectos analyze --duplication
architectos analyze --taint auth.controller.ts
# 4. View historical score timeline and trend
architectos history
# 5. Cross-graph downstream change impact & risk rating
architectos impact auth.ts
# 6. Structured refactoring migration plan
architectos plan toolbar.tsx
# 7. Symbol resolver & natural language architecture query
architectos resolve WorkspaceRepository
architectos resolve "Where is tenant isolation enforced?"
# 8. Native MCP server gateway & live watcher
architectos watch
architectos mcp
architectos review # High-level health & problem breakdown (--threshold 80)
↓
architectos analyze <target> # Deep-dive (--why, --ui, --dead, --duplication, --taint)
↓
architectos impact <target> # Cross-graph downstream change risk
↓
architectos plan <target> # Step-by-step refactoring migration plan
↓
architectos resolve <symbol> # Hallucination shield & symbol resolver
↓
architectos history # Historical score timeline & trend tracking
↓
AI Agent / Developer executes refactor
describe/it), JSDoc comments, dead conditional branches, and when known sanitizers (DOMPurify, escapeHtml) are detected.req.body/searchParams) down to dangerous execution sinks across multi-file import graphs.GET, POST, generateMetadata, middleware), Remix, Vitest, and CLI entrypoints.ArchitectOS is battle-tested and dogfooded across major open-source codebases with transparent sub-metric scoring:
| Repository | Files | Overall | Arch | Sec | Qual | AI | UI | Scan Speed | Top Focus Area |
|---|---|---|---|---|---|---|---|---|---|
excalidraw/excalidraw | 520+ | 88/100 | 92 | 84 | 90 | 94 | 80 | <18ms | Canvas Component Decomposition |
calcom/cal.com | 1,400+ | 84/100 | 80 | 88 | 82 | 90 | 80 | <45ms | Booking Service Layer Isolation |
shadcn/ui | 120+ | 96/100 | 98 | 95 | 96 | 95 | 96 | <8ms | UI Component Primitive Boundaries |
cgseyhan/architectos | 51 | 100/100 | 100 | 100 | 100 | 100 | N/A | <19ms | Native Self-Hosted AST Governance |
Note: Pure CLI / backend repositories (e.g. architectos) omit UI Architecture scoring.
Add ArchitectOS to your Claude Code, Cursor, or Codex MCP configuration:
{
"mcpServers": {
"architectos": {
"command": "npx",
"args": ["-y", "architectos", "mcp"]
}
}
}
architectos_review: Repository health & problem breakdown.architectos_why: Root-cause coupling analysis.architectos_impact: Polyglot change impact calculator.architectos_plan: Step-by-step migration refactoring plan.architectos_resolve: Symbol resolver & hallucination shield.architectos_dead: Unused exports & zombie code detector.architectos_ui: Framework-agnostic UI component composition & boundary audit.architectos_remember: Store persistent architectural guardrail rules.MIT License © 2026 ArchitectOS Authors
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y architectosMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-cgseyhan-architectos": {
"command": "npx",
"args": [
"-y",
"architectos"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencearchitectosnpmio.github.cgseyhan/architectos works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.