Fortnox MCP connector
The Fortnox connector lets Claude, ChatGPT, Cursor and the Elaichi Agent look up customers, articles, suppliers and invoices in Fortnox and raise new invoices, each person working inside their own Fortnox access.
-
How it connects. Connects over OAuth. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
16 tools
How to connect
How to connect Fortnox to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Fortnox once
-
Open Connections, choose Add connection, and pick Fortnox.
-
Optionally set Share with to give a team access, then press Connect.
-
Supply your own Fortnox app, then approve. Fortnox needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Fortnox MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Fortnox MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Fortnox MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Fortnox to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Fortnox through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Finance
Raise the invoice straight after the job
Ask for a new invoice against an existing Fortnox customer with the right articles on it, and it is created in Fortnox ready for review.
-
Sales
Check whether a customer is already set up
Before quoting, ask whether a company already exists as a Fortnox customer and what price an article carries, and create the customer if it is missing.
-
Accounts receivable
Find every open invoice for one customer
Pull up the invoices for a customer, see which are unpaid and when they were due, and get a plain summary before you chase.
-
Purchasing
Look up a supplier before you order
Ask for a supplier's details from Fortnox, organization number, terms and address, without opening the accounting system.
-
Customer service
Catch the customer record up after a call
When a customer gives a new invoice address or contact, ask for the Fortnox customer to be updated and it is done while you are still on the line.
-
Leadership
Get a plain-language view of invoicing
Ask what was invoiced this month, to whom and for how much, and get an answer built from live Fortnox invoices rather than an exported sheet.
Try asking
- “Show me all unpaid invoices for Nordic Byggteknik AB”
- “Create an invoice for Lundgren Konsult with two hours of consulting”
- “Which suppliers do we have in Gothenburg?”
Compare
Elaichi vs Zapier MCP vs Composio for Fortnox
All three can connect Fortnox to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Fortnox tools | Allow or restrict single Fortnox tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Fortnox call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Fortnox tools for your AI agents
16 tools are ready to call through Elaichi's MCP endpoint the moment you connect Fortnox, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Fortnox gets you
6 screens from the product, each doing one job for your Fortnox account.
The agent
Ask about invoices and customers in plain language.
Answers come from live Fortnox records, not a spreadsheet someone exported last week.
- customers
- invoices
- articles
- suppliers
Ask Elaichi to work across your apps.
Show me all unpaid invoices for Nordic Byggteknik AB
Create an invoice for Lundgren Konsult with two hours of consulting
Which suppliers do we have in Gothenburg?
Also runs in Claude, ChatGPT or Cursor
MCP clients
One endpoint puts Fortnox in every client.
Claude, ChatGPT and Cursor sign in over OAuth, with no SDK and no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
16 Fortnox tools, ready without writing code.
Customers, articles, suppliers, invoices and company information, cataloged and callable from day one.
- List all Fortnox companyinformation
- List all Fortnox me
- Get single Fortnox customer by ID
- List all Fortnox customers
ElaichiToolsToolboxes
Every team gets its own Fortnox toolbox.
Finance raises invoices, sales looks up customers, each team scoped to what it needs.
- Finance
- Sales
- Accounts receivable
- Purchasing
ElaichiToolboxesShared connections
Teammates work through Fortnox, never touching a credential.
One person connects the Fortnox account and shares it with teams and members.
- Finance
- Sales Nordics
- Accounts receivable
- Purchasing
ElaichiConnectionsAudit log
Every Fortnox call answers who did what.
When, who, what happened, and which invoice or customer, in an append-only log.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule turns Fortnox invoices into a digest.
Invoices are fetched, grouped, drafted into a summary, approved by a person, then posted back.
Fortnox digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch customers
Fortnox
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Fortnox
Queued
Collections and dashboards
Fortnox invoicing health, refreshed on a schedule.
Four metrics, 14 days of invoices created, and a split by team, computed without a model.
Fortnox health
Refreshed 4 minutes ago · every 15 minutes · from the customers collection
Customers
1,284 ↓ 12%
Invoices
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Customers created
Last 14 days
By team
Share of activity
Finance 34%
Sales Nordics 27%
Accounts receivable 21%
Purchasing 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Fortnox to Claude?
Connect Fortnox in Elaichi first. Fortnox requires an app registered inside your own Fortnox account, so one person brings that client ID and secret once and then signs in to Fortnox to approve access, and nobody has to repeat that step afterwards. Then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Fortnox then appears in Claude for you.
Does Fortnox work with ChatGPT and Cursor as well as Claude?
Yes. Once Fortnox is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Fortnox once and every client gets it.
What can an AI agent actually do with my Fortnox data?
With Fortnox connected, an agent can look up customers, articles and suppliers, read invoices, create a new invoice, and add or update a customer. It can also read your Fortnox company information. It cannot delete anything in Fortnox and it cannot change an invoice once it exists, because this connector does not offer those actions.
Does connecting Fortnox give the AI access to everything in my accounts?
No. Every call runs inside the Fortnox access of the person who signed in, so the agent sees exactly the customers, invoices and suppliers that person can already see in Fortnox. Elaichi can narrow that further, for example to reading only, but it can never widen what Fortnox itself allows.
Can I stop an agent from changing things in Fortnox?
Yes. Restrictions on a Fortnox connection work per action, so you can allow reading customers and invoices while blocking the creation of invoices or changes to customer records. A blocked action is never shown to Claude, ChatGPT or Cursor at all, so no prompt can reach it.
What happens to a Fortnox connection when someone leaves?
Offboarding a person in Elaichi ends their Fortnox access at once, in every client. If they had shared a Fortnox connection, it keeps working for everyone else on the team. Disconnecting Fortnox once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.
Does the Fortnox MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Fortnox is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Fortnox?
Yes. Both let Claude, ChatGPT or Cursor use Fortnox. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Fortnox call.
How is Elaichi different from Composio for Fortnox?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Fortnox: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Fortnox in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.