Skip to main content
This page is for Copilot Studio makers adding Pleo as an MCP tool to an agent, not every individual Copilot user. If you use a Copilot agent that a maker has already connected to Pleo, you don’t need to do anything here beyond the first-time Pleo sign-in prompt.

​
Prerequisites

Before you begin:
  • Pleo MCP access is off by default; a company admin must enable it for your organisation before you can connect, and controls which people have access. See Access & Permissions if you’re not sure whether it’s enabled.
  • If your Microsoft 365 tenant blocks custom MCP servers by default, your tenant admin has approved Pleo. See How to Add Pleo MCP as a Custom Connector in Microsoft Copilot if Pleo doesn’t connect.

​
Steps

Follow the steps below to connect Pleo to a Copilot Studio agent.
  1. Open your agent in Copilot Studio and go to Tools → Add a tool → New tool → Model Context Protocol.
  2. Enter a server name (for example, “Pleo”) and the server URL:
  1. Under Authentication, choose OAuth 2.0 and select Dynamic discovery. If your agent doesn’t support dynamic discovery, choose Manual and contact Pleo for the OAuth endpoint details (Authorization URL, Token URL, Client ID, and Client Secret).
  2. Click Create a new connection, then Add to agent.
  3. Log in to Pleo if needed, then approve access.
  4. In the agent’s tool list, toggle on the specific Pleo tools you want the agent to use.
Pleo is now available as a tool for this agent. See Microsoft’s documentation: Connect your agent to an existing MCP server