Do I use web_search tool providing github-mcp-server?

[misumisumi]

According to copilot-cli/issues/57, copilot-cli seems to provide the web_search tool through the github-mcp-server.
Currently, I have a Copilot Pro subscription via the student discount and have enabled Web Search under settings/copilot/features. However, the web_search tool does not appear in copilot-cli when running /mcp show, nor is it listed in the available tools. I have tried logging out and logging back in on both the GitHub CLI and Copilot CLI, but the situation remains unchanged. Is the web_search tool currently being provided?
Also, I belong to several organizations and am a collaborator in one of them—could this status be affecting its availability?
Authentication is tied to an individual.

[aniruddhaadak80]

My guess is this is less about org membership and more about how the tool is surfaced in the specific client path. A feature can be enabled at the account level and still not appear if copilot-cli is only exposing the subset that the connected MCP server or current rollout supports.nnIt would help if someone from the team clarified whether web_search is expected to appear in /mcp show at all, or whether it is injected through a different capability path. Right now the confusing part is not just missing access, it is that the discovery surface gives no clue whether the feature is unsupported, gated, or temporarily unavailable.

[SamMorrowDrums]

@misumisumi you are correct that the settings here should do it: https://github.com/settings/copilot/features

It is possible for orgs to limit this too I believe, I am asking for clarification.

[misumisumi]

Thank you for your replys.
First, Copilot Pro was not provided by an organization; I am paying for it personally. Therefore, I think that it is not subject to any organizational policies.
Next, the features are configured as shown in the image.

Finally, the following are the results of running copilot-cli with only the built-in features enabled (model: gpt-5.1-codex-mini):

• copilot

• copilot --add-github-mcp-toolset web_search

Even if I am using a personal subscription, could my membership in these organizations be the reason why certain features (like web search) are not appearing in the
CLI?

[jluocsa]

web_search is not a toolset provided by github-mcp-server. The complete list of toolsets that this server exposes (as documented in README — Available Toolsets) is:

• Local server: actions, code_security, context, copilot, dependabot, discussions, gists, git, issues, labels, notifications, orgs, projects, pull_requests, repos, secret_protection, security_advisories, stargazers, users
• Additional remote-only toolsets: copilot, copilot_spaces, github_support_docs_search

There is no web_search toolset on either path, which is why copilot --add-github-mcp-toolset web_search doesn't expose it — there's nothing to enable on the GitHub MCP server side. That setting flag just maps to the toolsets above.

The "Web Search" feature you toggled at https://github.com/settings/copilot/features is a separate Copilot platform feature; it's surfaced through whichever Copilot client integrates it, not via this MCP server. As of today the Copilot CLI does not seem to expose Web Search as an MCP tool — the toggle controls the in-product chat experience.

Your org memberships shouldn't matter here because (a) you're on a personal Pro subscription and (b) even if a stricter org policy applied, the result wouldn't be a missing toolset — it'd be a permission denial on a tool that does exist.

If you have a link to where copilot-cli/issues/57 claims web_search is provided through github-mcp-server, it would help to verify whether the doc is outdated or whether a separate integration is being planned. Right now, based on this repo's source, there is no such tool to discover or enable.