Xledger MCP: connect Xledger to Claude and ChatGPT
Ask Claude or ChatGPT which customer invoices are overdue, which supplier invoices fall due this week or where a project stands. The answer comes straight from Xledger, without building a report first.
We build the connector for your company on Xledger’s own GraphQL API, with a token that reaches only the information types you choose. Admins decide which groups get it in Deployed OS, and it only reads.
Built for your company · Works in Claude, ChatGPT and Copilot
What your team can do with Xledger in Claude and ChatGPT
Receivables and payables in one answer
Where the project stands
The ledger across entities
The numbers behind the question
Ask it like this
“Which customer invoices are more than 30 days overdue in Xledger?”
“Which supplier invoices fall due in the next seven days, and from whom?”
“What have we invoiced Fjellstad Bygg AS this year?”
“What is the balance on account 1920 at the end of September?”
“Summarise the projects for Aker Marine Service and what has been invoiced on each.”
“Draft a friendly reminder to Lindvik Logistikk about invoice 70218. I will send it myself.”
What we build for Xledger
Deployed OS has no ready Xledger connector yet. We build it for your company when you start, on Xledger’s own API, with the same rules as every other connector: each person’s own login, access decided by group, every call logged.
- Customers and customer invoices
- Customers, and customer invoices with their amounts, due dates and what is still open.
- Suppliers and supplier invoices
- Suppliers, and supplier invoices with due dates and payment status.
- Projects
- Projects with their details and what has been invoiced on them.
- Ledger
- Account balances per entity and period.
Who sees what
- Read-only
- The connector reads. It does not post, approve invoices or change a customer or supplier.
- A token with only the areas you choose
- An Xledger administrator creates the API token and chooses which information types it may reach. It is a company token, not each person’s own Xledger login, so anything the token is not given stays out of reach.
- Your company decides who gets it
- Admins choose which groups get Xledger in Deployed OS. 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 Xledger connector in three steps
Xledger MCP: common questions
Not from Xledger, as far as we know in October 2026. There is an open-source, read-only server from a third party that a developer can run with an Xledger token. We build the connector on Xledger’s API so the whole company can use it in Claude and ChatGPT, with access per group and one log.
No. The connector reads customers, suppliers, invoices, projects and account balances. It does not post or approve anything, and we only add writing if you ask for it.
No. Xledger’s API uses a token your administrator creates for the company, limited to the information types you choose. Who can use it is decided per group in Deployed OS, and every call is logged with the name of the person who asked.
GraphQL API access and an API token. Your administrator creates the token under Access Control in Xledger, and if the GraphQL option is missing, Xledger’s support desk can turn it on.
Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. Xledger 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.