GitHub MCP Server 2.0 adds typed outputs and output schemas for agents that write code

What GitHub released

GitHub published version 2.0.0 of the GitHub MCP Server on 6 October 2026. The GitHub MCP Server is the company's open-source Model Context Protocol server, which lets AI agents read repositories, manage issues and pull requests, check Actions runs and review security alerts.

The release notes explain the reason for the major version. More agents now support what GitHub calls Code Mode or Programmatic Tool Calling, where the model writes code that calls tools instead of calling them one at a time. To support that, the server added structured outputs and output schemas, so a client knows the shape of each tool's result before it calls it. The pull requests in the release add typed inputs and outputs to tools for issues, pull requests, repositories, commits, search, GitHub Actions, security alerts, discussions, notifications and comments. A separate change caches the encoded tools/list schemas to cut repeated work.

What changed for MCP clients

The new schemas are only advertised to clients that declare support for the 2026-07-28 MCP specification or later. GitHub says its compound tools needed changes to the allowed output schemas that are not valid for older clients, so the server does not return those schemas to them. A client on an older protocol revision should therefore see the same tool shapes as before.

The 2.0 line needed three quick fixes. Version 2.0.1 on 7 October switched Go library users to the /v2 module path; the project README notes that the original v2.0.0 tag cannot be used as a Go module. Version 2.0.2 on 8 October restored HTTP header validation for typed tools. Version 2.0.3 on 21 October added cursor pagination to list_label, made get_file_contents return a resource link for files over 1 MB, and moved the build to Go 1.27.3 as a certificate authority mitigation.

Why it matters

Typed outputs matter more as agents move from calling one tool per turn to writing short programs that chain several calls. Without a schema, generated code has to guess field names in a result, which is a common source of failed runs. With one, a host can type-check or validate the code before running it. With more than 34,000 stars on its repository, GitHub's server is among the most visible MCP servers, so its adoption of the 2026-07-28 output schema rules gives client developers a large real-world target to test against.

The protocol-version gate is the other point to note. Rather than breaking older hosts, GitHub chose to serve the richer schemas only where the client has opted into the newer specification. That pattern, also used in the official MCP SDKs, is likely to become the norm as the 2026-07-28 revision spreads.

What to watch next

The release notes do not say when the hosted remote server picked up 2.0 or whether any client behavior changed for Copilot users. Watch for client support for 2026-07-28 in editors such as VS Code and in agent frameworks, since that decides who sees the new schemas. More MCP coverage is collected under AI Agents.

Questions people ask

Which clients see the new output schemas in GitHub MCP Server 2.0?

Only clients that advertise support for the 2026-07-28 MCP specification or later, according to the v2.0.0 release notes.

Do Go library users need to change anything?

Yes. Version 2.0.1 moved the module path to github.com/github/github-mcp-server/v2, and the README says the v2.0.0 tag cannot be used as a Go module.

Is the GitHub MCP Server free to use?

The server code is open source under the MIT license. Pricing for the hosted remote server is not stated in the announcement.

Sources

1. GitHub MCP Server 2.0.0 (GitHub, 6 Oct 2026)
2. GitHub MCP Server 2.0.1 (GitHub, 7 Oct 2026)
3. GitHub MCP Server 2.0.2 (GitHub, 8 Oct 2026)
4. GitHub MCP Server 2.0.3 (GitHub, 21 Oct 2026)
5. GitHub MCP Server README (GitHub, 28 Oct 2026)