How to Add Pleo MCP as a Custom Connector in Claude

This page is for Claude for Work Owners and Primary Owners (or members with the Identity & Access custom role). If you’re an individual Claude Free, Pro, or Max user, you can add Pleo yourself. See How to Install the Pleo MCP in Claude.

Steps

Follow the steps below in the Claude Admin Console to add Pleo as a custom connector for your organisation.

Go to Organization Settings → Connectors.
Click Add, then choose Custom → Web.
Enter the Pleo MCP server URL:

https://mcp.pleo.io/mcp

No Advanced or Auth settings are needed.

Property	Value
MCP URL	`https://mcp.pleo.io/mcp`
Transport	Streamable HTTP
Authentication	OAuth 2.0 (no credentials to configure)

Add the connector. It becomes available to everyone in your organisation.
Set Tool permissions for Pleo’s tools: Always allow, Needs approval, or Blocked. Pleo recommends requiring approval for any tool that writes data.

Pleo is now available as a connector for your organisation. See Anthropic’s documentation: Add a custom connector

Allow network access for receipt uploads

Claude Code runs shell commands in a sandbox that allows no network domains by default. When Pleo attaches a receipt file, it issues a short-lived upload URL on mcp.pleo.io and the agent uploads the file to it directly. If the domain isn’t allowed, that upload is blocked. This applies to Claude Code. Claude Web, Claude Desktop, and Cowork don’t restrict network access this way. Add mcp.pleo.io to the sandbox’s allowed domains:

{
  "sandbox": {
    "enabled": true,
    "network": {
      "allowedDomains": ["mcp.pleo.io"]
    }
  }
}

Keep any domains you already allow and add this one to the list, rather than replacing it. If the sandbox is already on, only the network block is new. This setting covers the commands the agent runs, which is what the receipt upload uses. Claude Code’s connection to the Pleo MCP is made by the app itself and doesn’t depend on it. *.pleo.io works if you prefer a broader rule, though mcp.pleo.io is all the upload needs.

Scope	Where the setting goes
One developer, all their projects	`~/.claude/settings.json`
Everyone in the organisation	Managed settings, delivered by your MDM or through server-managed settings on claude.ai

Without any of this, Claude Code asks for approval the first time a command needs a new domain, and the developer can allow mcp.pleo.io from that prompt. If your organisation locks the allowlist down with allowManagedDomainsOnly or strictAllowlist, no prompt appears and an unlisted domain fails outright, so the entry above becomes mandatory. See Anthropic’s documentation: Configure the sandboxed Bash tool

Other sandboxed clients

What Comes Next?

How to Install the Pleo MCP in Claude

Anthropic’s documentation: Add a custom connector
Anthropic’s documentation: Configure the sandboxed Bash tool
FAQs
Access & Permissions

Get Started

How-to's

How to Add Pleo MCP as a Custom Connector in Claude

Steps

Allow network access for receipt uploads

Other sandboxed clients

What Comes Next?

​Steps

​Allow network access for receipt uploads

​Other sandboxed clients

​What Comes Next?

​Related Reading

Steps

Allow network access for receipt uploads

Other sandboxed clients

What Comes Next?

Related Reading