Tool 'get_me' not found with GitHub MCP dynamic toolsets in Claude Desktop?

5 answers

• Best answerAgentArmor teamTeam3d ago

  Dynamic toolsets shipped officially in github-mcp-server v0.2.0 (Docker tags latest and v0.2.0), enabled with GITHUB_DYNAMIC_TOOLSETS=1: the server starts with 4 tools and enables more as the model requests actions. One user running it locally on Docker reported it works very well.

  The Tool 'get_me' not found symptom in Claude Desktop was reported in the thread but never confirmed as a server bug. A maintainer said dynamic toolsets "should work for any host applications that support tool change notifications," pointed to a Reddit thread of Claude Desktop users with the same experience, and added "Perhaps it is not supported yet." So the likely cause is that Claude Desktop does not yet apply the server's tool change notifications, but that was not confirmed.

  Setup used in the thread (.vscode/mcp.json):

  jsonCopy to clipboard

  {
      "inputs": [
          {
              "id": "github-pat",
              "type": "promptString",
              "description": "Github Personal Access Token",
              "password": true
          }
      ],
      "servers": {
          "github-mcp-server": {
              "type": "stdio",
              "command": "docker",
              "args": [
                  "run", "-i", "--rm", "-e", "GITHUB_DYNAMIC_TOOLSETS=1", "-e", "GITHUB_PERSONAL_ACCESS_TOKEN", "ghcr.io/github/github-mcp-server:main",
                  "./github-mcp-server", "stdio"
              ],
              "env": {
                  "GITHUB_PERSONAL_ACCESS_TOKEN": "${input:github-pat}"
              }
          }
      }
  }
  

  Known limitations from the thread:

  • A user asked whether dynamic toolsets work with GitHub's remote MCP server; that question was never answered.
  • --read-only does not restrict dynamically enabled tools: one user could still submit a PR approval with both --read-only and dynamic toolsets on. A maintainer agreed this should change and called it a candidate breaking change.
  • Another user reported agents still fail to discover tools (especially for PR creation) and switched most operations to the gh CLI. A maintainer said they are also exploring consolidating tools, but combining read and write tools forces approval prompts on read actions in some agents.

  Security note: with GITHUB_DYNAMIC_TOOLSETS=1, do not rely on --read-only to block write actions.

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What @eden881 tried on GitHub (Worked)

  Ran the server locally on Docker with dynamic toolsets enabled and reported it works very well.

  Source: https://github.com/github/github-mcp-server/issues/275#issuecomment-3074800620 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What @nathaliellenaa tried on GitHub (Didn't work)

  Used Claude Desktop with dynamic toolsets; searching for issues assigned to the user raised Tool 'get_me' not found and the available tool count never increased.

  Source: https://github.com/github/github-mcp-server/issues/275#issuecomment-3081815578 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What @danbarr tried on GitHub (Didn't work)

  Ran the server with both dynamic toolsets and --read-only and was still able to submit a pull request approval through it.

  Source: https://github.com/github/github-mcp-server/issues/275#issuecomment-3286942296 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport
• AgentArmor teamTeam3d ago

  What @chalkplum tried on GitHub (Didn't work)

  Reported agents frequently cannot discover tools, especially for PR creation, and switched most operations to the gh CLI.

  Source: https://github.com/github/github-mcp-server/issues/275#issuecomment-4470783784 (opens external site) ↗

  Did this work for you?WorkedDidn't work
  UpvoteStarReport