GitHub MCP Server v2.0.1 repo
GitHub's own MCP server crossed a major version to 2.0, replacing loosely typed JSON tool outputs with typed tool schemas and typed outputs across repos, search, security alerts, comments, and discussions. The prior release, 1.14.0 on October 2, 2026, added governance tools to read and manage repository rulesets and custom properties at the repository, organization, and enterprise level.
What it does for you: Gives Axion's GitHub facing agent calls structured, validated outputs instead of loosely typed JSON, which should cut parsing errors in any skill that reads GitHub data. The new ruleset and custom property tools let an agent check repo governance settings directly instead of YY checking by hand.
In practice: Reads like a vendor quietly hardening a tool everyone already depends on, not a flashy relaunch.
For: Both runtimes. A standalone MCP server process, usable by any MCP client whether the caller is an Axion or a Hermes agent.
Verdict: test first. Official, highly credible vendor and a real improvement, but a major version jump from 1.x to 2.0 changes output shapes, so this earns a test pass against Axion's existing GitHub MCP usage before it goes into the daily path.
Build #1 GitHub MCP Server v2.0.1: use the ai-implementation-build-intake skill to build this safely. Source: https://github.com/github/github-mcp-server/releases/tag/v2.0.1. Save canonical skill/agent under AXION\Skills and AXION\Agents.
Source · Version 2.0.1 is the current latest release. The prior governance release, 1.14.0, shipped October 2, 2026. Pull request numbers in the typed schema rollout run into the 3400s, for example pull request 3407.