Pleo MCP: connect Pleo to Claude and ChatGPT
Ask Claude or ChatGPT what you spent on software last quarter, which expenses are tagged to a project or what is still waiting to go to accounting. The answer comes straight from Pleo, without an export to a spreadsheet first.
We build the connector for your company on Pleo’s own API, next to your other systems. It only reads, and your admins decide which groups get it.
Built for your company · Works in Claude, ChatGPT and Copilot
What your team can do with Pleo in Claude and ChatGPT
Spend by category, tag or person
What is left before the close
Your team’s spend in one answer
The numbers next to the plan
Ask it like this
“What did we spend on software subscriptions last quarter, by tag?”
“Summarise all expenses tagged to Project Nordlys this year, by category.”
“Which expenses from October have not been exported to accounting yet?”
“Which of the people on Karin Lindqvist’s team made the most company card purchases in September?”
“Which out-of-pocket claims from Johan Berg are not yet exported to accounting?”
“Compare travel spend this autumn with last autumn, by person.”
What we build for Pleo
Deployed OS has no ready Pleo connector yet. We build it for your company when you start, on Pleo’s own API, with the same rules as every other connector: each person’s own login, access decided by group, every call logged.
- Expenses and accounting entries
- Card purchases, out-of-pocket claims, mileage and other expense types, as Pleo hands them to accounting through its export API.
- Export status
- Which expenses have gone to your accounting system and which are still waiting, so the AI can say what is left before the close.
- Tags
- Your tags, the cost allocations such as projects or cost centres, so spend can be grouped the way your company does it.
- Employees
- The people in Pleo, so the AI can tell you whose spend it is.
Who sees what
- Read-only
- The connector reads. It does not change an expense, approve anything, move money or touch your cards.
- Access per group, not per Pleo login
- For a company’s own integration, Pleo’s API uses a key your Pleo admin creates, with the entities and read scopes you choose. So people do not sign in with their own Pleo login; Deployed OS decides who may use it.
- Your company decides who gets it
- Admins choose which groups get Pleo in Deployed OS, for example finance only. A group without access never sees the connector.
- Every call logged
- Who asked, what was read and when. Deployed OS keeps the log, and it can be exported.
Set up the Pleo connector in three steps
Pleo’s own MCP server or Deployed OS?
Pleo has its own MCP server, which Pleo describes as a beta. A Pleo admin turns it on per entity, everyone signs in with their own Pleo login, and the AI works within that person’s Pleo permissions. It searches expenses and can read and change fields on a single expense, such as category, tags, notes and receipts, but not company setup. If the job is handling your own expenses from Claude or ChatGPT, it is a good fit.
Deployed OS is for when Pleo is one system among several. It sits next to your accounting system, CRM and other tools in one company connection, admins decide which groups get each system, every call is logged in one place, and the same rules apply in Claude and ChatGPT, next to your company’s skills and guardrails.
Pleo MCP: common questions
Yes. Pleo has its own MCP server, described as a beta, that a Pleo admin turns on. Each person signs in with their own Pleo login and it works within their Pleo permissions. Deployed OS adds Pleo to one company connection with your other systems, with access per group and one log.
No. The connector we build reads expenses, export status, tags and employees. It does not edit expenses, approve anything or touch cards.
No. A company’s own integration with Pleo’s API uses a key your Pleo admin creates, limited to read scopes and the entities you choose. Who may use it is decided per group in Deployed OS, and every call is logged.
Yes. When your Pleo admin creates the API key, they choose which entities it covers. The connector sees nothing outside them.
Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. Pleo data is fetched when someone asks for it.
It depends on the size of your team. Get in touch and we will walk you through it.
See it on your own tools.
Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.