Use Case

Cursor + Ornold

Use Cursor with Ornold for authorized QA, internal operations, and repeatable browser workflows.

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 — AI browser automation for authorized workflows.

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 supported browser workspace do I use? Options: Linken Sphere, Dolphin Anty, Vision Browser, Wadex, or none yet. This selects the appropriate connector from AGENTS.md.
3. Which interaction mode should I use? Choose "vision" for visually dynamic pages or "dom" for stable pages with reliable selectors. If unsure, default to vision. If I need both, set up two separate MCP servers so each 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.
5. Confirm that I will use Ornold only with systems, accounts, and data I own or am authorized to manage.

Once I answer, install Ornold MCP for Cursor using the install method, browser connector, and mode from AGENTS.md. 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 authorized browser automation?

Cursor plans the workflow and calls Ornold's typed MCP tools. Teams get live browser state, execution logs, and manual approval for sensitive steps.

Key Features

Direct MCP tool access

Navigate, inspect page state, fill test forms, and run JavaScript through typed browser tools.

Vision and DOM modes

Use visual analysis for changing interfaces or structured references for predictable pages.

Logs and recovery

Preserve execution state and retry only authorized sessions that need attention.

Real-World Use Cases

Web application QA

Test interfaces your organization owns or is authorized to operate.

Connect test profiles

Open the test environment

Run the validation flow

Record results

Internal workflows

Automate repeatable operations inside approved internal tools.

Describe the approved task

Verify target profiles

Run steps with logging

Confirm final state

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 browser profiles you are authorized to manage. Cursor can then call the available browser tools directly.

What is Cursor best for with Ornold?Cursor plans the workflow and calls Ornold's typed MCP tools. Teams get live browser state, execution logs, and manual approval for sensitive steps.

Can Cursor run multiple browser 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