Invoking MCP server through Copilot Studio throws a 404 after invocation

Open
#36 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure
Domain
api, cloud

Research direction

Start by reviewing the APIM-exposed MCP server endpoint and the custom connector invocation in Power Automate. Compare the successful invocation with the 404 shown in Power Automate and Copilot Studio, using the attached screenshots as context. Done means the MCP response is displayed in Copilot Studio without a 404 Resource not found error.

Written by the indexing model from the issue text.

Description

We have an MCP server endpoint exposed on APIM and we created a custom connector in power automate and trying to invoke the same in copilot studio. We see that it is invoked successfully but a 404 Resource not found error is thrown before the response is displayed.

Please find the screenshots below for reference.

Image Image

Invoking from power automate test tab shows the below error

Image

Please advise whats missing.

Dominant language
No language data
Stars
28
Forks
77
Avg merge
7d 12h
Merged PRs (30d)
7

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Azure/MCP

All issues in Azure/MCP

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.