Connect the MCP server

The pre.dev product MCP server is https://api.pre.dev/mcp. One connection exposes seven primary tools for specifications and browser automation.

Connect your client

Claude Code
Cursor
Other clients

claude mcp add --transport http predev https://api.pre.dev/mcp

In Claude Code, run /mcp, select predev, and follow the browser authentication flow. Sign in to pre.dev and select the account or organization to connect. See the Claude Code MCP documentation for client-specific settings.

Add this to your Cursor MCP configuration, then use the server’s authentication control:

{
  "mcpServers": {
    "predev": {
      "url": "https://api.pre.dev/mcp"
    }
  }
}

You can also add pre.dev to Cursor. The client opens a browser when authentication is needed.

Add a remote server with Streamable HTTP transport and URL https://api.pre.dev/mcp. Use browser OAuth if your client supports it.For a programmatic client, send one of the supported authentication headers, for example Authorization: Bearer <key>. Obtain the key at pre.dev/projects/key. No pre.dev npm MCP server package is required.

Try a tool

Ask your assistant:

Use pre.dev fast_spec to plan a team task manager with projects,
assignees, due dates, and organization-scoped access. Retrieve the
completed specification and show me its milestones.

Or try browser automation:

Use pre.dev browser_agent to read https://example.com and extract
its main heading. Fetch the complete structured result afterward.

Tool execution uses your account’s credits and access. Connecting a server does not change your plan. See authentication eligibility if a free account can use browser REST but cannot authenticate to MCP.

Connection lifecycle

The client authenticates, initializes the connection, discovers tools, and calls one. Progress notifications can arrive before the tool result. Use a standard MCP client library to handle JSON-RPC initialization and response streams. For Streamable HTTP, requests should accept both application/json and text/event-stream.

Transport details

Endpoint	Purpose
`POST /mcp`	Current Streamable HTTP transport; stateless requests
`GET /mcp/info`	Public metadata and tool inventory
`GET /mcp`	Returns `405 Method Not Allowed`; this is expected
`GET /mcp/sse`	Deprecated legacy SSE connection
`POST /mcp/messages?sessionId=…`	Message endpoint for a legacy SSE session

The server advertises protocol versions 2024-11-05, 2025-03-26, 2025-06-18, and 2025-11-25. Let the client negotiate a supported version. An unsupported MCP-Protocol-Version header returns 400. The current transport does not create a persistent MCP session ID or provide a server-initiated GET stream. Notifications arrive on the active POST response. Legacy clients must use the separate /mcp/sse endpoint.

Troubleshooting

Symptom	What to check
Opening `/mcp` in a browser returns `405`	Open service metadata; configure the MCP client to POST
Authentication fails	Reauthenticate in the client; check the selected account, key, and plan
Tools are missing	Restart or refresh the client, then rediscover `tools/list`
A spec tool returns before the spec is ready	Save its ID and poll `get_spec`
A browser result contains only a summary	Call `browser_agent_get` for full data
Progress is missing	Logging support varies by client; progress notifications require a `progressToken`

For exact arguments and return formats, use the MCP tool reference. To attach a third-party server to the pre.dev Coding Agent, use external MCP servers.

​Connect your client

​Try a tool

​Connection lifecycle

​Transport details

​Troubleshooting

Connect your client

Try a tool

Connection lifecycle

Transport details

Troubleshooting