Two tools carry the idea: verify_implementation scores what was built against each outcome and constraint separately, and record_implementation_finding sends the correction back into the spec instead of leaving it in a commit message. The specs stay as markdown in your repo, so nothing here holds your requirements hostage.
An MCP server for Pathmode's intent specs. Specs live as plain markdown you own — intent.md in the repo — and the server gives an agent the structured version: objectives, outcomes, constraints, edge cases, the dependency graph between intents, and the evidence behind why each one exists.
- get_current_intent, get_intent, list_intents and search_intents — the active intent with a summary of the evidence supporting it, one by ID, all of them with status, or a keyword search across goals, objectives, outcomes and constraints
- get_intent_relations and analyze_intent_graph — what an intent depends on, enables or blocks, and an analysis of the whole graph: critical path, cycles, bottlenecks, orphans, status mismatches and stalled work
- get_agent_prompt — the full execution prompt for one intent, with its objective, outcomes, constraints, edge cases and verification steps
- get_workspace and get_constitution — the vision, non-negotiables and architecture principles, and the constitution rules every implementation must respect
- create_intent, update_intent and update_intent_status — write a new spec, change its content, or mark it shipped or verified
- verify_implementation — grade what you built against the spec, item by item across outcomes, constraints, constitution rules and edge cases, with a pass or fail and reasoning for each
- log_implementation_note and record_implementation_finding — record why you chose an approach, and correct the spec when building it proved an assumption wrong
- query_evidence, create_evidence and link_evidence — friction points, user quotes, observations, metrics and feature requests, searchable and attachable to the intents they justify
- export_context, sync_context, intent_save and intent_export — write the workspace context into CLAUDE.md or AGENTS.md idempotently, save a spec to intent.md, or export it as .cursorrules or an outcomes rubric
Nothing to sign up for. Add it to .mcp.json and the client runs npx @pathmode/mcp-server; specs live in intent.md in your repository. Set PATHMODE_API_KEY only if you want intent and evidence synced across a team.
One command — npx @pathmode/mcp-server