Gemini

The Gemini CLI configures MCP servers in its settings.json, under an mcpServers object.

Add the connector

heymcp share localhost:8000

Then in your Gemini CLI settings.json:

{
  "mcpServers": {
    "heymcp": {
      "httpUrl": "https://amber-jetty.t.heymcp.dev/mcp"
    }
  }
}

The key is httpUrl, not url. Gemini CLI uses httpUrl for the streamable HTTP transport and url for legacy SSE endpoints. HeyMCP serves streamable HTTP, so httpUrl is the one you want.

With a bearer token

If you shared with --bearer:

{
  "mcpServers": {
    "heymcp": {
      "httpUrl": "https://amber-jetty.t.heymcp.dev/mcp",
      "headers": {
        "Authorization": "Bearer s3cret"
      }
    }
  }
}

timeout is also accepted if a tool of yours is slow enough to need it.

Check it connected

Start the Gemini CLI and confirm your tools are listed. In the HeyMCP inspector you should see handshake rows fingerprinted as Gemini.

It’s not showing up

The server is ignored entirely

Almost always url where it should be httpUrl, or a JSON syntax error in settings.json.

Nothing in the HeyMCP inspector

Gemini never reached the edge. Check the URL and that heymcp share is still running.

401 in the inspector

The headers block is missing, or the token doesn’t match --bearer.

⌘I

Get started

Core concepts

Connect a client

Security

CLI reference

Checks

Account

Help

Changelog

Add the connector

With a bearer token

Check it connected

It’s not showing up

​Add the connector

​With a bearer token

​Check it connected

​It’s not showing up

Add the connector

With a bearer token

Check it connected

It’s not showing up