missing required parameter: query

[vorburger]

Describe the bug

GitHub MCP server does not work for me to query GitHub Issues with Copilot from within VSC due to:

missing required parameter: query

The same does work fine for me when using https://github.com/copilot.

Affected version

N/A, as using https://api.githubcopilot.com/mcp/.

Steps to reproduce the behavior

1. In GitHub Copilot in Visual Studio Code
2. I'm selecting Agent Mode and using GPT-4.1
3. and enabling all Tools of the remote GitHub MCP server,
4. using this mcp.json configuration:

   {
     "servers": {
       "github": {
         "type": "http",
         "url": "https://api.githubcopilot.com/mcp/"
       }
     }
   }

5. Prompting it with "How many issues are assigned to me on https://github.com/enola-dev/enola/issues ?"
6. It successfully "Ran Get my user profile" (so my credentials are working)
7. then it fails, due to:

Ran Search issues 
Completed with input: {
  "owner": "enola-dev",
  "repo": "enola",
  "q": "assignee:vorburger is:open",
  "perPage": 100
}

Ran Search issues 
Completed with input: {
  "q": "repo:enola-dev/enola assignee:vorburger is:open",
  "perPage": 100
}

There is a technical issue with the search tool: it requires the parameter to be named `query`, not `q`. I will retry using the correct parameter name. I am unable to retrieve the number of issues assigned to you due to a technical limitation with the available tools.

[vorburger]

The same prompt also does work from Gemini CLI, so this appears to be more of a problem in with Copilot from within VSC specifically.

[LuluBeatson]

Hi @vorburger, thank you for opening an issue.

I've not been able to reproduce the bug myself but I can see that the search_issues tool used to use a q param but it was renamed to query in June (#583). So your VSCode might have cached an older version of the tool schemas.

You can try clearing your MCP tool cache by Cmd+Shift+P/Ctl+Shift+P and searching for MCP: Reset Cached Tools:

Then go to your MCP config, restart your GitHub MCP server and try your issue search prompt again.

(optional) You can also check the tools schemas returned by the server in output logs

Go to your MCP config, click More... > Show Output:

Turn on Trace logs:

Restart your server again and you should see a large JSON response containing the tool schemas. You can search in here for search_issues and check that the arguments includes query not q.

Please let me know if you resolve this :)