Add an existing Model Context Protocol (MCP) server to your agent

If you have an MCP server already set up, you must configure a custom connector (via Power Apps or Power Automate) for your MCP server to add the server to your agent.

If you have not yet set up an MCP server, see Create a new MCP server for information on how to get started.

Supported transports

In MCP, transports are the foundation for client-server communication. Transports handle the mechanics of sending and receiving messages. Currently, Copilot Studio supports the following transport types:

• Streamable - Recommended (generally available)
• Server-Sent Events (SSE) (public preview)

Create a custom MCP connector

To carry out this procedure, you need a schema file for your MCP server. The schema file is an OpenAPI specification YAML file that describes the API of your MCP server.

For guidance on what the specification file should look like, check out some of the provided MCP server schema examples.

1. Select Agents in the left navigation.

2. Select your agent from the list of agents.

3. Go to the Tools page for your agent.

4. Select Add a tool.

5. Select New tool.

6. Select Custom connector. You're taken to Power Apps to create a new custom connector.

7. Select New custom connector.

8. Select Import OpenAPI file.

9. Navigate to your schema file and select Import to import the file.

10. Select Continue to complete the setup in Power Apps. You can read more about the setup process in the Power Apps documentation at Import the OpenAPI definition.

MCP server schema examples

Here are two sample OpenAPI schema files for MCP servers using fictional data, in YAML format. The samples demonstrate each of the supported transports. You need to fill in the details for your own MCP server.

Here is an example YAML for Streamable (Recommended):

swagger: '2.0'
info:
  title: Contoso
  description: MCP Test Specification, YAML for streamable MCP support in Copilot Studio
  version: 1.0.0
host: contoso.com
basePath: /
schemes:
  - https
paths:
  /mcp:
    post:
      summary: Contoso Lead Management Server
      x-ms-agentic-protocol: mcp-streamable-1.0
      operationId: InvokeMCP
      responses:
        '200':
          description: Success

Here is an example YAML for SSE:

swagger: '2.0'
info:
  title: Contoso
  description: MCP Test Specification, YAML for SSE MCP support in Copilot Studio
  version: 1.0.0
host: contoso.com
basePath: /
schemes:
  - https
paths:
  /mcp/sse:
    get:
      summary: Contoso Lead Management Server
      x-ms-agentic-protocol: mcp-sse-1.0
      operationId: InvokeMCP
      responses:
        '200':
          description: Success