MCPMIT · agent-agnostic
MCP
MCP integration
Optional stdio bridge for MCP-capable agents. The file-based CLI workflow remains the default for teams and CI.
When to use MCP
Default: CLI + committed files. Best for teams, CI, and reproducible handoffs.
MCP: when your agent host supports tool servers and you want route listing or compile hints during a live session — without leaving the editor.
Start server
Stdio MCP server
npx dzine-skill mcpTools
| Tool | Behavior |
|---|---|
| dzine_list_routes | Lists canonical style routes from corpus validator |
| dzine_compile_contract | Compiles brief → DesignContract JSON |
| dzine_validate_contract | Runs dzine_contract.py validate |
| dzine_render_pack_hint | Returns CLI render command |
| dzine_score_url_hint | Returns CLI score command |
| dzine_repair_prompt_hint | Returns CLI repair command |
| dzine_install_hint | Init and setup guidance |
Cursor setup
- Run
npx dzine-skill init --target cursor - Add MCP server config pointing at
npx dzine-skill mcp(from your repo clone) - Prefer generating
./build-pack/via CLI for commits and CI
Start with Agent handoff if you are new to DZINE.