@happyvertical/smrt-dev-mcp
Development-time knowledge, review, architecture, introspection, and code-generation tools for AI coding agents.
What it gives you
Development-time knowledge, review, architecture, introspection, and code-generation tools for AI coding agents.
- 01Twenty-one read-only tools over a workspace, with no access to application data
- 02A declared ok, coverage, diagnostics, and data result envelope on every tool
- 03Ships as a self-contained Agent Plugin with one bundled review skill
The Development MCP server
The server reads source, manifests, and authored documentation from a workspace on disk. It never writes files, never executes generated code, and calls no model provider: review and architecture tools return deterministic findings plus a reusable prompt bundle.
smrt-dev-mcp →Runtime tools use the project's own core
The standalone installation ships static tooling and the scanner, not smrt-core, SQL drivers, AI, or filesystem providers. Code generation, knowledge and context tools, agent skills, and introspection of a built manifest work without a runtime. Source-scan enrichment and the runtime tools resolve @happyvertical/smrt-core from the selected project; install its dependencies first.
smrt-dev-mcp →Coverage instead of a silent empty answer
Package discovery reads the workspace globs and records the source of each package object. An empty result produces an error-grade diagnostic that names the checked roots and artifact paths. Thus, an unreadable project is not reported as a project without a model.
Knowledge tooling →Package UI
No UI layer to carry
This package stays focused on models, runtime behavior, or tooling. Build its interface with smrt-ui, or use a related domain package that exposes a /svelte entry point.
Intentionally headless
Package previews
No playground module yet
This package does not currently export a ./playground module. Its component names and import path remain available in the Components tab.
Intentionally not registered
Generated interface
REST
The exact route set comes from each model's @smrt({ api }) policy
and the application manifest—not from a second controller definition.
This package supports the runtime or build pipeline; it does not define a representative CRUD resource of its own.
Generated interface
MCP
AI tools are generated from the methods you explicitly include. Their inputs are validated against the same model metadata used by REST and CLI.
This package is itself infrastructure, UI, or tooling. Its capabilities are consumed by generated app MCP servers rather than exposed as a model resource.
Browser-native agent interface
WebMCP
The generated web definitions carry the same tool names, descriptions, and JSON Schema
inputs as MCP. smrt-web registers them with document.modelContext.
This package does not define a representative browser tool itself. Its models can still participate when an application exposes them through generated web collections.
Generated interface
CLI
The app CLI turns manifest resources into predictable operator commands while keeping package-specific actions close to their models.
Use this package through its documented build or runtime entry points. It does not contribute a representative generated resource command.