Pathmode

@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.md files this server writes
• The intent.md profile: the six checks check_intent_readiness scores against
• Pathmode: the platform for teams
• Listed in the MCP registry and on Smithery, which carries the same server as a local bundle that runs the build it ships instead of fetching from npm at launch

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