Skip to main content
Enablement is the organisation-level step that allows members to add the Pleo MCP in their AI platform. Whether you need it depends on your plan: individual plans (such as Claude Pro or ChatGPT Plus) usually need no admin action, while managed workspaces and tenants often restrict custom connectors until an admin allows them.

​
Prerequisites

​
Find Your Enablement Guide

These guides walk an admin through enabling the Pleo MCP at the organisation level, so individual members can then connect it themselves. Select your AI platform below for the relevant enablement steps.

Claude

Add Pleo as an organisation-wide custom connector in Claude for Work.

Codex

Where org-level control lives for Codex, which has no admin console of its own.

ChatGPT

Enable custom connectors for a ChatGPT Business, Enterprise, or Edu workspace.

Gemini Enterprise

Register Pleo as a Custom MCP Server in Google Cloud.

Microsoft Copilot

Approve Pleo as an allowed MCP server for Copilot Studio agents.

​
Allow Network Access for Receipt Uploads

When the agent attaches a receipt file, Pleo issues a short-lived upload URL on mcp.pleo.io and the agent uploads the file to it with an HTTP PUT from a command it runs. Some AI clients restrict the network access of those commands, and then the upload is blocked. The client’s connection to the Pleo MCP itself isn’t affected. Check whether your client restricts it, and allow mcp.pleo.io where it does: For any other client that sandboxes commands or routes them through a proxy, allow mcp.pleo.io in that client’s network settings, or at your firewall or proxy if the control lives there. mcp.pleo.io is the only domain the upload needs.

​
What Comes Next?