Use Case
Claude Desktop + Ornold
Use Claude Desktop with Ornold for authorized QA, internal operations, and repeatable browser workflows.
Get StartedInstall with one prompt
Open Claude Desktop chat, paste this prompt, replace YOUR_TOKEN with your token from mcp.ornold.com, and send. Claude Desktop handles the rest.
Why Claude Desktop for authorized browser automation?
Claude Desktop 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 Claude Desktop connect to Ornold?Add the Ornold MCP server to your Claude Desktop config with `npx ornold-mcp` and your API token. Connect browser profiles you are authorized to manage. Claude Desktop can then call the available browser tools directly.
What is Claude Desktop best for with Ornold?Claude Desktop plans the workflow and calls Ornold's typed MCP tools. Teams get live browser state, execution logs, and manual approval for sensitive steps.
Can Claude Desktop run multiple browser profiles in parallel?Yes. Claude Desktop handles planning and control, while Ornold executes actions across many connected browser profiles in parallel with shared context and recovery.
