apiwatch

All changes / GitHub MCP Server

Breaking mcp

From v1.10.0, the GitHub MCP server in HTTP mode refuses to start when the static --tools list contains an unknown tool name, instead of falling back to the full tool inventory

Took effect · Server configuration --tools / GITHUB_TOOLS in HTTP server mode — unknown tool names

Reviewed against the vendor source on Sep 24, 2026 (AI-assisted review). Key facts are re-checked against the source daily.

What changes

Issue #2933 reported that the HTTP server's static-inventory path replaced an invalid --tools entry with the full tool inventory, although the README says invalid tool names cause startup failure. v1.10.0 (PR #3050) propagates the validation error, so an HTTP-mode deployment with an unknown name in --tools or GITHUB_TOOLS that used to start with every tool exposed now fails to start. The fix is confined to the HTTP server path.

Breaking: Calls fail after this date.

What to do

Before upgrading an HTTP-mode deployment to v1.10.0, check every name in --tools / GITHUB_TOOLS against the server's current tool list and correct or remove unknown names; while a name was invalid, that deployment was exposing the full tool inventory.

Strings to search for

--toolsGITHUB_TOOLS

Not affected (matches inside these are ignored): "stdio", "--tools"

Counts only in files that mention github-mcp-server.

Source

https://github.com/github/github-mcp-server/releases/tag/v1.10.0