Connect HelpKit to any other MCP client – HelpKit

HelpKit is a standard remote MCP server, so it works with any client that speaks MCP over HTTP. Windsurf, Zed, Continue, the Gemini CLI and anything you have built yourself all qualify. Only the wording of the settings changes.

What to look for in your client

Find where your tool configures an MCP server, a connector, a remote server or a tool server, then make sure of two things:

The transport is HTTP or Streamable HTTP, not stdio and not SSE

The address is https://connect.helpkit.so/mcp

The standard configuration

Most clients accept this shape:

{
  "mcpServers": {
    "helpkit": {
      "url": "https://connect.helpkit.so/mcp"
    }
  }
}

If your client supports signing in through a browser, it opens a HelpKit page the first time it connects. Sign in, click Approve, and you are done.

If your client cannot open a browser

Use a key instead. Create one in Account Settings → MCP, under Connected clients & keys, and pass it as a header:

{
  "mcpServers": {
    "helpkit": {
      "url": "https://connect.helpkit.so/mcp",
      "headers": {
        "Authorization": "Bearer hk_YOUR_KEY"
      }
    }
  }
}

Both routes give exactly the same access. The browser sign-in is simply tidier, because there is no key to store or rotate.

Check it worked

Ask your assistant:

Check my HelpKit setup status.

If it names your projects, the connection is good.

If it does not work

The usual culprits are the wrong transport, a truncated address, or a key pasted without the word Bearer.

Fixing a HelpKit MCP connection that will not work