io.github.pathmodeio/mcp-server

Record a person's answer to one open product choice in the local intent.md, or take an answer back. Local mode only. Call it once per choice the person has explicitly answered, with their own words for THAT choice in answer, parents before the choices that depend on them. One message may answer several choices; each still gets its own call and its own quoted words. A blanket "go with the recommendations" is not an answer to any choice: ask about each one, recommendation first, and never offer to accept them all at once. Set humanApproved only after the person has answered the choice you are recording. The answer is written the way a workspace review writes one (the accepted claims enter the spec, a decision is logged), marked answered locally (unverified), and bound to the choice text: editing the choice afterwards reopens it. It is the local record of a conversation, not verified approval, and it does not authorize anything for a team. A choice whose kind is question has no recommendation: ask it as written, then use change with the person’s answer and the claims it adds. Do not invent explanation fields. Actions: use (accept the recommendation), change (a different answer: pass alternative), exclude (leave the behavior out, with a reason), defer (leave it open), reopen (take a recorded answer back, removing what it added). change is also how a flagged outcome claim is corrected, since a saved choice cannot be edited: keep the person's answer as alternative.answer and give the measurable outcome in alternative.claims. You translate the answer into an observable claim without changing its meaning or inventing thresholds; never ask the person to supply measurable wording. If behavior is still missing, ask a concrete product question. After recording, rerun check_intent_readiness.

Run the deterministic preflight on an intent spec before handing it to an implementation agent. Six calibrated checks — title, objective, outcomes, constraints, edge cases, verification — computed by pure functions: no model call, no network, the same spec always gets the same verdict. Pass a spec inline to check before saving, pass intentId to check a specific saved intent, pass repoRoot to check the intent.md of the repository you are working in, or pass nothing to resolve the repo-bound intent.md from MCP workspace roots or the launch directory. The repo-bound intent.md is the one at the repository root or, when there is none, the single intent.md in an intent/ folder (intent/intent.md or intent/<feature>/intent.md), where Anthropic's AI-native SDLC playbook keeps it. Pass path to choose among several, or to check a file with another name. When the repository has no intent.md, or cannot be identified, it refuses rather than grading an unrelated intent; pass repoRoot to name the repository, or intentId to check a specific saved intent. A failing verdict names the exact blockers; repair the fields and re-run. This is the gate that runs at preflight.pathmode.io.

Resolve an "unconfirmed" readiness dimension, in a local intent.md or in a connected workspace. Use this when check_intent_readiness reports that it READ your objective or outcomes but could not confirm them: the gate matches a fixed English and Finnish vocabulary and misses valid phrasing, including other languages. confirm: state who is affected and what goes wrong for them, in your own words, and the dimension passes. waive: mark the dimension as not applicable to this change (a pure refactor has no product outcome). A waiver is a HUMAN decision, so set humanApproved only after the user has explicitly agreed. Waivers are local-mode only: a workspace will not accept one over an API key, which authenticates as a machine. The confirmation is bound to the exact text it was made against and dies automatically if that text is edited. You cannot confirm a dimension the gate read nothing for; write the field first, save, then confirm.

Get the currently active intent, preferring approved intents with real objective/outcome content over empty stubs. With a workspace connected it chooses across the whole workspace, not by repository, so do not use it to find the intent for the repository you are working in: read intent.md or call check_intent_readiness with no arguments, and when the repository has none, ask which intent the user means. Returns the full IntentSpec plus an evidenceSummary (how many evidence items it cites by ID, across all trust tiers; tier counts come with include_evidence=true). Evidence is referenced by ID; pass include_evidence=true to inline the evidence content grouped by trust tier (backing, unreviewed, assumption) with per-tier counts, or call get_agent_prompt for the full evidence-backed execution prompt.

Get a single intent by ID with full details including objective, outcomes, constraints, edge cases, and relations. Evidence is referenced by ID; call get_agent_prompt for the full evidence-backed execution prompt.

Export an intent spec as .cursorrules, a CLAUDE.md or AGENTS.md section, a Claude Managed Agents Outcomes rubric, or an OpenSpec change folder. Use agents-md for Codex, Cursor, and other AGENTS.md-aware agents. Use openspec to hand the intent to an OpenSpec workflow: it writes proposal.md, a spec delta, and the verification contract in tasks.md, placed where the preflight reader finds them, and never writes into an existing change.

Adopt an existing OpenSpec change as the Pathmode intent record. Reads the change folder exactly as the preflight does (proposal.md, spec deltas, design non-goals, verification in tasks.md) and saves it as intent.md — with a workspace key, also as a workspace intent. The change folder is NEVER modified, and field text travels verbatim, so never retype fields from the change yourself. After importing, resolve any unconfirmed dimensions with confirm_intent_dimension.

Save an intent spec to the repository intent.md — the default choice when you are working inside a repository. With no path it writes the file check_intent_readiness reads: intent.md at the project root, or the single intent.md in an intent/ folder when the root has none. With a Pathmode API key set it ALSO creates or updates the intent in the workspace and records the sync in the file, so the file is the projection of the record rather than a second copy of it. Re-saving the same intent bumps its version and preserves its status; it never silently replaces a different intent. Never block saving a failing spec: it saves, and the reply names its blockers; do not start implementation from it. Use create_intent instead when there is no repository to write into.

List all intents in the workspace. Returns an array of IntentSpecs with their status, objectives, and metadata.

Search intents by keyword. Searches across user goals, objectives, outcomes, and constraints.