fortnox-automation-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORTNOX_BASE_URL | No | Base URL for the Fortnox API. | https://api.fortnox.se |
| FORTNOX_ENV_FILE | No | Path to an environment file containing the Fortnox configuration. | |
| FORTNOX_AUDIT_LOG | No | Path to the audit log file. | |
| FORTNOX_CLIENT_ID | No | Fortnox developer application client ID. | |
| FORTNOX_COMPANY_ID | No | Fortnox company identifier. | |
| FORTNOX_ACCESS_TOKEN | No | Current Fortnox access token. | |
| FORTNOX_CLIENT_SECRET | No | Fortnox developer application client secret. | |
| FORTNOX_ENABLE_WRITES | No | Set to '1' to expose write tools. Defaults to '0' (reads only). | 0 |
| FORTNOX_REFRESH_TOKEN | No | Fortnox refresh token for token rotation. | |
| FORTNOX_APPROVAL_TOKEN | No | Secret token required for each write operation when writes are enabled. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fortnox_list_invoicesC | List Fortnox invoices (read-only) |
| fortnox_list_customersC | List Fortnox customers (read-only) |
| fortnox_preview_receiptA | Validate a receipt and build a balanced voucher preview; does not write to Fortnox |
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 3 tools
The three tools have clearly distinct purposes: listing invoices, listing customers, and previewing a receipt. There is no overlap in resource or action, so an agent can easily select the right tool.
All tool names follow a consistent pattern with the same prefix and verb_noun structure: fortnox_list_invoices, fortnox_list_customers, fortnox_preview_receipt. The convention is predictable and readable.
Three tools is on the thin side for a server named 'automation', which suggests broader workflow support. It is not critically low, but the surface feels under-scoped for the implied domain.
The server offers only read-only listing and one non-writing preview, while Fortnox automation would typically require creating, updating, or deleting invoices/customers and posting vouchers. Significant lifecycle operations are missing, which would cause agent failures for common automation tasks.