MCP Server

What pathmodeio/mcp-server MCP server does

pathmodeio/mcp-server MCP server helps coding agents determine whether a request is ready for implementation. It focuses on product decisions that the request leaves unspecified, rather than generating code or using a model to judge readiness. The server works with an intent.md file in the project repository, where the specification remains plain Markdown owned by the team.

Its readiness result is based on six calibrated checks. A request can therefore be technically understandable yet still fail preflight because important product choices remain open. The documented example uses a cancellation feature: the agent inspected existing code, identified a potentially harmful reuse of refund logic, recorded four unresolved choices in intent.md, and did not write product code.

How it works

The package is launched as an MCP process through npx. An MCP-compatible coding client can then use the server during task planning. The workflow is deterministic, keyless, and does not make a model call for the preflight itself.

The repository contains an issue tracker rather than the package source. The published npm package is the current distribution, while the repository documents the workflow and links to related specifications. The six checks used by check_intent_readiness are described by the IntentSpec intent.md profile.

pathmodeio/mcp-server MCP server is suited to teams that want a repeatable gate before implementation. It is less suitable if the goal is direct code generation, an API-backed planning service, or an autonomous implementation tool.

Setup and configuration

Add the server to .mcp.json in the project root:

{
  "mcpServers": {
    "pathmode": {
      "command": "npx",
      "args": ["@pathmode/mcp-server"]
    }
  }
}

No account or API key is needed for the basic setup. Intent specifications are stored in the repository as intent.md.

For version or issue investigation, the project asks maintainers to include the output of npx @pathmode/mcp-server --version and the client being used. The npm package is the authoritative published artifact; the GitHub repository may not contain the current source snapshot.

Tools and capabilities

• Runs six deterministic readiness checks before implementation.
• Uses the repository's intent.md as the input specification.
• Supports an intent-readiness check named check_intent_readiness.
• Helps an agent record unresolved product choices instead of proceeding directly to code.
• Works without a model call or API key in the keyless workflow.
• Can sync intent and evidence across a team when PATHMODE_API_KEY is set.

Limitations and notes

pathmodeio/mcp-server MCP server does not replace product decisions. A passing six-check preflight does not mean every implementation detail is complete; the documented example passed all six checks while remaining blocked by unresolved choices. The server also does not claim to implement the requested feature.

The source is maintained in a private monorepo and published to npm, so the GitHub repository is primarily for issues and project documentation. Review intent.md, the IntentSpec profile, and the published package when exact behavior or version details matter.