Support OAuth http MCP servers

[Tiberriver256]

Describe the feature or problem you'd like to solve

Would love to be able to work with the new remote Figma MCP server or the Atlassian MCP server both of which use OAuth

Additional context

• Figma Remote MCP Server
• Atlassian MCP Server
• MCP OAuth2 Spec

[scr4bble]

Does copilot-cli share the same restrictions as copilot coding agent? In other words - would solving this feature request automatically lift the same restriction in copilot coding agent?

[dmytroslotvinskyy]

It`s not possible to use mcp with oauth 2.1 and redirect URL

[scr4bble]

It`s not possible to use mcp with oauth 2.1 and redirect URL

@dmytroslotvinskyy can you please make your statement more specific? This issue is flagged as "Feature enhancement" so if you just comment on the current state of things - yes, that is clear.

[Asylvestre]

Any updates on this? we would be willing to swap from claude code to copilot cli if these features are coming.

[Tiberriver256]

Temporary workaround is to use this:
https://github.com/steipete/mcporter

[levkach]

Temporary workaround is to use this: https://github.com/steipete/mcporter

would you mind elaborating how you've set it up? the tool doesn't autodiscover the mcps from ~/.copilot/mcp-config.json out-of-the-box.

[chrisnelmes]

+1

[alefranz]

Hello! is there any update on this feature request?
This is also required to be able to use background agents in Visual Studio Code, given it relies on the Copilot CLI.
Thanks!

[rysweet]

any updates here? w in MSFT would need this to be able to use eng.ms 1eschat map

[Tiberriver256]

Good news on the horizon

[ellismg]

In 0.0.389 we released support for OAuth MCP Servers that support Dynamic Client Registration (DCR).

We don’t yet support the newer CIMD standard which solves some of the client registration issues that DCR brings up, so if the MCP server you’re trying to connect to requires CIMD, we don’t support that yet (I’d love to hear more about the MCP server you’re trying to use in this case so I can make sure it works as I build out our CIMD support). #1305 tracks adding support for CIMD to the CLI.

If you are using existing remote servers with an explicit Authorization header that you have configured, this should have no impact of your day to day. The OAuth codepaths only light up when we fail to authenticate by default, so if you are explicitly getting a token and configuring the remote server there should be no changes to your workflow.

Feedback welcome - we’ll keep pushing on great MCP support in copilot!