Fortnox MCP: connect Fortnox to Claude and ChatGPT
Ask Claude or ChatGPT which customers haven’t paid, what a customer was invoiced last quarter or which supplier invoices fall due this week. The answer comes straight from Fortnox. No exports, no copy-paste.
With Deployed OS everyone at the company connects with their own Fortnox login. The AI sees exactly what that person sees in Fortnox, and nothing is ever booked or sent.
5 read actions · read-only · Works in Claude, ChatGPT and Copilot
What your team can do with Fortnox in Claude and ChatGPT
Chase what’s overdue
Know the customer before the call
Cash flow at a glance
Supplier invoices under control
Ask it like this
“Which customers have overdue invoices right now, and how much is it in total?”
“Show everything we’ve invoiced Acme AB since January, with the rows on the largest invoice.”
“Which supplier invoices fall due in the next 14 days?”
“List the customer invoices from last month that haven’t been booked.”
“What are the payment terms and org number for customer 1043?”
“Summarise this quarter’s invoicing per customer, top ten.”
What the Fortnox MCP connector does today
- Reads
fortnox_search_customersSearch customers by name: customer number, email, phone, org number, city and whether they are active.
- Reads
fortnox_get_customerRead one customer: contact details, org and VAT numbers, address, currency and payment terms.
- Reads
fortnox_list_invoicesList customer invoices by status (unpaid, overdue, unbooked, paid, cancelled), customer and date.
- Reads
fortnox_get_invoiceRead one invoice with its rows, totals, balance, references and remarks.
- Reads
fortnox_list_supplier_invoicesList supplier invoices by status and date, with totals and balance.
Need it to do more? We extend connectors for the companies that use them.
Who sees what
- Read-only
- The connector reads customers, customer invoices and supplier invoices. It cannot create, book or send anything in Fortnox.
- Each person’s own rights
- Everyone connects their own Fortnox user, so the AI sees what that user sees. Someone without access to supplier invoices in Fortnox gets none through the AI either.
- You choose who gets it
- Admins decide which groups at the company can use the Fortnox connector at all. Everyone else never sees it.
- Every call logged
- Who asked, which connector, when. Deployed OS shows reads per connector and per person, and the log can be exported.
Set up the Fortnox connector in three steps
Fortnox MCP: common questions
Not from Fortnox itself, as of October 2026. There are open-source servers a developer can run for one person. Deployed OS gives the whole company the same connection, with each person’s own login, access per group and a log of every call.
No. The connector only reads. Nothing is created, booked or sent. If you want it to do more, for example draft invoices, we can extend it for you.
Yes. Deployed OS is your company’s own MCP, so the same Fortnox connection works in Claude, ChatGPT and Copilot. People keep the assistant they prefer.
Yes. Your company needs access to the Fortnox Developer Portal to create the integration, and you can apply there if you don’t have it. We walk you through the steps.
Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. Fortnox 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.
