Skip to main content
The pre.dev MCP server gives any AI coding agent production-ready planning: full specs, architecture, and sequenced roadmaps, generated before a line of code is written.

Quick Start

1

Sign in to pre.dev

pre.dev account

Make sure you’re signed in. The MCP install will open a browser tab to ask which account (solo or enterprise organization) to authorize.
2

Install the MCP Server

Run this in your terminal:
A browser window opens — sign into pre.dev (if not already), pick which account or organization to authorize, and click Approve. Claude Code completes the handshake automatically.
For troubleshooting, see the Claude Code MCP documentation.
3

Test the Integration

Open your AI coding agent and try this command:
If successful, you’ll receive a comprehensive project specification!

Why your agent needs it

Coding agents drift on complex, multi-file projects when they plan as they go. The pre.dev MCP server front-loads the plan, so your agent builds against real architecture instead of improvising:
  • Complete system designs — database schemas, API contracts, component hierarchies
  • Sequenced roadmaps — milestones and stories your agent can execute in order
  • Technology decisions — auth, state management, and API choices made up front
  • Shared context — the same spec works across every tool that speaks MCP

Available Tools

fast_spec

Cost: ~5-10 credits (variable) | Speed: ~1 minuteQuick project specifications perfect for rapid prototyping and MVP planning.

deep_spec

Cost: ~10-50 credits (variable) | Speed: ~3-5 minutesComprehensive, detailed specifications ideal for enterprise projects and complex systems.

Advanced Features

Build on existing work by referencing previous specs or projects:
The MCP will automatically:
  • Fetch your existing context
  • Validate permissions
  • Generate new specs that build on your previous work
Automatically scrape and archive external documentation alongside spec generation.Simply reference documentation URLs in your request:
What you get:
  • Accurate Specs: AI uses the documentation to generate precise integration specifications
  • Documentation Archives: Downloadable ZIP files containing all scraped documentation
  • Organized by Platform: Each documentation source gets its own well-structured archive
  • Parallel Processing: Documentation scraping runs simultaneously with spec generation (no slowdown)
  • Graceful Fallback: Spec generation completes even if documentation scraping fails
Enterprise users can view and download documentation archives from the API Usage Logs in their dashboard.Example with multiple docs:
You’ll receive separate archives for HL7 and HIPAA documentation alongside your spec.

Cost Management

Check Your Usage: Visit pre.dev/projects/key to view remaining credits, usage history, and upgrade options.
Out of Credits?If you run out of credits, you’ll see this message:
Visit pre.dev/projects/key to upgrade your plan or purchase additional credits.

Common Use Cases

Perfect for MVPs and quick validation:

Troubleshooting

  • Re-run claude mcp add (or the Cursor one-click) to redo the browser authorization
  • Make sure you’re signed into the right pre.dev account in your browser before the consent page loads
  • If you’re an enterprise admin, pick the correct organization on the consent page — each org has its own credit pool
  • Check that your subscription is active at pre.dev/projects/key
  • Restart your editor after adding the MCP config
  • Verify the URL: https://api.pre.dev/mcp
  • Check JSON syntax in configuration