How to Connect Zenhub to Gemini — via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Zenhub, paste your credentials, mint an MCP API key — done. No Docker, no git clone, no local server.

Zenhub + Gemini

Work with Zenhub boards from an AI agent through the GraphQL API: workspaces, pipelines and the issues in them, issue details, sprints and their issues, epics and their child issues, estimates; move issues, set estimates, plan sprints, create issues and comment. 17 typed tools plus a generic query tool, personal API key.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

ZENHUB_API_KEY

Step 1 — Get credentials

The connector talks to the Zenhub GraphQL API with a personal API key. The key acts as its user: workspaces and repositories that user cannot see are missing from every result.

1. In Zenhub open the API section of the dashboard (https://app.zenhub.com/settings/tokens) and create a Personal API Key for the GraphQL API. A user can have up to 5 keys.
2. Copy the key right away (it is shown once) and paste it into ZENHUB_API_KEY without Bearer in front. A legacy REST token does not work here.
3. Call zenhub_get_viewer to check the key, find a workspace with zenhub_search_workspaces, then read the board with zenhub_list_pipelines and zenhub_list_pipeline_issues.

Things to know:

• Each key gets 90 seconds of processing time per minute and at most 30 concurrent requests, and one query may not exceed 200 complexity points. That is why the list tools return 10 to 30 items by default; page with after set to pageInfo.endCursor.
• Zenhub ids are opaque strings. The write tools need the Zenhub issue id, not the issue number.
• For what the typed tools do not cover (releases, roadmaps, dependencies, priorities, labels), use zenhub_graphql_query or zenhub_graphql_mutation.
• zenhub_move_issue, zenhub_set_estimate, zenhub_add_issues_to_sprints, zenhub_create_issue and zenhub_add_comment change the board or post content the team sees.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Gemini

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Gemini CLI reads MCP servers from ~/.gemini/settings.json (on Windows %USERPROFILE%\.gemini\settings.json). Add:

{
  "mcpServers": {
    "anythingmcp": {
      "httpUrl": "https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID",
      "headers": { "X-API-Key": "YOUR_MCP_API_KEY" }
    }
  }
}

1. Create an MCP API key in AnythingMCP under MCP Servers → your server → API keys, and paste it in place of YOUR_MCP_API_KEY.
2. Save the file and restart gemini.
3. Run /mcp inside Gemini CLI (or gemini mcp list in your shell) — anythingmcp should show as connected.
4. Start prompting — Gemini CLI can now call the Zenhub tools.

Available tools

FAQ

Where does Gemini CLI look for MCP servers? In ~/.gemini/settings.json for your user, or in .gemini/settings.json inside a project. gemini mcp list shows each server and whether it connects.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Meta Muse