Skip to content
Agent Radar

GitHub MCP server 2.1.0 adds issue artifact tools

Updated GitHub MCP server

Summary

GitHub MCP server 2.1.0 (November 3, 2026) adds two opt-in tools for issue artifacts, fixes merged state in PR lists and rejects oversized integers.

Tool
GitHub MCP server
Category
MCP servers
Date
Open source
Yes
License
MIT
MCP
Yes
Pricing
Not stated in the sources we cited.
Sources

GitHub released version 2.1.0 of its GitHub MCP server on November 3, 2026. The minor version bump comes from two new experimental tools that let an agent keep plans, instructions and references attached to an issue. Both are off unless you turn on a feature flag, so an upgrade does not change what your agent can call by default.

Release facts

FactDetail
ProductGitHub MCP server, repository github/github-mcp-server
Version2.1.0 (tag v2.1.0), the release after 2.0.3
Release dateNovember 3, 2026
New toolsissue_artifact_read and issue_artifact_write, behind the issue_artifacts flag
Behavior fixesMerged state in list_pull_requests; integer parameters at or above 2^63
LicenseMIT, per the repository's license file

Issue artifacts, opt-in only

PR 3554 adds issue_artifact_read, which lists or gets artifacts, and issue_artifact_write, which creates, updates or deletes them. Every call targets an issue by owner, repo and issue_number. Get, update and delete use the artifact number scoped to that issue, not a global ID.

The limits matter more than the feature list:

  • Off by default. The PR says the tools stay off even in Insiders mode until you enable issue_artifacts.
  • Read-only mode exposes only issue_artifact_read.
  • Lockdown mode rejects every artifact operation, because artifact responses do not say who wrote them, so the server cannot run its push-access check.
  • Scope. The tools declare the repo OAuth scope. The flag exposes the tools but does not grant any API access your token lacks.
  • No retries on writes. API failures come back as errors. List pages are capped at 100 artifacts.

Fixes that change output

  • Merged pull requests: PR 3468 fixes list_pull_requests reporting merged: false for merged PRs when the REST list response leaves out the merged field. The server now falls back to a nonzero merged_at. If you built contribution summaries from this tool, rerun them.
  • Huge integers: PR 3650 rejects integer parameters at or above 2^63. Before, such values slipped past the range check and reached the API as the minimum or maximum int, depending on the CPU. Schemas are unchanged; you now get the existing range error.

The rest is dependency bumps, a docs link fix and a switch of the repository's own issue triage from GitHub Models to agentic workflows, which does not affect the server.

Questions

Do I need to change my config to upgrade? No. The new tools are hidden unless you enable issue_artifacts, and the two fixes keep the same tool schemas.

Can I use issue artifacts with lockdown mode on? No. The PR states every artifact operation is rejected in lockdown mode.

What counts as an artifact? The PR describes plans, instructions and references stored on an issue, with a name and a body. Its test run listed an existing Slack link on an issue as an artifact.

For the first stable release, see GitHub MCP server 1.0.0. For how to pick toolsets, read GitHub MCP server tools: which toolsets to turn on. More servers are in the MCP servers category.

Alternatives

GitHub MCP server compared with its alternatives
ToolLicensePricing note
GitHub MCP serverThis launchGitHub's official MCP server: 92 tools in 22 toolsets, 45 on by default. Version 2.1.0 shipped November 3, 2026 with opt-in issue artifact tools.
Open sourceThe server repository is public. GitHub product charges, if any, are your existing GitHub plan.
Model Context Protocol ServersGitHub repository of Model Context Protocol servers, shipped as npm and PyPI packages such as filesystem and git.
—Not stated
Playwright MCPMicrosoft's Apache-2.0 MCP server that lets LLM agents drive a browser through Playwright accessibility snapshots instead of screenshots.
Apache-2.0Apache-2.0 and free to run with npx. You pay your model provider for the agent that calls it.

More from GitHub MCP server

View all

  • GitHub MCP server 1.0.0

    GitHub MCP serverGitHub shipped MCP server 1.0.0 on April 16, 2026, with organization issue fields and an MCP Apps feature flag.

Questions

What is the GitHub MCP server?

It is GitHub's Model Context Protocol server, repository github/github-mcp-server. It runs as a GitHub-hosted remote server or locally, and lets an AI host read and change repositories, issues, pull requests, Actions and security alerts.

How many tools does it have?

The README for the local server lists 92 distinct tools across 22 toolsets as of November 4, 2026. With no configuration it loads the default set: context, repos, issues, pull_requests and users, which is 45 tools. The remote server adds Copilot, Copilot Spaces and support-docs toolsets.

What is new in 2.1.0?

Released November 3, 2026, it adds issue_artifact_read and issue_artifact_write behind the issue_artifacts feature flag, fixes merged state in list_pull_requests and rejects integer parameters at or above 2^63.

What are alternatives?

Functionize's MCP server exposes application tests. TinyFish exposes web search and browsing. Neither replaces GitHub issues and pull requests.

Filed on Agent Radar. Claims in this note are limited to the sources above.