GitHub replaces MCP server instructions with filtered skills in version 2.2.0
GitHub has released version 2.2.0 of its MCP server. It replaces server instructions with filtered MCP skills and adds optional secret hiding to the tools that handle secret scanning alerts.
GitHub released version 2.2.0 of its MCP server on 16 November. The release notes give each change only a one-line title and a link to the change, so the details remain unclear.
MCP is a protocol that lets an AI application use external tools. GitHub’s MCP server gives a coding agent, for example, tools to read and work with repositories, issues and pull requests.
The main change concerns server instructions: text that an MCP server gives an application at the start of a connection to explain how to use its tools. In version 2.2.0, filtered MCP skills replace them. A skill is a package of instructions that an agent uses only when a task needs it. The release notes do not say how the skills are filtered.
The second user-facing change involves GitHub’s secret scanning, which searches repositories for leaked keys and passwords, for example, and raises alerts about what it finds. The tools that handle these alerts now have optional secret hiding. The release notes do not explain how to enable it or whether it is on by default.
The release also adds public agent automation tools and two fixes: one for returning empty completion results and one for handling validation errors.
GitHub’s documentation says the MCP server is available to all GitHub users regardless of plan, but each tool requires the same permissions and paid licences as the corresponding GitHub feature. Users can connect to a remote server hosted by GitHub or run the server on their own machine. GitHub recommends the remote server for most users. Installation instructions are in GitHub Docs and the server’s repository.
Read more: How an agent works · Agent map