> ## Documentation Index
> Fetch the complete documentation index at: https://www.integrate.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# ETL: Connect Microsoft Copilot to MCP

> Connect a Microsoft Copilot Studio agent to the Integrate.io ETL MCP server with OAuth, then publish it to Microsoft 365 Copilot and Teams.

Microsoft Copilot reaches MCP servers through agents built in [Microsoft Copilot Studio](https://learn.microsoft.com/microsoft-copilot-studio/mcp-add-existing-server-to-agent). You add the Integrate.io endpoint to an agent as an MCP tool, sign in with OAuth, and then publish the agent to Microsoft 365 Copilot and Teams. There is no token to paste and no bridge to install. For OAuth detail, see [Authentication](https://www.integrate.io/docs/etl/mcp-authentication.md).

The endpoint is:

`https://api.xplenty.com/api/mcp`

This is the global URL. With OAuth you choose the account when you sign in; with a Personal Access Token, the account the token was created in is used. To connect several accounts at the same time, add one server per account with the per-account URL `https://api.xplenty.com/YOUR_ACCOUNT_ID/api/mcp` instead. See [Connect a client](https://www.integrate.io/docs/etl/mcp-connect.md).

> [!NOTE]
>
> This page covers Copilot Studio agents, which is how MCP tools reach Microsoft 365 Copilot and Teams. GitHub Copilot is a separate product: in VS Code it reads remote servers from `mcp.json` the same way [Cursor](https://www.integrate.io/docs/etl/mcp-connect-cursor.md) does. See [Other clients](https://www.integrate.io/docs/etl/mcp-connect-other.md) for the generic setup.

## Before you start

* You need access to Copilot Studio and permission to create agents in your Power Platform environment.
* If your organization has a Power Platform data policy that governs connectors, it also governs MCP tools. Ask your Power Platform admin to allow the connector if the tool is blocked.
* Copilot Studio connects from Microsoft's cloud, so the endpoint must be reachable over the public internet (the production URL is). If your account sits behind a firewall or IP whitelist, make sure Microsoft's egress can reach `api.xplenty.com`.

## Add the MCP server to an agent

**1. Open the MCP wizard**

In Copilot Studio, open your agent (or create one) and go to the **Tools** page. Select **Add a tool**, then **New tool**, then **Model Context Protocol**.

**2. Enter the server details**

| Field | Value |
| :- | :- |
| **Server name** | `Integrate.io` |
| **Server description** | A sentence the agent uses to decide when to call the server, for example: "Read and manage Integrate.io ETL packages, connections, jobs, clusters, and schedules." |
| **Server URL** | `https://api.xplenty.com/api/mcp` |

**3. Choose OAuth 2.0 with Dynamic discovery**

For authentication, select **OAuth 2.0**, then set **Type** to **Dynamic discovery**. Copilot Studio finds the Integrate.io OAuth endpoints and registers itself, so there is no client ID, client secret, or authorization URL to enter. Select **Create**, then **Next**.

**4. Create the connection and authorize**

In the **Add tool** dialog, select **Create a new connection**. Copilot Studio opens the Integrate.io consent screen. Sign in if you aren't already, check that the return host is a Microsoft host, then click **Authorize**.

**5. Add the tool to the agent**

Select **Add to agent**. The Integrate.io tools now appear on the agent's **Tools** page.

The connection appears in **Settings → Developer Settings → Connected Applications** in your Integrate.io dashboard, where you can audit or revoke it.

## Verify

In the Copilot Studio test pane, ask a read-only prompt, for example: "List the workspaces in my Integrate.io account." The first call may ask you to confirm the connection. If you see your workspaces, the connection works.

## Make the agent available in Microsoft 365 Copilot and Teams

1. **Publish** the agent in Copilot Studio.
2. Go to **Channels** and select **Teams and Microsoft 365 Copilot**.
3. Leave the Microsoft 365 Copilot option selected and select **Add channel**.
4. Select **See agent in Teams** and add it. The agent is now installed for you in Teams and Microsoft 365 Copilot.

To make the agent available to others in your organization, submit it for admin approval through the same channel. For the current steps, see Microsoft's [publishing guide](https://learn.microsoft.com/microsoft-copilot-studio/publication-fundamentals-publish-channels).

## Sharing the agent

Integrate.io access is account-wide with the permissions of whoever signed in, and write tools can change live pipelines (see [Safety and audit](https://www.integrate.io/docs/etl/integrateio-mcp-server.md#safety-and-audit)). Before you share the agent, open the Integrate.io tool's settings in Copilot Studio and check **Credentials to use**:

| Setting | What happens |
| :- | :- |
| **End user credentials** (recommended) | Each person who uses the agent signs in to Integrate.io with their own login and gets only their own access. |
| **Maker-provided credentials** | Everyone who uses the agent acts with your Integrate.io access. Avoid this unless every user should have that access. |

## FAQ

**Which OAuth type should I pick?**

**Dynamic discovery**. The Integrate.io MCP server publishes its OAuth metadata and supports dynamic client registration, so Copilot Studio configures itself. **Dynamic** and **Manual** are for servers that lack one or both of those.

**Can I use a Personal Access Token instead of OAuth?**

Use OAuth. With the **API key** option, every person using the agent has to supply a token themselves, and a Personal Access Token has a 10-year default lifetime, so a token pasted into a shared agent is hard to keep track of. OAuth tokens are short-lived and each sign-in shows up in **Connected Applications**.

**Does Copilot Studio support the SSE transport?**

No. Copilot Studio supports only Streamable HTTP, which is what the Integrate.io endpoint uses.

**The tool asks me to connect again in every chat.**

Check that the connection in Copilot Studio still exists and that it wasn't revoked in **Connected Applications**. If it was revoked, remove the connection and create a new one. See [Troubleshooting](https://www.integrate.io/docs/etl/mcp-troubleshooting.md) for other errors.

## Related

> [card] [Connect a Client to MCP](https://www.integrate.io/docs/etl/mcp-connect.md)

> [card] [MCP Authentication](https://www.integrate.io/docs/etl/mcp-authentication.md)

> [card] [MCP Troubleshooting](https://www.integrate.io/docs/etl/mcp-troubleshooting.md)

> [card] [Integrate.io MCP Server](https://www.integrate.io/docs/etl/integrateio-mcp-server.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.