[FEAT]: Support MCP servers

[QuinnBast]

Describe the need

Currently this implementation does not support MCP servers, it can only do basic tool calls. This is a feature request to add support for MCP tools to the SDK.

I tried getting the Copilot to call Jira MCP, but it kept complaining that it didn't have access to search_jira MCP tools, even though these tools are available in my IDE.

It would also be nice to be able to view connected MCPs and list available tools through the session

SDK Version

No response

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct

[QuinnBast]

I see a new MR has been created, that is awesome and I'm eager to try it out!

But does this MR actually get the copilot agent to use the user's MCPs? It adds support to the SDK that lets the user view and query current MCP status, but does it actually get the agent that gets created to use the user's MCP configuration file? I think the issue here is that the agent that the SDK creates when it creates new sessions, for whatever reason, doesn't know how to find the user's mcp.json file. I have mine at ~/.copilot/mcp-config.json, and this works for the copilot CLI, but if I talk to copilot through the SDK it can't use any of the MCP tools. So I think there's a bigger issue at play here with how Copilot sessions are being created through the SDK.