What MCP gives a Copilot Studio agent
The Model Context Protocol (MCP) is an open standard for offering tools and data to AI models. A server describes its tools once, and any client that speaks MCP can use them: Claude, ChatGPT, Cursor, and also Copilot Studio. Instead of building a custom connector per action, you point the agent at the server and it gets every tool that server offers, with their descriptions. When the server adds a tool, the agent sees it too.
Option 1: the MCP onboarding wizard
This is the fastest route (documentation as of November 2026):
- Open the agent and go to Tools > Add a tool > New tool > Model Context Protocol.
- Fill in Server name, Server description and Server URL. The description matters: the agent uses it to decide when to call the server.
- Choose authentication:
| Option | When to use |
|---|---|
| None | Public or test servers |
| API key | Key sent in a header or query parameter |
| OAuth 2.0, dynamic discovery or dynamic | The server handles client registration itself; fewer fields to fill in |
| OAuth 2.0, manual | You enter client ID, secret, authorization URL, token URL, refresh URL and scopes, and register the callback URL Copilot Studio shows you |
- Select Create, then Create a new connection, then Add to agent.
Option 2: a custom connector
If you want to manage the server like any other Power Platform connector, create a custom connector in Power Apps from an OpenAPI definition in YAML that carries x-ms-agentic-protocol: mcp-streamable-1.0. The connector then shows up under tools in Copilot Studio.
A third route exists for organizations using Agent 365: register the server with the Agent 365 CLI. An admin approves it in the Microsoft 365 admin center, and it can take up to 30 minutes before it appears.
The common mistake: an SSE server
Many MCP servers written in 2024 and early 2025 used Server-Sent Events (SSE). Copilot Studio supports only the Streamable HTTP transport, and SSE has not been supported since August 2025. If the connection fails with a server that works fine in another client, check the transport first.
Governance
MCP servers in Copilot Studio fall under the same data policies as connectors, so an admin can allow or block them per environment in the Power Platform admin center. The governance overview also lists maker audit logs in Microsoft Purview and real-time risk assessment of agents. Treat an MCP server as what it is: a door into a system, used under the identity you chose in the authentication step. More on the admin side is in How do you govern Copilot Studio agents as an admin?.
What this means for a team
MCP turns Copilot Studio from a Microsoft-only builder into a client of the same tool ecosystem your developers use in Claude Code or Cursor. A team that already runs an MCP server for its CRM or ticketing system can offer it to Copilot agents without rebuilding it. Two points to settle first:
- Who owns the server and its credentials, since every agent that connects acts through it.
- Whether the server is reachable from Microsoft’s cloud: Copilot Studio calls it over the internet by URL.
What the agent can do comes from the tools. What it knows about your team still comes from its instructions and knowledge, see What are Copilot agents?.
Where Bombos fits
Because Copilot Studio speaks MCP, a memory that is offered over MCP can reach Copilot agents too. Bombos is a plugin that gives Copilot, your Studio agents and the other AI tools your team uses (Claude, Claude Code, ChatGPT, Codex, Cursor, your own agents) one shared memory: team knowledge, learned rules, mail, documents and repos, traceable, in the cloud or on your own server. One person can try it first with their own agents.
Related questions
Does Copilot Studio support SSE MCP servers?
No. Microsoft's documentation says only the Streamable transport is supported and SSE has not been supported since August 2025. A server that only speaks SSE needs an update or a proxy.
Which harnesses can use MCP servers?
The setup guide describes the standard harness, and Microsoft's harness overview lists tools including MCP for the Microsoft Copilot harness and the Customer Conversation harness as well.
Can an admin block an MCP server?
Yes. MCP servers are added as connectors, so the data policies an admin sets on connectors in the Power Platform admin center govern them too.
Why doesn't my MCP server show up after registering it through Agent 365?
Registration via the Agent 365 CLI needs admin approval in the Microsoft 365 admin center, and Microsoft notes it can take up to 30 minutes to appear.
