@rqml/mcp
v0.6.1
Published
Model Context Protocol server exposing the RQML engine (@rqml/core) as agent tools: validate, status, check, trace, show, impact, link, and skeleton.
Downloads
1,041
Maintainers
Readme
@rqml/mcp
A Model Context Protocol server that exposes
the RQML engine (@rqml/core) to coding agents as tools over stdio.
Tools
| Tool | Purpose |
|------|---------|
| rqml_validate | XSD + referential-integrity validation of a document |
| rqml_status | Requirement count, trace coverage, dangling references |
| rqml_check | The deterministic gate: validation + coverage + drift → pass/fail |
| rqml_trace | Resolve the trace graph and report dangling local references |
| rqml_discover | Enumerate the governing specs in a repository, and resolve the spec governing a file — for monorepos |
| rqml_show | One artifact: statement, acceptance criteria, trace neighborhood — data + markdown |
| rqml_impact | What is affected, transitively, if an artifact changes |
| rqml_matrix | Traceability matrix: per-requirement status, goals, code, tests, coverage warnings — data + markdown |
| rqml_overview | Readable spec projection: whole document or scoped by section/id — outline + markdown |
| rqml_approve | Transition a requirement's lifecycle status (writes on explicit intent) |
| rqml_gate | Approval-before-implementation verdict (optionally scoped to changed paths) |
| rqml_skeleton | Generate a schema-valid RQML snippet (req / edge / testCase / stateMachine) |
| rqml_link | Record/maintain an implements/verifiedBy edge and its drift baseline (writes on explicit intent) |
Each document-reading tool accepts the document inline as xml, as a filesystem
path (read without modification — REQ-MCP-PATH-INPUT), or as a file whose
governing spec is resolved by nearest-wins discovery (handy in monorepos);
rqml_check and rqml_matrix take additional options. Every tool is backed by @rqml/core, so results are
equivalent to the corresponding rqml CLI command (REQ-MCP-PARITY); responses
are text/JSON only (the server depends on no optional MCP client features such as
resources or elicitation), and it performs no irreversible filesystem actions
without explicit caller intent (REQ-MCP-READONLY).
Run
npx @rqml/mcp # speaks MCP over stdio