Start here
MCP for Copilot is a directory of 36,311 unique Model Context Protocol (MCP) servers from the official MCP Registry and Microsoft's certified MCP connector list. Each one gets a verdict on whether it's likely to connect to Microsoft Copilot Studio, based on what Copilot Studio's documentation says it supports. Data built 2026-10-21, refreshed nightly.
Verdicts are rule-based estimates, not tested in Copilot Studio. We send one read-only
initialize request to each listed remote endpoint and read public metadata. Always confirm with the vendor's docs. Independent project, not affiliated with Microsoft.How to read the three verdicts
| likely compatible 19,639 unique | A Microsoft-certified connector, or a remote Streamable HTTP endpoint with an auth mode the Copilot Studio wizard handles (none, API key header, or OAuth with Dynamic Client Registration). You should be able to add it with the MCP onboarding wizard. |
| needs work 15,994 unique | Could work, but you have to do something first: host it, register an OAuth app, fill in a tenant URL, or check why the endpoint didn't answer. |
| not compatible 678 unique | As listed, there's nothing Copilot Studio can connect to: an SSE-only endpoint, or no endpoint or package at all. |
What to do with “needs work” servers
- Local package only (stdio), 15,676 registry entries: Copilot Studio needs a server URL, so the package has to run somewhere reachable behind a Streamable HTTP endpoint first. See Streamable HTTP vs SSE vs stdio for the options.
- OAuth without Dynamic Client Registration, 247 entries: register your own app with the vendor's identity provider and use OAuth 2.0 → Manual (client ID, secret, authorization and token URLs), then add Copilot Studio's callback URL to the app.
- Credentials required, scheme undocumented, 253 entries: check the vendor's docs for an API key header or OAuth details.
- Per-tenant URL template, 269 entries: fill in your own tenant or workspace values in the URL.
- No valid MCP answer at the last check, 2,310 entries: the endpoint timed out or errored. It may be down or moved; check the project before relying on it.
For not compatible SSE-only servers (728 entries), the fix is on the server side: ask the maintainer for a Streamable HTTP endpoint.
Copilot Studio's own requirements
- Generative orchestration must be on. Microsoft Learn: “You must turn on generative orchestration to use MCP.” (Extend your agent with MCP)
- Tools and resources only. MCP servers can offer tools, resources and prompts; Learn says “Copilot Studio currently supports MCP tools and resources.” Prompts aren't in that list. (source)
- Streamable HTTP only. “Currently, Copilot Studio supports the Streamable transport type,” and it “no longer supports SSE for MCP after August 2025.” (Connect to an existing MCP server)
- Auth options in the onboarding wizard: None, API key (header or query), or OAuth 2.0 (Dynamic discovery, Dynamic, or Manual). (source)
Where to go next
- Search the directory: filter by verdict, auth type, or Microsoft-certified.
- Methodology: every rule (R1 to R5) and what we actually checked.
- How the numbers add up: from 47,517 registry entries to 36,311 unique servers.
- Streamable HTTP vs SSE vs stdio: which transports Copilot Studio accepts and what to do with local-only servers.
- Newsletter: a short weekly email on new Copilot-ready servers, breakages and auth changes.