Github copilot not setting bearer token on acces to tools.

[bzuidgeest]

Describe the bug
I have created an MCP server and I am trying to use it in visual studio 2026 with github copilot. I created an .mcp.json for the solution and I managed to authenticate using oauth using the codelens ui for that file. When saving the .mcp.json file Visual Studio supplies the bearer token to the MCP server and it is marked as online.

But when copilot chat tries to access it, the bearer token is not included in the request. But the server still shows connected in the config. I don't know if this is a problem with this library or not. If I execute the tools using the bearer token and postman it all works. But github copilot does not try to supply the token.

Do I need to add anything special in the way of attributes or such to get copilot ai to understand it needs to supply the bearer token when calling tools?

To Reproduce

1. Authenticate the mcp server
2. Try to use the tool in the chat. No token gets send.

Expected behavior
copilot chat should send the bearer token to the mcp server

Logs

Additional context

[PederHP]

This seems like an issue for VS Code / GitHub Copilot and not the SDK, given that it works using other clients?

[bzuidgeest]

That is quit possible, but I don't know why the bearer token is not included. I also used the "report a problem" functionality to submit it to microsoft. But I was hoping someone here might have a suggestion or know that I missed something in for example the tool attribute configuration to show the tool needs authentication.
If there is no such thing. Then by all means close and forget about it.