Performs deterministic intent preflight checks to identify product decision gaps before a coding agent begins implementation.
Also known as pathmodeio/mcp-server, @pathmode/mcp-server
- Stars
- 3
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.44.0
- Last commit
- Oct 20, 2026
- License
- —
What is Pathmode MCP?
Pathmode performs deterministic intent preflight checks to identify product decision gaps before a coding agent begins implementation.
Summary generated from the project's README
About Pathmode MCP server
Identifying product decision gaps before a coding agent starts writing code is the primary function of this server. It performs six calibrated, deterministic checks to evaluate if a request is ready for implementation. By using the check_intent_readiness tool, the server analyzes instructions against an intent.md file to find missing product choices that could lead to incorrect code.
Developers set this up locally by adding the npx command to their mcp.json configuration. It operates without requiring an account or an API key for basic use, though setting a PATHMODE_API_KEY allows teams to sync intent and evidence. The system relies on plain markdown files that you own, ensuring that the preflight process is based on your specific project specifications rather than external model calls.
What you can do with it
- 1Preventing incorrect implementation logicAsk the agent to analyze a feature request to see if existing code patterns might conflict with the new requirement.
- 2Automating product readiness assessmentsUse the server to score whether a task has enough information to proceed without further human input.
- 3Drafting missing requirement documentationHave the agent generate a list of open product choices when it encounters an ambiguous instruction.
Written from the project's README. Every use case is checked against a quote from it.
How to install Pathmode MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Pathmode MCP in Claude Code
$ claude mcp add --env 'PATHMODE_API_KEY=<YOUR_PATHMODE_API_KEY>' mcp-server -- npx -y @pathmode/mcp-serverInstall Pathmode MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@pathmode/mcp-server"
],
"env": {
"PATHMODE_API_KEY": "<YOUR_PATHMODE_API_KEY>"
}
}
}
}Install Pathmode MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pathmode/mcp-server"
],
"env": {
"PATHMODE_API_KEY": "<YOUR_PATHMODE_API_KEY>"
}
}
}
}Install Pathmode MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp-server","type":"stdio","command":"npx","args":["-y","@pathmode/mcp-server"],"env":{"PATHMODE_API_KEY":"<YOUR_PATHMODE_API_KEY>"}}'Install Pathmode MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@pathmode/mcp-server"
],
"env": {
"PATHMODE_API_KEY": "<YOUR_PATHMODE_API_KEY>"
}
}
}
}Install Pathmode MCP in Codex
$ codex mcp add mcp-server --env 'PATHMODE_API_KEY=<YOUR_PATHMODE_API_KEY>' -- npx -y @pathmode/mcp-serverInstall Pathmode MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-server] command = "npx" args = ["-y", "@pathmode/mcp-server"] [mcp_servers.mcp-server.env] PATHMODE_API_KEY = "<YOUR_PATHMODE_API_KEY>"
Install Pathmode MCP in Gemini CLI
$ gemini mcp add -s user -e 'PATHMODE_API_KEY=<YOUR_PATHMODE_API_KEY>' mcp-server npx -- -y @pathmode/mcp-serverInstall Pathmode MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server": {
"command": "npx",
"args": [
"-y",
"@pathmode/mcp-server"
],
"env": {
"PATHMODE_API_KEY": "<YOUR_PATHMODE_API_KEY>"
}
}
}
}Configuration
PATHMODE_API_KEYSecretOptional: Your Pathmode API key for team features (dependency graph, workspace context). Get one from Settings > API Keys in the Pathmode app.
| Name | Description | |
|---|---|---|
| PATHMODE_API_KEY | Optional: Your Pathmode API key for team features (dependency graph, workspace context). Get one from Settings > API Keys in the Pathmode app. | Secret |
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachablepathmodeio/mcp-server is public and reachablegithub.com/pathmodeio/mcp-server ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-11-13github.com/pathmodeio/mcp-server ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from @pathmode/mcp-serverPass
- No critical advisory in the package or its dependenciesthe package checked; no critical advisoryosv.dev ↗Pass
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeNot checked
README
View on GitHub@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
Pathmode MCP questions
How do I add Pathmode MCP to Claude Code?
Run claude mcp add --env 'PATHMODE_API_KEY=<YOUR_PATHMODE_API_KEY>' mcp-server -- npx -y @pathmode/mcp-server in your terminal. Add --scope user to make it available in every project.
How do I add Pathmode MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Where can I find the source code?
The source code is developed in a private monorepo and published to npm; you can view it by unpacking the published tarball.