Skip to main content
The pre.dev platform’s core spec generation engine is also available as a standalone API and MCP (Model Context Protocol) server. These are extension points for developers who want to integrate pre.dev’s architecture capabilities into their own workflows.

​
When to Use the API vs. the Platform

Use CaseRecommended
Build a full app from scratchPlatform (pre.dev web app)
Generate specs inside Cursor/Claude CodeMCP Server
Integrate spec generation into CI/CDAPI
Build custom tooling on top of pre.devAPI + SDKs
One-off spec for a feature you’ll build manuallyMCP Server

​
The Architect API

The API gives you programmatic access to pre.dev’s spec generation:
  • POST /fast-spec — Quick specs in ~30-60 seconds (~3-8 credits)
  • POST /deep-spec — Comprehensive specs in ~2-5 minutes (~15-40 credits)
  • GET /spec-status/:id — Check async generation progress
  • GET /list-specs — List your generated specs
  • GET /find-specs — Search specs by content
  • GET /credits-balance — Check remaining credits
Authentication: Bearer token via Authorization header. 
curl -X POST https://api.pre.dev/fast-spec \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{"input": "Build a task management app with team collaboration"}'
See the full API Reference for details.

​
The MCP Server

The MCP server lets AI coding agents (Cursor, Claude Code, VS Code Copilot, Windsurf) generate pre.dev specs conversationally. Instead of switching to the web app, you can generate architecture specs directly in your IDE. Supported tools:
  • Cursor (one-click install)
  • Claude Code
  • VS Code
  • Windsurf
  • Any MCP-compatible client
Setup: 
{
  "mcpServers": {
    "predev": {
      "url": "https://api.pre.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
See the full MCP Server setup guide for per-tool instructions.

​
SDKs

For deeper integration, use the official SDKs:

Node.js / TypeScript

npm install predev-api

Python

pip install predev-api

​
API vs. Platform: What’s Different?

The API provides spec generation only — it produces the structured specification (milestones, stories, subtasks) as markdown. It does not include:
  • Autonomous build agents
  • Acceptance verification
  • PR creation
  • Progress tracking
  • Knowledge Base integration
These are platform-only features. The API is for developers who want the spec and will handle building themselves (or feed the spec into their own agent pipeline).

​
Common API/MCP Patterns

​
Generate spec → Feed to your own agent

Use the API to generate a comprehensive spec, then feed it as context to your own coding agent (Cursor, Claude Code, Aider, etc.).

​
Pre-planning in CI

Automatically generate a spec for every feature branch to validate scope before development begins.

​
Custom dashboards

Use the API to generate and track specs as part of your team’s internal tooling.

​
Getting Your API Key

Get API Key

Visit the playground to generate your API key.