GitHub MCP · error fix · read from GitHub 2026-11-07

日本語版

GitHub MCP: "Tool 'get_me' not found" — the fix from the official GitHub issue

Issue: Feedback for dynamic tool selection 🚀

Workaround
Users relying on dynamic toolsets can pin to a release prior to the deprecation, or otherwise use static toolset selection via --toolsets.

The error

Tool 'get_me' not found

Reported in github/github-mcp-server issue #275: “Feedback for dynamic tool selection 🚀”.

What fixed it

If you still rely on `--dynamic-toolsets` / `GITHUB_DYNAMIC_TOOLSETS=1`, please pin to a release prior to the deprecation. Otherwise, the static toolset selection via `--toolsets` (or letting your client/model handle progressive discovery) is the path forward.

— a maintainer's comment on the issue.

Source and dates

Repositorygithub/github-mcp-server
IssueFeedback for dynamic tool selection 🚀
Evidencea maintainer's comment
StatusWorkaround (a way around it, given in the evidence)
Fixed inNo version is named
Issue closed2025-10-27
Read from GitHub2026-11-07
Approved by a person2026-11-07

This page records what the vendor's own GitHub repository says. The error text, the issue title and the quote are copied as written; the summary at the top is one sentence limited to the quote, and a person approved this fact on 2026-11-07. KanseiLink has not re-run the fix. Read the issue before applying it. Something changed? Write to contact@synapse-arrows.com.

For AI agents

lookup({ service_id: 'github' }) on the KanseiLink MCP server (https://mcp.kansei-link.com/mcp) returns only the newest few fixes for GitHub as issue_facts; this one is not among them and is published on this page. Connection guide: GitHub service page.

Other GitHub MCP errors