Zenhub MCP Server

MCP server for ZenHub GraphQL API

Local serverstdioTypeScript

What is the Zenhub MCP MCP server?

MCP server for ZenHub GraphQL API. That is what the zenhub mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

An MCP (Model Context Protocol) server that provides full access to the ZenHub GraphQL API.

  • Full GraphQL Access — Execute any GraphQL query against the ZenHub API
  • Common Operations — Built-in tools for frequent tasks like creating issues, epics, workspaces, and sprints
  • Secure Authentication — API key-based authentication for all requests
  • Error Handling — Comprehensive error handling and validation

The tools it exposes

The server publishes 14 tools. What each one is for:

  • zenhub_query — Execute any GraphQL query against the ZenHub API. - query (required): GraphQL query string - variables (optional): Variables for the query
  • zenhub_search_issues — The zenhub_search_issues tool exposed by this server
  • zenhub_search_issues_in_repository — The zenhub_search_issues_in_repository tool exposed by this server
  • zenhub_get_workspace_issues — The zenhub_get_workspace_issues tool exposed by this server
  • zenhub_get_viewer — The zenhub_get_viewer tool exposed by this server
  • zenhub_get_issue_by_info — The zenhub_get_issue_by_info tool exposed by this server
  • zenhub_get_repositories — The zenhub_get_repositories tool exposed by this server
  • zenhub_create_issue — The zenhub_create_issue tool exposed by this server
  • zenhub_close_issues — The zenhub_close_issues tool exposed by this server
  • zenhub_reopen_issues — The zenhub_reopen_issues tool exposed by this server
  • zenhub_move_issue — The zenhub_move_issue tool exposed by this server
  • zenhub_add_assignees_to_issues — The zenhub_add_assignees_to_issues tool exposed by this server

What it needs from you

Configuration is passed through the environment: ZENHUB_API_KEY, GITHUB_PAT. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Getting it running

npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Zenhub MCP's toolset — zenhub_query, zenhub_search_issues, zenhub_search_issues_in_repository and 11 more — is a fair guide to whether it matches your workflow. It is maintained by derekbar90; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Zenhub MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
zenhub_queryExecute any GraphQL query against the ZenHub API. - query (required): GraphQL query string - variables (optional): Variables for the query
zenhub_search_issuesThe zenhub_search_issues tool exposed by this server.
zenhub_search_issues_in_repositoryThe zenhub_search_issues_in_repository tool exposed by this server.
zenhub_get_workspace_issuesThe zenhub_get_workspace_issues tool exposed by this server.
zenhub_get_viewerThe zenhub_get_viewer tool exposed by this server.
zenhub_get_issue_by_infoThe zenhub_get_issue_by_info tool exposed by this server.
zenhub_get_repositoriesThe zenhub_get_repositories tool exposed by this server.
zenhub_create_issueThe zenhub_create_issue tool exposed by this server.
zenhub_close_issuesThe zenhub_close_issues tool exposed by this server.
zenhub_reopen_issuesThe zenhub_reopen_issues tool exposed by this server.
zenhub_move_issueThe zenhub_move_issue tool exposed by this server.
zenhub_add_assignees_to_issuesThe zenhub_add_assignees_to_issues tool exposed by this server.
zenhub_add_labels_to_issuesThe zenhub_add_labels_to_issues tool exposed by this server.
zenhub_set_estimateThe zenhub_set_estimate tool exposed by this server.

How to install the Zenhub MCP MCP server

{
  "mcpServers": {
    "zenhub": {
      "command": "npx",
      "args": ["-y", "npm"],
      "env": {
        "ZENHUB_API_KEY": "your-value",
        "GITHUB_PAT": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
ZENHUB_API_KEYCredential the server authenticates with.Yes
GITHUB_PATConfiguration value read at startup.Optional

Example prompts to try

  • Use Zenhub MCP to zenhub query.
  • Use Zenhub MCP to zenhub search issues.
  • Use Zenhub MCP to zenhub search issues in repository.

Frequently asked questions

It connects Zenhub MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (zenhub_query, zenhub_search_issues, zenhub_search_issues_in_repository, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Zenhub MCP directly.