LABSCO SUMMARY
Read their data-processing note before connecting: colleague names on expenses go to your AI provider.
Pleo say it plainly, which is more than most do — expense data including the names of colleagues on those expenses is processed by whichever AI provider you connect, under that provider's terms, possibly outside the UK and EU. That is a finance-team decision, not an individual one, which is presumably why the switch is an admin toggle per entity rather than a user setting. The permission inheritance is the right model; the disclosure is the thing to actually read.
What it is
Pleo's hosted endpoint over their company card and expense platform. Included with eligible Pleo plans at no extra charge, though the docs do not name which plans qualify.
What you get
Read and write access to the spend data the connecting user can already see — the agent inherits that user's permissions and nothing more. It cannot alter company setup or configuration.
Requirements
- An admin has to enable it first: Settings, General, Pleo AI, MCP access — per entity, and off until they do
- OAuth 2.0 with PKCE and dynamic client registration for the connection itself
- A user can revoke their own connection under My Account, Security and Devices, MCP Connections
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Asking about company spend
Scoped to what the connecting user can already see.
02
Deciding whether to enable it
An admin toggle per entity, with the data-processing note as the thing to weigh.
03
Cutting a connection
Revoke from your own account, or the admin switch for everyone.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- OAuth 2.0 with PKCE and dynamic client registration
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.pleo.io/mcpRequirements
- OAuth 2.0 with PKCE and dynamic client registration