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.

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

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?