Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.pre.dev/llms.txt

Use this file to discover all available pages before exploring further.

One pre.dev MCP server, all the tools. Install it once and your agent gets browser_agent (browser automation) plus fast_spec / deep_spec (the Architect Agent) in one shot.

​
Quick Start

1

Get your API key

Get API Key

Visit the playground to copy your API key.
2

Install the MCP server

Run this in your terminal:
claude mcp add --transport http predev https://api.pre.dev/mcp
Your browser opens to authorize — sign into pre.dev (if not already) and pick which account or organization to connect.
See the Claude Code MCP docs for MCP basics.
3

Try it

Ask your agent:
Use pre.dev browser_agent to extract the top 10 stories from
news.ycombinator.com with title, url, and points.
Your agent calls the browser_agent tool and returns structured JSON.

​
Example prompts

Use pre.dev browser_agent to extract the top 10 products from
https://www.producthunt.com with name, tagline, and upvote count.
Return a JSON array.

​
Live event streaming

Every step of a task emits an MCP notifications/message frame. The taskIndex field ties each event to a specific task in the batch. Your agent sees:
  • navigation — the agent loaded a URL
  • plan — the agent decided what to do next
  • action — a click, type, or scroll executed
  • screenshot — a screenshot was captured
  • done — the task completed
Event shapes are identical to the REST SSE stream — see Run a Task → SSE frames.

​
Auth

PREDEV_API_KEY is all you need. The key is your personal SuperTokens userId (solo) or your enterprise org API key. Same key works for REST and MCP.

​
Troubleshooting

  • Restart your client after adding the MCP config
  • Verify the URL is exactly https://api.pre.dev/mcp
  • Check JSON syntax in your config file
  • Confirm your API key is valid at pre.dev/projects/browser-agents
  • Make sure the Authorization header starts with Bearer (with the space)
  • Solo accounts: use your personal key. Enterprise: use the org key from your org settings
  • Check your subscription is active
browser_task, browser_task_list, browser_task_get still work as aliases — old integrations continue working without changes.