MCP server · General-purpose

A virtual computer your agent spins up for any task.

OpenHelm gives your assistant a secure remote environment: a stealth browser, a code runner, file access and more. Write a task in natural language, get back structured, evidence-backed results. Zero-install MCP server or REST API, your choice.

General-Purpose
Tool call
Sandbox
Result
Call run_task from my assistant.

now

Assistant called run_task
OpenHelm spun up a cloud sandbox
Working through the task…
Evidence-backed result returned
Where shall we steer?
General-Purpose · live

What it does

The general-purpose server gives your assistant the keys to a full virtual computer. Rather than a fixed opinionated workflow, it exposes the OpenHelm /v1 engine directly: define a task in natural language, optionally pin a JSON output schema, and the agent executes it inside an isolated cloud environment with a stealth browser and code execution, returning structured, evidence-backed results.

It is the right server when you are building custom automations, prototyping in Cursor, or want full control over prompts and output shape rather than a domain-specific toolset.

Endpoint

Add this URL to your MCP client.

Remote MCP URL
https://mcp.openhelm.ai/main/mcp
Local bridge (optional)
npx mcp-remote https://mcp.openhelm.ai/main/mcp

Tools

What your assistant can call.

Available on https://mcp.openhelm.ai/main/mcp

run_task

Execute an inline natural-language prompt, with an optional structured JSON output schema.

create_project

Establish a container to organise jobs and runs.

list_projects

Fetch the projects belonging to your organisation.

create_job

Store a reusable, named agent task template.

run_job

Trigger an instance of a stored template with input parameters.

list_runs

Retrieve historical run logs.

check_result

Query status and retrieve the results of an active or completed task.

Get started

Connect in under a minute.

  1. 1

    Add the remote server

    In ChatGPT, Claude, Cursor or any MCP client, add a remote connector pointing at https://mcp.openhelm.ai/main/mcp. No install, no terminal, no Node setup. For clients that need a local bridge, run npx mcp-remote https://mcp.openhelm.ai/main/mcp.

  2. 2

    Connect your OpenHelm account

    Click Connect and you are sent to app.openhelm.ai/connect to authorise via OAuth 2.1. Your encrypted OpenHelm API key is wrapped in a signed token, the server itself stores no secrets.

  3. 3

    Add a card to start the trial

    New accounts add a card to activate a 14-day free trial (you are not billed during the trial). This keeps the shared cloud compute protected from multi-account abuse.

  4. 4

    Run tasks from your assistant

    Ask your assistant in plain English. It calls the right tool, OpenHelm spins up an isolated cloud browser sandbox, and returns evidence-backed structured results, polling check_result for longer runs.

Prefer to call the engine directly from your own product? The same primitives are available over REST.

Build on the OpenHelm API→

Common questions about the General-Purpose server

Want it run for you instead?

The MCP servers put the tools in your assistant. If you'd rather we run the whole workflow as a managed service, book a 20-minute call and we'll scope it.