fortnox-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORTNOX_ACCESS_TOKEN | Yes | OAuth2 access token from Fortnox |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_invoicesB | List and filter invoices. Supports filtering by status, date range, and pagination. |
| get_invoiceB | Get full details of a specific invoice by its document number. |
| create_invoiceB | Create a new invoice for a customer with line items. |
| send_invoiceC | Send an invoice to the customer via email. |
| get_invoice_paymentsA | Check payment status and history for a specific invoice. |
| list_customersC | Search and filter the customer database. |
| get_customerB | Get full details of a specific customer. |
| create_customerB | Add a new customer to Fortnox. |
| list_supplier_invoicesC | List incoming supplier invoices (bills/expenses). |
| get_supplierA | Get details of a specific supplier/vendor. |
| create_supplier_invoiceC | Record a new supplier invoice (expense/bill). |
| list_vouchersC | List journal entries/vouchers. Optionally filter by financial year. |
| create_voucherB | Create a manual journal entry (voucher). Rows must balance (total debit = total credit). |
| get_accountsA | Get the chart of accounts. Useful for finding account numbers for bookkeeping. |
| get_financial_yearB | Get information about financial/accounting years. |
| get_company_infoB | Get company information and settings from Fortnox. |
| list_projectsC | List all projects for tracking time and costs. |
| list_cost_centersC | List cost centers for allocating expenses across departments or projects. |
| list_ordersB | List and filter sales orders. |
| create_offerC | Create a quote/offer for a customer. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 20 tools
Every tool targets a distinct resource-action combination. Invoices, customers, suppliers, accounting entries, projects, cost centers, orders, and offers are clearly separated with no overlap.
All tools use a consistent verb_noun pattern in snake_case (e.g., get_invoice, list_customers, create_voucher). Variations like 'get_accounts' vs 'get_customer' follow the same pattern.
20 tools cover a broad ERP domain (invoicing, customers, suppliers, accounting, projects, orders, offers) without being excessive. Each tool earns its place.
Core operations are present (create, read, list for key entities), but notable gaps exist: no update or delete for invoices, customers, suppliers, or orders. Offers lack list/get/update. The surface is functional but incomplete for full lifecycle management.