About Pathmode
Pathmode is an MCP server that checks which product decisions remain unresolved before a coding agent implements a request. Its deterministic preflight runs six checks without an account, API key, or model call, and can sync intent and evidence for teams.
Key features
- 01Six-check deterministic readiness assessment
- 02Zero-config use without model calls
- 03Specs stored as repository intent.md
- 04Team sync via PATHMODE_API_KEY
Use cases
- 01Find unresolved product choices before implementation
- 02Draft intent specifications from a coding request
- 03Reproduce a readiness verdict on a branch
MCP support
The MCP server gives coding agents access to Pathmode's intent preflight workflow. The repository README describes package installation and use through an MCP client.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @pathmode/mcp-serverPATHMODE_API_KEYSecretOptional: Your Pathmode API key for team features (dependency graph, workspace context). Get one from Settings > API Keys in the Pathmode app.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
22Saved tool list · updated 3w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| status | string | No | Filter by status: draft, validated, approved, shipped, verified |
| include_evidence | boolean | No | Inline the actual evidence items (truncated) this intent cites. Default false — the default response carries only a fetch-free evidenceSummary to keep casual calls cheap. |
Details
From the project README@pathmode/mcp-server
Find the product decisions a request leaves open, before your coding agent builds. A deterministic preflight: six calibrated checks, keyless, no model call.
This repository dogfoods the same workflow: read its intent.md.
This repository is the issue tracker for the package, not its source. The server is developed in Pathmode's private monorepo and published to npm from there. This repo previously held a hand-copied snapshot of the source, which drifted several versions behind the published package. It no longer carries that copy, so there is nothing here to read out of date.
To read the code, unpack the published tarball:
npm pack @pathmode/mcp-server && tar -xzf pathmode-mcp-server-*.tgz
Install
Add to .mcp.json in your project root:
{
"mcpServers": {
"pathmode": {
"command": "npx",
"args": ["@pathmode/mcp-server"]
}
}
}
No account and no API key. Specs live in intent.md in your repo, as plain markdown you own. Set
PATHMODE_API_KEY to sync intent and evidence across a team.
See it work
Given one instruction, implement FN-412, in Fieldnote
(a fictional billing app whose ticket asks for a Cancel plan button), an agent with this server
wrote no product code. It found that the only cancel code in the repository was written for
refunds and would take paid days away from every customer who cancels, drafted an intent.md with
four open product choices, and stopped: preflight passed 6/6, still blocked by those choices.
The recorded run
lists every tool call, and npx -y @pathmode/cli preflight on that branch reproduces the verdict.
Links
- npm package: the published server, always current
- IntentSpec: the open specification for the
intent.mdfiles this server writes - The intent.md profile: the six checks
check_intent_readinessscores against - Pathmode: the platform for teams
- Listed in the MCP registry
Issues
Bug reports and feature requests belong in Issues.
Include the output of npx @pathmode/mcp-server --version and the client you are running.
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.