HubSpot MCP with Copilot Studio: Connection succeeds but no tools load; MCP Auth App returns PKCE er

Hi Team,

I’m evaluating HubSpot MCP integration with Microsoft Copilot Studio and am seeing two different behaviors depending on how the HubSpot side is configured.

Environment:

Scenario 1: Using HubSpot app credentials

I configured Copilot Studio to connect to:

https://mcp.hubspot.com

The connection succeeds, but Copilot Studio shows:

  • No actions available
  • Empty JSON response ({})
  • No HubSpot tools are discovered

Scenario 2: Using a HubSpot MCP Auth App / MCP Server configuration

When I create and use the HubSpot MCP-specific authentication setup and attempt to connect from Copilot Studio, authentication fails with:

“Authorization failed because the code challenge parameter is missing. PKCE is required for this authorization request.”

The authorization request generated by Copilot Studio does not appear to include:

  • code_challenge
  • code_challenge_method=S256

Questions:

  1. Has anyone successfully connected https://mcp.hubspot.com directly to Copilot Studio and had HubSpot tools/actions load successfully?
  2. For Copilot Studio integrations, should we create a standard HubSpot app or a HubSpot MCP Auth App?
  3. Is Copilot Studio currently supported for HubSpot Remote MCP authentication?
  4. Is the “No actions available” result expected when using standard app credentials?
  5. Are there any additional scopes, discovery endpoints, or configuration steps required for Copilot Studio to discover HubSpot MCP tools?

Any working configuration examples would be greatly appreciated.

Thank you.

Hi @AAlva4,

Thank you for posting to the Community!
I’d like to tag in some of our Top Contributors to see if they have any ideas on this one. Hi @jpsanchez, @suprdense, and @keurcien, do you have any suggestions for @AAlva4?

Thank you in advance!

Cassie, Community Manager

I have been using the official MCP server with a custom MCP client for a few months, and it works great using HubSpot MCP Auth App. Looking at the things you’ve tried, it looks like the problem stands on Copilot’s side.

Have you tried running the modelcontextprotocol/inspector to test the MCP configuration?

I did a quick search, and I’m not sure Copilot Studio supports PKCE.

To confirm this hypothesis, use the MCP inspector and check if the authorization URL includes a code challenge or another MCP Client (like Claude Desktop).

Ran into this same problem. Copilot studio does not support pkce.. ugh. Microsoft recommends an API proxy to use MCP.. might as well just use the Rest API instead of MCP at this time.