Copilot Studio

Configuring connection to Github MCP server

(0) Share

Report

Posted on by YK-20041934-0

Environment:

Copilot Studio / Power Platform
GitHub MCP Server (remote endpoint: https://api.githubcopilot.com/mcp/)
Authentication: Personal Access Token (PAT)

Problem:

When configuring the GitHub MCP server in Copilot Studio using a PAT, I receive the following error:
- Content-Type must be 'application/json'\n

Categories:

Model context protocol

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

Sunil Kumar Pashikanti 2,318 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @YK-20041934-0,

You can’t fix this with headers or a PAT.

Why it fails:

Copilot Studio calls MCP tools using a stateless HTTP POST and expects a single JSON response.
GitHub’s hosted MCP endpoint is designed for IDEs (VS Code, Cursor) and requires a stateful Server‑Sent Events (SSE) stream.

When Copilot Studio sends a one‑off POST, GitHub rejects the transport model, and the gateway surfaces a misleading
Content-Type must be 'application/json' error.

What works instead:

Add an adapter (bridge) e.g., an Azure Function that:

Accepts the stateless POST from Copilot Studio

Manages the SSE session with GitHub MCP

Flattens the stream into a single JSON response

Or skip MCP, use the native GitHub REST or GraphQL APIs (built‑in or custom connector), which are fully compatible with Copilot Studio.

In short: this is a transport mismatch (stateless REST vs stateful SSE), not a configuration issue.

References:
The Protocol Paradox: Why GitHub MCP Fails to Integrate with Copilot Studio

How to Fix the "Content-Type must be application/json" Error in Copilot Studio MCP

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.

Was this reply helpful? Yes No
Suggested answer

Ashlesha-MSFT Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!
Hi,

Adding to the explanation above — this is indeed a transport mismatch and not a configuration issue, so adjusting headers or the PAT won't resolve it.

Just to summarize the two recommended paths:

Azure Function bridge — if you specifically need GitHub MCP tools in Copilot Studio, this is the right approach. The function acts as a middleware that handles the SSE session with GitHub and returns a flat JSON response to Copilot Studio.

GitHub REST/GraphQL API via custom connector — if you don't strictly need MCP, this is the simpler and more stable option, and is natively compatible with Copilot Studio.

We'd recommend starting with the REST/GraphQL connector approach if your use case allows it, as it avoids the complexity of managing an SSE bridge layer.

Was this reply helpful? Yes No