Skip to content

MCP server · Dev changes

A virtual coding environment that clones, changes, tests, and opens the PR.

OpenHelm gives your assistant an isolated cloud dev environment: clone the repo, make the smallest focused change, run the project's own tests, push, and open a reviewable PR. Also triages issues against real code, reviews diffs, and audits dependencies. Zero-install via MCP.

Connect the serverSee the tools ↓

What it does

The Dev Changes server gives your assistant a complete virtual coding environment. It starts a clean clone of the repo in an isolated cloud workspace, makes one focused change that matches the project's conventions, runs the actual test suite, then pushes and opens a reviewable PR. The agentic system manages the full flow, clone to PR, and stops to explain when a request needs a product decision rather than hacking around it.

It is built for engineering teams, indie developers and AI coding agents who want routine changes and maintenance handled as proper PRs. Real data only: it never fabricates a change, a PR URL, or a passing test, and when a request depends on missing credentials or a product decision it stops and explains the external fix rather than hacking around it.

Endpoint

Add this URL to your MCP client.

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

Tools

What your assistant can call.

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

  • open_pull_request

    Implement a described change and open a PR (clone, change, test, push-first).

  • propose_change

    Analyse the repo and propose a diff/plan without pushing.

  • triage_issue

    Reproduce/analyse an issue against the code; propose the smallest fix.

  • review_pull_request

    Review a PR or the latest changes: bugs, security, missing tests, conventions.

  • dependency_audit

    Audit outdated/vulnerable deps; propose safe bumps (optionally open a PR).

  • check_result

    Retrieve the finished result of a longer-running change.

Get started

Connect in under a minute.

  1. Add the remote server

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

  2. Connect your OpenHelm account

    Click Connect and you are sent to www.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. 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. 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.

Want recurring dependency upkeep and housekeeping PRs? The Repo & Developer Changes strategy runs it on a schedule.

Set up scheduled repo maintenance→

Common questions about the Dev Changes server

Do I need to install anything?

No. OpenHelm MCP servers are remote, Streamable-HTTP servers. You add a URL as a remote connector in ChatGPT, Claude, Cursor or another MCP client. Clients without native remote support can use the lightweight npx mcp-remote bridge.

Where does the work actually run?

Not on the MCP endpoint. When a tool is called, OpenHelm starts an asynchronous agent run in an isolated E2B cloud sandbox that drives a real browser and reads official sources. The MCP layer is stateless: it holds no database and stores no secrets.

What happens with long-running tasks?

The server uses a bounded-wait pattern of about 75 seconds. Fast tasks return their structured result in one turn. Slower tasks return a task_id and your assistant calls check_result a moment later to retrieve the finished output, so connections never time out mid-run.

How is it billed?

Connecting requires an OpenHelm account with a card on file, which starts a 14-day free trial. You are not charged during the trial. After that, usage runs on your OpenHelm plan.

More servers

Explore the rest of the OpenHelm MCP suite.

Developers, engineering teams & power users

General-Purpose

Spin up a virtual computer for any custom task, browse, run code, read data, and return structured results.

Investment analysts, VCs & corporate strategy teams

Deep Research

A virtual research environment that reads SEC filings, earnings prints, and live market data, grounded in official sources.

Growth marketers, content directors & SEO specialists

SEO & GEO

A virtual SEO environment: audit rankings, draft content, and measure AI engine citations of your brand.

Founders, sales & ops teams, and AI agents

Email Outreach

A virtual inbox your agent controls, send, monitor replies, and run the whole conversation to completion.

Product, marketing & competitive-intelligence teams

Site Monitoring

Watch websites, competitors and prices; get evidence-backed diffs and briefs instead of noisy pixel alerts.

Sales, support & operations teams · soon

Phone Reach-Out

A virtual phone your agent uses to call, converse, and act on the outcome, coming soon.

Sales, support & operations teams · soon

WhatsApp Reach-Out

A virtual WhatsApp inbox your agent uses to message, handle replies, and achieve the goal, coming soon.

Operations, procurement & personal assistants · soon

Online Buying

A virtual shopper that sources products, compares options, and checks out within your guardrails, coming soon.

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.

Book a demoAll MCP servers →