Cannot get MPC server working under any circumstances

(4) Share

Report

Posted on by NH-05051841-0

I've followed the MCP implementation lab from the Microsoft documentation and have created a jokes MCP server that provides various joke tools (Chuck Norris jokes, dad jokes, etc.). My implementation is correctly deployed to Azure and works as expected in testing, but fails in Copilot Studio. Lab link: https://github.com/microsoft/mcsmcp

What's Working:

Successfully deployed the MCP server to Azure

SSE endpoint correctly returns session IDs

Successfully tested with Postman (using proper JSON-RPC format)

Successfully tested with the MCP Inspector tool - all tools are discoverable and executable

The Issue:

When trying to use the MCP connector in Copilot Studio, I consistently get:

Sorry, something went wrong. Error code: SystemError. Conversation ID: [ID]. Time (UTC): [timestamp].

Example: Sorry, something went wrong. Error code: SystemError. Conversation ID: 5887e02d-ff3a-44ff-9abb-7be335ffe58b. Time (UTC): 5/5/2025 7:10:56 PM.

Technical Details:

Using TypeScript with Express

Deployed to Azure App Service

YAML configuration includes the required "Agentic" and "McpSse" tags

Server is accessible and functioning correctly when tested directly

Tools are properly registered and work through the MCP Inspector

Question:

Has anyone successfully implemented an MCP server that works with Copilot Studio? Are there any specific requirements or workarounds needed beyond what's in the documentation?

Any guidance would be greatly appreciated!

Categories:

Model context protocol

I have the same question (0)

All responses (4)

Answers (0)

Sort by

Suggested answer

zankard Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi @NH-05051841-0 -

Please ensure your endpoint returned in the open SSE connection call is a fully qualified URL.

For example:

By default, most standard SDK configurations return something like this:
event: endpoint
data: /message

But, Copilot Studio requires a fully qualified URI:
event: endpoint
data: https://microsoft.com/mcp/message [microsoft.com]

Let us know if this resolves your issue!

Was this reply helpful? Yes No
AD-05061823-0 2 on at

Like (0)

Report
Copy link

Link copied!

I have the same issue at the moment.

Was this reply helpful? Yes No
Suggested answer

Romain The Low-Code... 2,564 Super User 2026 Season 1 on at

Like (0)

Report
Copy link

Link copied!

hey ;) i did the lab last morning and add same error : how i solve.

First before try copilot studio : Try the part in visual studio code. i discovered that i had the same error in visual studio code agent BUT the good point is it have debug mod and trace !

My error : link was not public "realy" public and anonymous.

Then i add another error : I made a mistake and made the copilot studio part in a normal environnement. I restard in a preview env and everything was great and ok.

If you have problem with the deploy to azure, to use the forward port mode in visual studio : since the lab is not intented to work all day, the forward port in vs code is enough :) (and click public :!)

If this answer solved or helped you to solve please click answer it's important :)

Was this reply helpful? Yes No
dezrrm 26 on at

Like (0)

Report
Copy link

Link copied!

Also cannot get an MCP connection working. I have the lab deployed to Azure, and it works in MCP inspector. I have the connector, adding to the copilot, it says there is an error loading Tools.

Was this reply helpful? Yes No