Developer · Remote MCP server
Openhelm
Autonomous cloud agent tasks: real browser + your tools, structured evidence-backed results.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.openhelm/openhelm- Version
- 0.1.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-11
- Updated
- 2026-07-11
- Publisher
- ai.openhelm · 6 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain openhelm.ai · how
- Listed under
- Browser automation MCP servers
- Website
- openhelm.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.openhelm.ai/main/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Openhelm
Openhelm is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.openhelm.ai/main/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from ai.openhelm
| Server | Runs |
|---|---|
| Deep ResearchAutonomous buy-side research: diligence, earnings, SEC filings, comp sets. Source-cited real data. | Remote · HTTPLive check: sign-in required |
| Dev ChangesTurn described changes into reviewed pull requests: propose, triage, review, dependency audits. | Remote · HTTPLive check: sign-in required |
| Email OutreachGoal-directed email outreach: research, draft, send, triage replies. Real data, never fabricated. | Remote · HTTPLive check: sign-in required |
| MonitoringSite & competitor monitoring: snapshots, evidence-backed diffs, briefs, price checks, mentions. | Remote · HTTPLive check: sign-in required |
| Seo GrowthAutonomous SEO + GEO growth: keyword research, audits, content, AI answer-engine visibility. | Remote · HTTPLive check: sign-in required |
More developer servers
| Server | Runs |
|---|---|
| OpenDocsWrite, organize and publish documentation sites, help centers and SOPs on OpenDocs.cloud. | Remote · HTTPLive check: sign-in required |
| Openflowkit MCPLocal-first OpenFlowKit diagramming tools for Claude, Cursor, Windsurf & other MCP clients. | Local · stdio |
| Opengate MCPCheck whether an AI answer is grounded in its context - deterministic, no LLM judge. | Local · stdio |
| OpenharnessLets AI coding agents discover and reference each other's recent sessions. | Local · stdio |
| openITCOCKPITOpenITCOCKPIT monitoring: host and service state, history, downtimes, acknowledgements, patches. | Local · stdio |
| openLCA MCP ServerConnect AI assistants to openLCA. 35 tools for database search, model building, and LCIA. | Local · stdio |
| OpenMayhemUse OpenMayhem text, embedding and media models with explicit cost controls. | Remote & Local · HTTP, stdioLive check: sign-in required |
| OpenOCD DebuggerDebug microcontrollers via OpenOCD: flash, breakpoints, memory, registers and variables. | Local · stdio |