Claude Code MCP Server

Intent Compiler

Build structured intent specs through Socratic conversation in your terminal. Zero config. No signup. Just add the MCP server and start talking.

Get Started Try in Browser

Works with Claude Code today. Cursor and Windsurf support coming soon.

claude — intent-compiler

> Help me write an intent spec for our checkout flow

What's broken about it? When you say "checkout flow" — is the whole thing failing, or is there one specific moment where users bail?

> Payment step times out and users get confused

When you say "times out" — is that 5 seconds or 30? And what does the user actually see? A spinner? A blank screen? An error they can't act on?

> About 8 seconds, they see a spinner with no feedback

Proposed Objective: "Reduce cart abandonment caused by payment step timeouts exceeding 3 seconds, where users see a spinner with no status feedback or recovery path." Does that capture it, or is there more to the pain?

How it works

Claude becomes your product thinking partner. It challenges vague ideas until the spec is clear enough to build.

1. Describe the problem

Paste a support ticket, describe a user complaint, or just say what's broken. Claude starts by challenging your framing.

2. Socratic conversation

Claude pushes back on vague language, asks one pointed question at a time, and proposes precise spec fields as clarity emerges.

3. Save & export

When the spec is ready, Claude writes intent.md to your project and optionally exports as .cursorrules or CLAUDE.md.

What you get

A structured spec that AI coding agents can actually execute. Not a vague description — a precise contract with objectives, testable outcomes, and edge cases.

intent.md
The structured spec file. YAML frontmatter + markdown sections. Readable by humans, parseable by tools.
.cursorrules
Agent-directive format. Cursor reads this automatically and sees the intent as its implementation context.
CLAUDE.md
Appends a Pathmode section to your project's CLAUDE.md. Every Claude Code conversation sees the intent.

---
id: "intent_17291..."
version: 1
status: "draft"
---

# Fix Checkout Payment Timeout

## Objective
Reduce cart abandonment caused by payment step
timeouts exceeding 3 seconds, where users see
a spinner with no status feedback or recovery path.

## Outcomes
- [ ] Payment completes in under 3 seconds for
      95th percentile of transactions
- [ ] Users see real-time status during processing
- [ ] Failed payments show actionable error with
      retry button

## Edge Cases
- **Network timeout during payment**: Show retry
  button, do not double-charge
- **Payment provider returns unknown status**:
  Hold order, notify user within 30 seconds

Get started in 30 seconds

Add the Pathmode MCP server to your Claude Code settings. No API key needed.

Add to your Claude Code settings

.claude/settings.json

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

Start a conversation

> Help me write an intent spec for improving our search results

Claude picks up the compile-intent prompt and becomes your Socratic product thinking partner.

Save and export

When the spec is ready, Claude automatically calls intent_save to write intent.md to your project root. Want agent-ready output? Ask for .cursorrules or CLAUDE.md export too.

From REPL to Runtime

The Intent Compiler gives you structured specs in your terminal. When you need dependency tracking, team collaboration, and governance — connect to the full platform.

Intent Compiler

Free, zero-config

Socratic spec building in terminal
Export to intent.md / .cursorrules / CLAUDE.md
Works offline, no account needed
Single-intent, single-developer

Pathmode Platform

For teams shipping with AI

Everything in Compiler, plus:
Intent dependency graphs & critical path
Evidence board — link specs to user feedback
Team collaboration & governance
Auto-sync to Linear and Jira

What you get

A structured spec that AI coding agents can actually execute. Not a vague description — a precise contract with objectives, testable outcomes, and edge cases.

intent.md

The structured spec file. YAML frontmatter + markdown sections. Readable by humans, parseable by tools.

.cursorrules

Agent-directive format. Cursor reads this automatically and sees the intent as its implementation context.

CLAUDE.md

Appends a Pathmode section to your project's CLAUDE.md. Every Claude Code conversation sees the intent.

--- id: "intent_17291..." version: 1 status: "draft" --- # Fix Checkout Payment Timeout ## Objective Reduce cart abandonment caused by payment step timeouts exceeding 3 seconds, where users see a spinner with no status feedback or recovery path. ## Outcomes - [ ] Payment completes in under 3 seconds for 95th percentile of transactions - [ ] Users see real-time status during processing - [ ] Failed payments show actionable error with retry button ## Edge Cases - **Network timeout during payment**: Show retry button, do not double-charge - **Payment provider returns unknown status**: Hold order, notify user within 30 seconds