Can AI agents automate Pleo?

Pleo is automatable today through its first-party hosted MCP and documented REST APIs. This record is Pleo business spend management (cards, bills, expenses, accounting export and import), including the vendor-hosted MCP at https://mcp.pleo.io/mcp. It is not SAP Concur, House of Control, or Ramp. The MCP uses Streamable HTTP and browser OAuth 2.0 with no client credentials to configure. Access is off by default until a company admin enables it per entity under Settings → General → Pleo AI. The English pricing table lists MCP only on Optimise, not Start or Build; MCP FAQs say it is included with eligible plans at no extra charge and still refer to a beta. Vendor docs describe expense search and retrieval, completing missing details (categories, tags, tax codes, notes, attendees, receipts), review and approval, and adding ready expenses to the export queue. They also state the agent inherits the connected user's Pleo permissions, cannot change company setup, and does not support wallet top-ups, reimbursement payouts, invoice payments, or other payment actions. Named MCP tool identifiers were not taken from a live catalog. REST APIs at https://external.pleo.io use JSON over GET, POST, PUT, and DELETE, with OpenAPI specs, staging at https://external.staging.pleo.io, and a 600-request-per-minute rate limit. OAuth 2.0 with Bearer access tokens is the recommended partner method; standalone and integrated API keys exist as restricted exceptions and authenticate with HTTP Basic using the key as username. Documented surfaces include Export jobs and items, Tags, Chart of Accounts, Tax Codes, Employees, Companies, Vendors, and Webhook Subscriptions. Export jobs can also be consumed as immutable JSON, and the platform overview documents ERP-specific CSV templates from the web app. Partner OAuth sits behind the Early Access Programme; standalone API keys are not self-service; new External APIs are not broadly enabled by default. Zapier, Make, Microsoft Power Automate, and n8n catalogs were not opened. No official general-purpose SDK or CLI was established. Computer-use viability is unassessed. API and MCP each score 7. MCP is the best path because it is the vendor agent interface once an Optimise tenant admin has enabled it.

Best path today: mcp · Overall automatability: 7/10