GitHub MCP server 2.1.0 adds issue artifact tools
Updated 1 min read
Summary
Agent Radar 2026-11-04: GitHub MCP server 2.1.0 adds opt-in issue artifact tools and fixes merged state in PR lists. Plus a guide to its 22 toolsets.
Agent Radar tracked one launch as of 2026-11-04, covering the window 2026-10-28 to 2026-11-04 for tools we have not written about this week. It is a minor release of GitHub's MCP server, and the only change that alters output today is a bug fix in pull request lists.
At a glance
| Launch | Tool | Released | What changed |
|---|---|---|---|
| GitHub MCP server 2.1.0 adds issue artifact tools | GitHub MCP server | 2026-11-03 | issue_artifact_read and issue_artifact_write behind the issue_artifacts flag; merged PRs no longer listed as unmerged; integers at or above 2^63 rejected |
What changed
- New tools, off by default: the two artifact tools let an agent keep plans and references on an issue. Read-only mode exposes only the read tool, and lockdown mode blocks both.
- Fix to check:
list_pull_requestscould reportmerged: falsefor merged PRs. If a report or changelog was built from that output, rerun it after upgrading.
Questions
Does upgrading change what my agent can do?
No. The new tools stay hidden until you enable the issue_artifacts flag.
Which toolsets should I enable? The default five cover most coding work. Our new guide, GitHub MCP server tools: which toolsets to turn on, maps all 22 toolsets to jobs. Related reading: GitHub MCP vs reference MCP servers.
In this issue
Rank 1 GitHub MCP server 2.1.0 adds issue artifact tools
GitHub MCP serverGitHub 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.
Category: MCP servers
Pricing: Open source
