OpenHelm via MCP & API

A virtual computer your agent calls for the work it can't do alone.

OpenHelm spins up a secure remote environment — a real stealth browser, a coding agent, an email inbox and more — to execute one-off or scheduled tasks on behalf of your AI. Access it via zero-install MCP servers in ChatGPT, Claude or Cursor, or call the REST API from your backend.

MCP call
Sandbox
Result
Schema
Call run_task from my assistant — "Research this company"

now

Assistant called run_task via MCP· tool_call_id
Agent working in a cloud sandbox
Extracting into JSON schema…
Structured result returned to assistant
Where shall we steer?
MCP + API · live

Two ways in

Your assistant gets the virtual computer. Or build it into your product.

Remote MCP servers

Add a URL in ChatGPT, Claude or Cursor — no install, no key handling. Your assistant gets tools that spin up a full virtual computer in the cloud to do the actual work.

REST API (/v1)

POST /v1/runs with a prompt + optional JSON output_schema. Projects, jobs, runs, connections and email — server-to-server from your own backend.

Stealth browser, deeper web access

The virtual computer drives a browser that is undetectable by anti-bot systems, giving the agent access to more of the web than standard automation tools.

Goals achieved, not just tasks dispatched

A monitoring layer watches work in progress and ensures the objective is actually reached — not just that a tool call returned a response.

Multi-step orchestration

Complex tasks are broken into sequential steps managed by an agentic system that adapts when things change, rather than a single prompt-to-output call.

Real budgets

Per-key monthly caps, an org daily cap, and a cost estimate on every started run. Usage draws from your plan's credits.

REST API

Or call it directly from your backend.

POST /v1/runs
curl https://api.openhelm.ai/v1/runs \
  -H "Authorization: Bearer oh_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "prompt": "Get the pricing tiers from stripe.com",
    "output_schema": { "type": "object",
      "properties": { "tiers": { "type": "array", "items": { "type": "string" } } } }
  }'
202 + poll/webhook
HTTP/1.1 202 Accepted
{
  "task_id": "run_2x9f4c...",
  "poll_url": "https://api.openhelm.ai/v1/runs/run_2x9f4c...",
  "billing": { "model": "sonnet", "estimated_cost_usd": { "low": 0.05, "high": 0.3 } }
}

# poll until done (or supply callback_url for a webhook):
curl https://api.openhelm.ai/v1/runs/run_2x9f4c... -H "Authorization: Bearer oh_live_..."

Full endpoints, the result envelope, webhooks, and the Connections API are in the developer docs, and the live API reference is generated from the deployed OpenAPI spec.

Get started via MCP

Connect in under a minute.

  1. 1

    Pick a server

    Choose from the purpose-built servers above, or start with the General-Purpose server for custom prompts and full API access from your assistant.

  2. 2

    Add the remote URL to your assistant

    In ChatGPT, Claude, Cursor or any MCP client, add the server URL as a remote connector. No install, no terminal, no Node setup required.

  3. 3

    Connect your OpenHelm account

    Click Connect and authorise via OAuth 2.1. Your encrypted OpenHelm API key is wrapped in a signed token — the server itself stores no secrets.

  4. 4

    Run tasks from your assistant

    Ask your assistant in plain English. OpenHelm spins up the virtual computer — stealth browser, code runner, or email environment — executes the task, and returns evidence-backed structured results.

Common questions

Give your agent a virtual computer. Zero-install.

Connect a remote MCP server in ChatGPT, Claude or Cursor in under a minute — stealth browser, coding environment, and email inbox ready to go. Or mint an API key and build OpenHelm directly into your own product.