Hi all,
I’m currently integrating HubSpot with Copilot Studio using Remote HubSpot’s MCP server.
The MCP server is configured with OAuth 2.1, and I’ve confirmed that the authentication flow works correctly using the MCP Inspector. However, when I try to connect to the same MCP server from an agent in Copilot Studio, the connection fails.
From what I can see, this appears to be related to the authentication protocol on the Copilot Studio side. It looks like the Copilot Studio MCP connector currently expects OAuth 2.0, which may be causing incompatibility with HubSpot’s OAuth 2.1 implementation.
My questions are:
- Does Copilot Studio’s MCP connector currently support OAuth 2.1, or if OAuth 2.1 is not yet supported, is there any roadmap or timeline for when it will be implemented?
- Has anyone found a workaround when integrating MCP servers that require OAuth 2.1?
Any insight or from others who’ve run into a similar issue would be greatly appreciated.
Thanks in advance


Report
All responses (
Answers (