Solarch Tools
- 1 repo stars
- Updated June 23, 2026
- solarch-dev/solarch-tools
solarch-tools is a Claude Code marketplace distributing SOLARCH 2.0 packages that scan NestJS codebases, detect architecture drift against cloud diagrams, and expose rule-checked MCP mutations for developers using Solarc
About
solarch-tools is a Claude Code marketplace for Solarch developer tooling across four packages: @solarch/ast-core ts-morph NestJS AST engine, @solarch/cli solarch binary, @solarch/mcp solarch-mcp server, and solarch-vscode extension. solarch connect links a NestJS repo to Solarch cloud; solarch scan and solarch diff compare As-Is code against To-Be diagrams with 21 node kinds and 16 edge kinds matching solarch-backend schemas. solarch diff --ci exits 1 on rule violations to block merges. solarch pull and solarch push synchronize .solarch/to-be.json with revision-aware 409 conflict handling. solarch bind and solarch watch propagate entity field changes into DTOs with @solarch:bound markers. The MCP server exposes six tools sharing CLI engines so agent and CI drift never diverge. Phases 1–3.7 are marked DONE including VS Code revision timeline and surgical status reporting. Use solarch-tools when Claude agents need real architecture context and safe NestJS mutations over MCP.
- Monorepo ships 4 packages: ast-core, cli, mcp, and vscode extension
- Matches 21 node kinds and 16 edge kinds to solarch-backend schemas
- solarch diff --ci blocks merges on architecture rule violations
- MCP server exposes 6 tools sharing @solarch/cli engines with CI
- solarch bind/watch auto-updates DTO fields from Entity changes
Solarch Tools by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add solarch-dev/solarch-toolsAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| repo stars | ★ 1 |
|---|---|
| Last updated | June 23, 2026 |
| Repository | solarch-dev/solarch-tools ↗ |
How do you enforce NestJS architecture drift in CI?
Wire solarch-mcp into mcp.json and run solarch diff --ci on NestJS repos to block merges when code drifts from Solarch architecture diagrams.
Who is it for?
NestJS teams using Solarch cloud diagrams who want AST-level scan/diff, pull/push sync, and MCP-safe mutations inside Claude Code agents.
Skip if: Non-NestJS frameworks, repos without Solarch API keys, or teams that only need informal architecture sketches without CI drift gates.
What you get
.solarch/to-be.json graph, drift diff reports, CI exit codes, bound DTO updates, and MCP architecture context for agents.
- Architecture drift report
- .solarch/to-be.json graph
- CI-blocking diff annotations
By the numbers
- Monorepo contains 4 packages: ast-core, cli, mcp, and vscode
- Taxonomy defines 21 node kinds and 16 edge kinds
- MCP server exposes 6 architecture context and mutation tools
Plugins in this marketplace
1 plugin - install individually after you add the marketplace.
Recommended Marketplaces
How it compares
Pick solarch-tools over generic NestJS linters when architecture must stay synchronized with Solarch cloud diagrams via AST scan, bidirectional push/pull, and MCP-safe mutations.
FAQ
How many MCP tools does solarch-mcp provide?
solarch-mcp exposes six tools for architecture context, drift detection, an unimplemented queue, and safe mutations. Tools reuse @solarch/cli engines so agent-reported drift matches solarch diff --ci output.
What taxonomy does Solarch Tools use for nodes and edges?
Solarch Tools mirrors Solarch cloud exactly with 21 node kinds and 16 edge kinds defined in packages/ast-core/src/types.ts, detecting roles from NestJS decorators like @Controller, @Injectable, and @Entity rather than filenames.
How does solarch diff behave in CI?
solarch diff --ci emits GitHub annotations and exits with code 1 when code contains unapproved expansions, missing diagram commitments, or live Rules Matrix violations such as a Controller calling a Repository directly.