MCP connectorsSpendesk

Spendesk MCP: connect Spendesk to Claude and ChatGPT

Ask Claude or ChatGPT what each cost centre spent last month, which supplier invoices are still missing a receipt or what is left to book before the monthly close. The answer comes straight from Spendesk, without an export to Excel first.

We build the connector for your company on Spendesk’s own API, next to your accounting system, CRM and other tools. It only reads, and your admins decide which groups get it.

Built for your company · Works in Claude, ChatGPT and Copilot

In practice

What your team can do with Spendesk in Claude and ChatGPT

Finance director

Spend by cost centre before the committee

Card payments, supplier invoices and expense claims, summarised by cost centre, expense category or supplier the way you ask, ready for the monthly review with the management team.

Accounting

What is left before the close

Payables with their bookkeeping status and attachments, so you can see what is ready for the accounts, what is missing a receipt and what has already been exported.

Budget owners

Your department’s spend in one answer

What your cost centre has spent this month and with which suppliers, without waiting for finance to send a report.

Purchasing

Know your suppliers

How much you spend with a supplier, how often and from which teams, read from Spendesk when you ask.

Examples

Ask it like this

“What did the Marketing cost centre spend in September, by supplier?”
“Which payables from October are still missing a receipt?”
“Summarise everything we paid to Imprimerie Lambert this year.”
“Which expense claims from Camille Rousseau have not been exported to accounting yet?”
“Compare software subscription spend this quarter with the same quarter last year.”
“Which suppliers did the Lyon office pay by card for the first time this month?”

The connector

What we build for Spendesk

Deployed OS has no ready Spendesk connector yet. We build it for your company when you start, on Spendesk’s own API, with the same rules as every other connector: each person’s own login, access decided by group, every call logged.

Payables: Card payments, supplier invoices and expense claims as Spendesk records them, with amounts, dates, attachments and bookkeeping status.
Settlements: How and when payables were settled, so the AI can say what has actually been paid.
Suppliers: Your suppliers in Spendesk, so spend can be grouped and compared by supplier.
Cost centres and categories: Cost centres, expense categories and your analytical fields, so spend is grouped the way your company already reports it.
Users: The people in Spendesk, so the AI can tell you whose spend it is.

Security

Who sees what

Read-only: The connector reads. It does not approve a request, pay an invoice, change a payable or touch your cards.
Access per group, not per Spendesk login: For a company’s own integration, Spendesk’s API uses credentials your Account Owner creates, with the read scopes you choose. So people do not sign in with their own Spendesk login; Deployed OS decides who may use it.
Your company decides who gets it: Admins choose which groups get Spendesk in Deployed OS, for example finance and budget owners 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.

Setup

Set up the Spendesk connector in three steps

We go through which questions matter most with you and build the connector on Spendesk’s API.

Your Spendesk Account Owner creates API credentials under Settings, Integrations, API access management, with read scopes only, and you choose which groups get Spendesk in Deployed OS.

The people in those groups use Spendesk through Deployed OS in Claude or ChatGPT. From then on they just ask.

Compared

Spendesk’s own MCP server or Deployed OS?

Spendesk has its own MCP server, which Spendesk describes as a beta. An Account Owner or Admin creates the connection in Spendesk for Claude, ChatGPT or Dust, it reads by default, and write tools are a separate beta step that an admin has to turn on. Only Account Owners and Controllers can use it, so it fits a finance team asking about its own Spendesk data.

Deployed OS is for when more people, and more systems, are involved. We can build on Spendesk’s API for the budget owners and managers the official server does not cover, add company-specific questions such as spend against your own budget lines, and put Spendesk next to your accounting system and CRM 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.

Their documentation: Spendesk’s MCP server

Questions

Spendesk MCP: common questions

Yes. Spendesk has its own MCP server, described as a beta, set up by an Account Owner or Admin for Claude, ChatGPT or Dust. It reads by default and only Account Owners and Controllers can use it. Deployed OS can sit alongside it and open Spendesk to other groups, with access per group and one log.

No. The connector we build reads payables, settlements, suppliers, cost centres and users. It does not approve, pay or edit anything. If your company wants a write action, we build it only when you ask for it.

No. A company’s own integration with Spendesk’s API uses credentials your Account Owner creates, limited to the read scopes you choose. Who may use it is decided per group in Deployed OS, and every call is logged.

Spendesk’s API is available on the Premium and Enterprise plans, and Spendesk switches API access on for your account before your Account Owner can create credentials.

Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. Spendesk 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.

More connectorsAll connectors

Let’s talk

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.