Use Case

Cursor + Ornold

Build and test browser automations inside Cursor, then scale them through Ornold.

Install with one prompt

Open Cursor chat, paste this prompt, replace YOUR_TOKEN with your token from mcp.ornold.com, and send. Cursor handles the rest.

Install Ornold MCP for Cursor — browser automation for antidetect browsers.

Full install guide for AI agents: https://github.com/ornold-ai/ornold-mcp/blob/main/AGENTS.md

Before running anything, ask me these questions and wait for my answers:
1. Do I have an Ornold token (starts with orn_sk_)? If not, send me to https://mcp.ornold.com → Tokens → Create token.
2. Which antidetect browser do I use? Options: Linken Sphere, Dolphin Anty, Vision Browser, Wadex, or none yet. (This decides the antidetect flags — see AGENTS.md.)
3. Which interaction mode? "vision" (recommended for stealth — clicks via screenshots + coordinates) or "dom" (faster — clicks via CSS selectors). If unsure, default to vision. If I want both, set up two separate MCP servers (one per mode) so the tool list stays focused.
4. Do I have Node.js 18+ installed? If unsure, run "node -v". If missing, point me to https://nodejs.org.

Once I answer, install Ornold MCP for Cursor using the install method and flags from AGENTS.md, with the antidetect + mode flags from my answers. Then install the AI skill (npx mcp-ornold-browser --install-skill, where supported) and call browser_status to verify the MCP server is reachable.

Read full setup guide

Why Cursor for antidetect browser automation?

Cursor keeps code, browser feedback, and MCP actions in one workspace. That makes iteration faster when you need to debug real antidetect profiles.

Key Features

Parallel browser control

Navigate, click, fill forms, and run JS across all connected antidetect profiles simultaneously via MCP tools.

Automatic CAPTCHA solving

Detects reCAPTCHA, hCaptcha, Turnstile, and 9 other types. Solves them in parallel across all sessions.

Grouped vision analysis

Take screenshots from all sessions, analyze them as a batch, and group browsers by their visual state.

Real-World Use Cases

Workflow development

Iterate on one profile, then fan out to many once the flow is stable.

Attach active antidetect profiles

Run against one browser first

Inspect results and adjust the script

Expand to the full batch

API + browser tasks

Combine external data sources with browser actions in one run.

Fetch source data from an API

Transform it into per-profile payloads

Fill forms across browsers

Send collected results back to your backend

Frequently asked questions

How does Cursor connect to Ornold?Add the Ornold MCP server to your Cursor config with `npx ornold-mcp` and your API token. Connect your antidetect browser profiles via CDP. Cursor can then call all browser tools directly.

What is Cursor best for with Ornold?Cursor keeps code, browser feedback, and MCP actions in one workspace. That makes iteration faster when you need to debug real antidetect profiles.

Can Cursor run many antidetect profiles in parallel?Yes. Cursor handles planning and control, while Ornold executes actions across many connected browser profiles in parallel with shared context and recovery.

Codex Windsurf

Also works with