Skip to content
OpenHelm logo

OpenHelm MCP server

Which servers in the official MCP registry are OpenHelm's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-13

← Back to OpenHelm

Whose server it is
  • Registry nameai.openhelm/deep-researchverified in the MCP registry

The registry name sits under openhelm.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-13
  • Staterequires sign-inchecked 2026-10-13

On 2026-10-13 the server answered and asked for a sign-in with a OpenHelm account (OAuth). It shows its tool list only to signed-in users, so we list none here.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "deep-research": {
      "type": "http",
      "url": "https://mcp.openhelm.ai/research/mcp"
    }
  }
}

The first time it connects, the client opens a OpenHelm sign-in.

Other servers listed as OpenHelm's
  • ai.openhelm/dev-changesanswers, requires sign-inverified in the MCP registry
  • ai.openhelm/email-outreachanswers, requires sign-inverified in the MCP registry
  • ai.openhelm/monitoringnot asked yetverified in the MCP registry
  • ai.openhelm/openhelmnot asked yetverified in the MCP registry
  • ai.openhelm/seo-growthnot asked yetverified in the MCP registry

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.