Skip to content

missing required parameter: query #1084

Description

@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.

Activity

  1. vorburger commented on Sep 13, 2025

    @vorburger
    ContributorAuthor

    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.

  2. LuluBeatson commented on Sep 17, 2025

    @LuluBeatson
    Contributor

    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:
    Image

    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:
    Image

    Turn on Trace logs:
    Image

    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.
    Image

    Please let me know if you resolve this :)

  3. github-actions commented on Jul 1, 2026

    @github-actions
    Contributor

    This issue is stale because it has been open for 30 days with no activity. Leave a comment to avoid closing this issue in 60 days.

  4. github-actions commented on Aug 31, 2026

    @github-actions
    Contributor

    This issue was closed because it has been inactive for 60 days since being marked as stale.

  5. leuasseurfarrelds247-arch commented on Aug 31, 2026

    @leuasseurfarrelds247-arch

    5c91da6d5b9ba973968221e6885a3da279284e44

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingstale

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions