Skip to main content
Glama
Fortnox MCP Server

Fortnox MCP Server

by erp-mafia

Fortnox MCP Server

An MCP (Model Context Protocol) server for integrating with the Fortnox Swedish accounting system. This server enables LLMs to interact with Fortnox for managing invoices, customers, suppliers, orders, accounts, vouchers, and provides business intelligence analytics.

Two Ways to Use

Mode

Best For

Setup

Remote Mode

End users

Just add URL, authorize in browser

Local Mode

Developers, self-hosted

Configure environment variables


Related MCP server: fortnox-mcp-server

The easiest way to use Fortnox MCP - no credentials needed, just authorize in your browser.

Option A: Add to Claude.ai (Web)

  1. Go to claude.ai

  2. Navigate to Settings → Integrations → Add Integration

  3. Enter the URL: https://fortnox-mcp.vercel.app/mcp

  4. Wait for it to load, then authorize access by clicking connect

Option B: Add to Claude Desktop

Open your Claude Desktop config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this configuration:

{
  "mcpServers": {
    "fortnox": {
      "url": "https://fortnox-mcp.vercel.app/mcp"
    }
  }
}

Restart Claude Desktop. When you first ask Claude to do something with Fortnox, a browser window will open for you to authorize access to your Fortnox account. Once authorized, you're all set!


Quick Start: Local Mode (Self-Hosted)

For developers who want to run the server locally or use their own Fortnox app credentials.

1. Get your Fortnox credentials

  1. Register at Fortnox Developer Portal

  2. Create an application to get your Client ID and Client Secret

  3. Complete the OAuth2 flow to get a Refresh Token

2. Add to Claude Desktop

Open your Claude Desktop config file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Add this configuration:

{
  "mcpServers": {
    "fortnox": {
      "command": "npx",
      "args": ["-y", "fortnox-mcp-server"],
      "env": {
        "FORTNOX_CLIENT_ID": "your-client-id",
        "FORTNOX_CLIENT_SECRET": "your-client-secret",
        "FORTNOX_REFRESH_TOKEN": "your-refresh-token"
      }
    }
  }
}

3. Restart Claude Desktop

That's it! You can now ask Claude to manage your Fortnox invoices, customers, and more.


Features

Customer Management

  • fortnox_list_customers - List and search customers

  • fortnox_get_customer - Get customer details

  • fortnox_create_customer - Create new customer

  • fortnox_update_customer - Update customer

  • fortnox_delete_customer - Delete customer

Invoice Management

  • fortnox_list_invoices - List invoices with filtering

  • fortnox_get_invoice - Get invoice details with line items

  • fortnox_create_invoice - Create new invoice

  • fortnox_update_invoice - Update draft invoice

  • fortnox_bookkeep_invoice - Bookkeep invoice

  • fortnox_cancel_invoice - Cancel invoice

  • fortnox_credit_invoice - Create credit note

  • fortnox_send_invoice_email - Send invoice by email

Supplier Management

  • fortnox_list_suppliers - List and search suppliers

  • fortnox_get_supplier - Get supplier details

  • fortnox_create_supplier - Create new supplier

  • fortnox_update_supplier - Update supplier

  • fortnox_delete_supplier - Delete supplier

Supplier Invoice Management

  • fortnox_list_supplier_invoices - List supplier invoices with filtering

  • fortnox_get_supplier_invoice - Get supplier invoice details

  • fortnox_approve_supplier_invoice - Approve supplier invoice for payment

  • fortnox_payables_report - Get accounts payable aging report

Order Management

  • fortnox_list_orders - List sales orders with filtering

  • fortnox_list_offers - List offers/quotes with filtering

Account Management

  • fortnox_list_accounts - List chart of accounts

  • fortnox_get_account - Get account details

  • fortnox_create_account - Create new account

  • fortnox_update_account - Update account

  • fortnox_delete_account - Delete account

Voucher Management

  • fortnox_list_vouchers - List vouchers (journal entries)

  • fortnox_get_voucher - Get voucher details with rows

  • fortnox_create_voucher - Create manual voucher

  • fortnox_list_voucher_series - List available voucher series

  • fortnox_account_activity - Get activity for a specific account

  • fortnox_search_vouchers - Search vouchers by description, account, or amount

Company Information

  • fortnox_get_company_info - Get company details

  • fortnox_list_financial_years - List company financial years

Analytics

  • fortnox_invoice_summary - Get invoice statistics by period

  • fortnox_top_customers - Get top customers by revenue

  • fortnox_unpaid_report - Get detailed unpaid invoice report

Business Intelligence

  • fortnox_cash_flow_forecast - Forecast cash flow based on invoices and payables

  • fortnox_order_pipeline - Analyze sales order pipeline

  • fortnox_sales_funnel - Analyze sales funnel from offers to invoices

  • fortnox_product_performance - Analyze product/article performance

  • fortnox_period_comparison - Compare financial metrics across periods

  • fortnox_customer_growth - Analyze customer acquisition and growth

  • fortnox_project_profitability - Analyze project profitability (if using projects)

  • fortnox_cost_center_analysis - Analyze costs by cost center

  • fortnox_expense_analysis - Analyze expenses by category

  • fortnox_yearly_comparison - Compare year-over-year performance

  • fortnox_gross_margin_trend - Track gross margin trends over time

Installation

No installation needed! Just add the config above to Claude Desktop.

Manual Installation

npm install -g fortnox-mcp-server

From Source

git clone https://github.com/jakobwennberg/fortnox-mcp.git
cd fortnox-mcp
npm install
npm run build

Configuration

Environment Variables

Local Mode (default)

Variable

Required

Description

FORTNOX_CLIENT_ID

Yes

Your Fortnox app client ID

FORTNOX_CLIENT_SECRET

Yes

Your Fortnox app client secret

FORTNOX_REFRESH_TOKEN

Yes

OAuth2 refresh token (only needed for initial setup; automatically persisted after first use)

FORTNOX_ACCESS_TOKEN

No

Current access token (auto-refreshed)

TRANSPORT

No

stdio (default) or http

PORT

No

HTTP port (default: 3000)

Remote Mode (AUTH_MODE=remote)

Variable

Required

Description

AUTH_MODE

Yes

Set to remote

SERVER_URL

Yes

Public URL of your server

JWT_SECRET

Yes

Secret for signing JWT tokens

FORTNOX_CLIENT_ID

Yes

Your Fortnox app client ID

FORTNOX_CLIENT_SECRET

Yes

Your Fortnox app client secret

UPSTASH_REDIS_REST_URL

Yes*

Upstash Redis URL for token storage

UPSTASH_REDIS_REST_TOKEN

Yes*

Upstash Redis token

PORT

No

HTTP port (default: 3000)

*Falls back to in-memory storage if not provided (not recommended for production)

Getting OAuth Credentials

  1. Register as a developer at Fortnox Developer Portal

  2. Create a new application to get Client ID and Client Secret

  3. Complete the OAuth2 authorization flow to obtain a refresh token

  4. Set the environment variables

Usage

With Claude Desktop

See Quick Start above.

As HTTP Server

TRANSPORT=http PORT=3000 node dist/index.js

Then connect to http://localhost:3000/mcp

Tool Examples

List Unpaid Invoices

{
  "tool": "fortnox_list_invoices",
  "arguments": {
    "filter": "unpaid",
    "limit": 20
  }
}

Create Invoice

{
  "tool": "fortnox_create_invoice",
  "arguments": {
    "customer_number": "1001",
    "rows": [
      {
        "description": "Consulting services",
        "quantity": 10,
        "price": 1000
      }
    ]
  }
}

Create Voucher

{
  "tool": "fortnox_create_voucher",
  "arguments": {
    "voucher_series": "A",
    "description": "Office supplies",
    "transaction_date": "2025-01-24",
    "rows": [
      { "account_number": 6110, "debit": 500 },
      { "account_number": 1910, "credit": 500 }
    ]
  }
}

Rate Limiting

The Fortnox API allows 25 requests per 5 seconds. This server includes automatic rate limiting to prevent exceeding this limit.

Development

# Run in development mode with auto-reload
npm run dev

# Build for production
npm run build

# Clean build artifacts
npm run clean

Publishing & Distribution

This server is published to multiple registries for easy installation:

Registry

URL

Purpose

npm

npmjs.com/package/fortnox-mcp-server

Package distribution via npx

MCP Registry

registry.modelcontextprotocol.io

Official MCP server discovery

GitHub

github.com/jakobwennberg/fortnox-mcp

Source code

How It Works

  1. User adds config to Claude Desktop with npx fortnox-mcp-server

  2. Claude Desktop starts the server via npx (downloads latest version from npm)

  3. Server authenticates with Fortnox using OAuth2 credentials from environment variables

  4. Claude can now use tools like fortnox_list_invoices, fortnox_create_customer, etc.

  5. Server handles API calls to Fortnox, including automatic token refresh and rate limiting

Token Persistence (Local Mode)

Fortnox refresh tokens are single-use — each token refresh returns a new one. The server automatically persists the latest refresh token to ~/.fortnox-mcp/tokens.json so it survives process restarts without requiring manual config updates.

  • On first run, the server reads FORTNOX_REFRESH_TOKEN from your environment/config

  • After each token refresh, the new refresh token is saved to ~/.fortnox-mcp/tokens.json

  • On subsequent restarts, the server uses the persisted token (which is always the latest)

  • If the persisted file is missing or corrupt, the server falls back to the environment variable

The token file is created with restricted permissions (0600) for security.

Releasing New Versions

To release a new version, use the release script:

# Bug fixes (1.0.0 → 1.0.1)
npm run release:patch

# New features (1.0.0 → 1.1.0)
npm run release:minor

# Breaking changes (1.0.0 → 2.0.0)
npm run release:major

The release script automatically:

  1. Bumps the version in package.json

  2. Updates server.json for the MCP Registry

  3. Builds the project

  4. Commits and tags the release

  5. Publishes to npm

  6. Publishes to MCP Registry

  7. Pushes to GitHub

Prerequisites for releasing:

  • npm login - Logged into npm

  • mcp-publisher login github - Logged into MCP Registry

  • Clean git working directory

Users Get Updates Automatically

When you publish a new version, users running npx -y fortnox-mcp-server will automatically get the latest version the next time they restart Claude Desktop.


Deploying Your Own Remote Server

Want to host your own instance of the Fortnox MCP server? Follow these instructions.

Deploy to Vercel

Deploy with Vercel

1. Prerequisites

2. Set Environment Variables

In your Vercel project settings, add these environment variables:

Variable

Description

AUTH_MODE

Set to remote

SERVER_URL

Your Vercel deployment URL (e.g., https://your-app.vercel.app)

JWT_SECRET

A random secret string for signing tokens (generate with openssl rand -hex 32)

FORTNOX_CLIENT_ID

Your Fortnox app client ID

FORTNOX_CLIENT_SECRET

Your Fortnox app client secret

UPSTASH_REDIS_REST_URL

Upstash Redis REST URL

UPSTASH_REDIS_REST_TOKEN

Upstash Redis REST token

3. Configure Fortnox OAuth Callback

In your Fortnox app settings, add this redirect URI:

https://your-app.vercel.app/oauth/fortnox/callback

4. Deploy

vercel --prod

Server Endpoints

Endpoint

Description

GET /health

Health check

GET /.well-known/oauth-authorization-server

OAuth metadata

POST /authorize

Start OAuth flow

POST /token

Exchange code for tokens

GET /oauth/fortnox/callback

Fortnox OAuth callback

POST /mcp

Protected MCP endpoint

Architecture

┌─────────────────────────────────────────────────────────────┐
│                    fortnox-mcp-server                       │
├─────────────────────────────────────────────────────────────┤
│   Mode: AUTH_MODE=local | remote                            │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│   LOCAL MODE                    REMOTE MODE                 │
│   ───────────                   ───────────                 │
│   • Env var tokens              • OAuth flow                │
│   • Single user                 • Multi-user                │
│   • stdio or HTTP               • HTTP only                 │
│   • Auto-persisted tokens       • Token storage (Redis)     │
│     (~/.fortnox-mcp/)                                       │
│                                                             │
└─────────────────────────────────────────────────────────────┘

License

MIT

Available Tools

51 tools
fortnox_account_activityAccount Activity ReportA
Read-onlyIdempotent

Show all voucher transactions affecting specific account(s).

IMPORTANT: The financial_year parameter uses Fortnox sequential IDs (1, 2, 3...), NOT calendar years. Use fortnox_list_financial_years first to find the correct ID for your target year.

Common use cases:

  • Rent expenses: account_number=5010 (or 5010-5099 range)

  • Salary costs: account_range={ from: 7000, to: 7999 }

  • Bank transactions: account_number=1930

  • Revenue analysis: account_range={ from: 3000, to: 3999 }

Note: This tool fetches voucher details and filters client-side since the Fortnox API doesn't support native account filtering. Use date ranges to limit the scan.

Args:

  • account_number (number): Single account number to filter by (1000-9999)

  • account_numbers (array): Multiple account numbers to filter by (max 20)

  • account_range (object): Account range { from: 3000, to: 3999 }

  • financial_year (number): Fortnox financial year ID (use fortnox_list_financial_years to find)

  • period ('today' | ... | 'last_year'): Convenience date period filter

  • from_date (string): Filter vouchers from this date (YYYY-MM-DD)

  • to_date (string): Filter vouchers to this date (YYYY-MM-DD)

  • voucher_series (string): Filter by voucher series (e.g., 'A')

  • include_summary (boolean): Include totals per account (default: true)

  • max_vouchers (number): Max vouchers to scan, 10-500 (default: 500)

  • response_format ('markdown' | 'json'): Output format

Returns: Transactions matching the account criteria with optional summary.

Examples:

  • First call fortnox_list_financial_years to find that ID 4 = 2025

  • Bank transactions this month: account_number=1930, financial_year=4, period="this_month"

  • Salary costs: account_range={ from: 7000, to: 7999 }, financial_year=4

  • Rent expenses: account_number=5010, financial_year=4

Inputs: no named parameters.

fortnox_approve_supplier_invoiceApprove Supplier Invoice for PaymentA

Approve a supplier invoice for payment.

This approves the invoice and marks it ready for payment processing.

Args:

  • given_number (string): The supplier invoice given number to approve (required)

  • response_format ('markdown' | 'json'): Output format

Returns: Confirmation that the invoice has been approved for payment.

Inputs: given_number (required), response_format.

fortnox_bookkeep_invoiceBookkeep Fortnox InvoiceA

Bookkeep an invoice, creating the accounting entries. Once booked, the invoice cannot be edited.

Args:

  • document_number (string): Invoice document number to bookkeep (required)

  • response_format ('markdown' | 'json'): Output format

Returns: Confirmation of bookkeeping with the created voucher reference.

Inputs: document_number (required), response_format.

fortnox_cancel_invoiceCancel Fortnox InvoiceA
Destructive

Cancel an invoice. Booked invoices will have reversal entries created.

Args:

  • document_number (string): Invoice document number to cancel (required)

  • response_format ('markdown' | 'json'): Output format

Returns: Confirmation of cancellation.

Inputs: document_number (required), response_format.

fortnox_cash_flow_forecastCash Flow ForecastA
Read-onlyIdempotent

Generate cash flow forecast from unpaid receivables and payables. Shows expected inflows, outflows, net flow, and running balance grouped by week or month.

Inputs: group_by, horizon_days, include_overdue, response_format, +1 more.

fortnox_cost_center_analysisCost Center AnalysisA
Read-onlyIdempotent

[LIMITED] Analyze costs by cost center/department. Returns cost center list only.

For actual cost center data, use fortnox_account_activity with cost center filtering on vouchers.

Inputs: period, to_date, from_date, cost_center, +3 more.

fortnox_create_accountCreate Fortnox AccountB

Create a new account in the chart of accounts.

Args:

  • account_number (number): Account number 1000-9999 (required)

  • description (string): Account description (required)

  • vat_code (string): VAT code for the account

  • active (boolean): Whether the account is active (default: true)

  • cost_center_settings ('ALLOWED' | 'MANDATORY' | 'NOTALLOWED'): Cost center settings

  • project_settings ('ALLOWED' | 'MANDATORY' | 'NOTALLOWED'): Project settings

  • sru_code (number): SRU code for tax reporting

Returns: The created account details.

Inputs: description (required), account_number (required), active, sru_code, +4 more.

fortnox_create_customerCreate Fortnox CustomerA

Create a new customer in Fortnox.

Args:

  • name (string): Customer name (required)

  • customer_number (string): Customer number (auto-generated if not provided)

  • organisation_number (string): Company registration number

  • email (string): Primary email address

  • phone (string): Primary phone number

  • address1, address2, zip_code, city, country, country_code: Address fields

  • currency (string): 3-letter currency code (e.g., 'SEK')

  • vat_number (string): VAT registration number

  • vat_type ('SEVAT' | 'EUVAT' | 'EUREVERSEDVAT' | 'EXPORT'): VAT type

  • terms_of_payment (string): Payment terms code

  • price_list (string): Price list code

  • comments (string): Internal comments

Returns: The created customer with assigned customer number.

Inputs: name (required), city, email, phone, +14 more.

fortnox_create_invoiceCreate Fortnox InvoiceA

Create a new invoice in Fortnox.

Args:

  • customer_number (string): Customer number (required)

  • rows (array): Invoice line items (at least one required)

    • Each row: { description, quantity?, price?, article_number?, unit?, discount?, vat?, account_number? }

  • invoice_date (string): Invoice date YYYY-MM-DD (defaults to today)

  • due_date (string): Due date YYYY-MM-DD

  • our_reference (string): Our reference person

  • your_reference (string): Customer's reference

  • invoice_type ('INVOICE' | 'CASH' | 'CARD' | 'UNDEFINED'): Invoice type

  • currency (string): 3-letter currency code

  • terms_of_payment (string): Payment terms code

  • comments (string): Internal comments

  • remarks (string): Remarks printed on invoice

  • freight (number): Shipping cost

  • administration_fee (number): Admin fee

  • send_type ('EMAIL' | 'PRINT' | 'EINVOICE'): How to send

Returns: The created invoice with assigned document number.

Example rows: [{ "description": "Consulting services", "quantity": 10, "price": 1000 }]

Inputs: rows (required), customer_number (required), freight, remarks, +11 more.

fortnox_create_supplierCreate Fortnox SupplierA

Create a new supplier in Fortnox.

Args:

  • name (string): Supplier name (required)

  • supplier_number (string): Supplier number (auto-generated if not provided)

  • organisation_number (string): Company registration number

  • email (string): Email address

  • phone (string): Phone number

  • address1, address2, zip_code, city, country, country_code: Address fields

  • currency (string): 3-letter currency code

  • vat_number (string): VAT registration number

  • bank_account (string): Bank account number

  • bg_number (string): Bankgiro number

  • pg_number (string): Plusgiro number

  • terms_of_payment (string): Payment terms code

  • comments (string): Internal comments

Returns: The created supplier with assigned supplier number.

Inputs: name (required), city, email, phone, +15 more.

fortnox_create_voucherCreate Fortnox VoucherA

Create a new voucher (manual accounting entry) in Fortnox.

IMPORTANT: The sum of debits must equal the sum of credits (balanced entry).

Args:

  • voucher_series (string): Voucher series (e.g., 'A', 'B') (required)

  • description (string): Voucher description (required)

  • transaction_date (string): Transaction date YYYY-MM-DD (required)

  • rows (array): Accounting rows, minimum 2 (required)

    • Each row: { account_number, debit?, credit?, description?, cost_center?, project? }

  • cost_center (string): Default cost center for all rows

  • project (string): Default project for all rows

Returns: The created voucher with assigned voucher number.

Example: Create a cash payment voucher: { "voucher_series": "A", "description": "Office supplies payment", "transaction_date": "2025-01-24", "rows": [ { "account_number": 6110, "debit": 500, "description": "Office supplies" }, { "account_number": 1910, "credit": 500, "description": "Cash" } ] }

Inputs: rows (required), description (required), voucher_series (required), transaction_date (required), +3 more.

fortnox_credit_invoiceCredit Fortnox InvoiceA

Create a credit note for an invoice. This creates a new credit invoice referencing the original.

Args:

  • document_number (string): Invoice document number to credit (required)

  • response_format ('markdown' | 'json'): Output format

Returns: The created credit invoice details.

Inputs: document_number (required), response_format.

fortnox_customer_growthCustomer Growth AnalyticsA
Read-onlyIdempotent

Identify growing and declining customers by comparing revenue across periods. Shows growth rates and trends.

Inputs: current_period (required), show, top_n, compare_to, +2 more.

fortnox_delete_accountDelete Fortnox AccountA
Destructive

Delete an account from the chart of accounts.

WARNING: This action cannot be undone. The account must not have any transactions.

Args:

  • account_number (number): Account number to delete (required)

Returns: Confirmation of deletion.

Inputs: account_number (required).

fortnox_delete_customerDelete Fortnox CustomerA
Destructive

Delete a customer from Fortnox.

WARNING: This action cannot be undone. The customer must not have any invoices or orders.

Args:

  • customer_number (string): Customer number to delete (required)

Returns: Confirmation of deletion.

Inputs: customer_number (required).

fortnox_delete_supplierDelete Fortnox SupplierA
Destructive

Delete a supplier from Fortnox.

WARNING: This action cannot be undone. The supplier must not have any invoices.

Args:

  • supplier_number (string): Supplier number to delete (required)

Returns: Confirmation of deletion.

Inputs: supplier_number (required).

fortnox_expense_analysisExpense AnalysisA
Read-onlyIdempotent

[LIMITED] Analyze expenses by account class. Returns category structure only.

For actual expense data, use fortnox_account_activity with account_range={from: 4000, to: 8999}.

Inputs: period, to_date, group_by, from_date, +4 more.

fortnox_get_accountGet Fortnox AccountA
Read-onlyIdempotent

Retrieve detailed information about a specific account.

Args:

  • account_number (number): The account number to retrieve (1000-9999, required)

  • response_format ('markdown' | 'json'): Output format

Returns: Complete account details including description, VAT settings, and balances.

Inputs: account_number (required), response_format.

fortnox_get_company_infoGet Fortnox Company InformationA
Read-onlyIdempotent

Retrieve information about the company connected to this Fortnox account.

Returns company name, organisation number, addresses, contact details, and other company information.

Args:

  • response_format ('markdown' | 'json'): Output format

Returns: Company details including name, organisation number, address, and contact information.

Inputs: response_format.

fortnox_get_customerGet Fortnox CustomerA
Read-onlyIdempotent

Retrieve detailed information about a specific customer.

Args:

  • customer_number (string): The customer number to retrieve (required)

  • response_format ('markdown' | 'json'): Output format

Returns: Complete customer details including contact info, addresses, payment terms, and VAT settings.

Inputs: customer_number (required), response_format.

fortnox_get_invoiceGet Fortnox InvoiceA
Read-onlyIdempotent

Retrieve detailed information about a specific invoice including all line items.

Args:

  • document_number (string): The invoice document number to retrieve (required)

  • response_format ('markdown' | 'json'): Output format

Returns: Complete invoice details including customer info, dates, amounts, line items, and payment status.

Inputs: document_number (required), response_format.

fortnox_get_supplierGet Fortnox SupplierA
Read-onlyIdempotent

Retrieve detailed information about a specific supplier.

Args:

  • supplier_number (string): The supplier number to retrieve (required)

  • response_format ('markdown' | 'json'): Output format

Returns: Complete supplier details including contact info, addresses, bank details, and payment terms.

Inputs: supplier_number (required), response_format.

fortnox_get_supplier_invoiceGet Fortnox Supplier InvoiceA
Read-onlyIdempotent

Retrieve detailed information about a specific supplier invoice including all line items.

Args:

  • given_number (string): The supplier invoice given number to retrieve (required)

  • response_format ('markdown' | 'json'): Output format

Returns: Complete supplier invoice details including supplier info, dates, amounts, line items, and payment status.

Inputs: given_number (required), response_format.

fortnox_get_voucherGet Fortnox VoucherA
Read-onlyIdempotent

Retrieve detailed information about a specific voucher including all accounting rows.

IMPORTANT: The financial_year parameter uses Fortnox sequential IDs (1, 2, 3...), NOT calendar years. Use fortnox_list_financial_years first to find the correct ID for your target year.

Args:

  • voucher_series (string): Voucher series (e.g., 'A') (required)

  • voucher_number (number): Voucher number within the series (required)

  • financial_year (number): Fortnox financial year ID (use fortnox_list_financial_years to find)

  • response_format ('markdown' | 'json'): Output format

Returns: Complete voucher details including all debit/credit rows.

Inputs: voucher_number (required), voucher_series (required), financial_year, response_format.

fortnox_gross_margin_trendGross Margin Trend AnalyticsA
Read-onlyIdempotent

[LIMITED] Analyze gross margin trends. Returns formula and structure only.

For actual margin data, use fortnox_account_activity with:

  • Revenue: account_range={from: 3000, to: 3999}

  • COGS: account_range={from: 4000, to: 4999}

Inputs: period, to_date, group_by, from_date, +3 more.

fortnox_invoice_summaryInvoice Summary AnalyticsA
Read-onlyIdempotent

Calculate summary statistics for invoices over a period.

Answers questions like:

  • "What was my total revenue this month?"

  • "How many invoices did we send last quarter?"

  • "What's the average invoice amount this year?"

  • "Show me revenue breakdown by customer"

Args:

  • period ('today' | 'yesterday' | 'this_week' | 'last_week' | 'this_month' | 'last_month' | 'this_quarter' | 'last_quarter' | 'this_year' | 'last_year'): Date period to analyze

  • from_date (string): Start date YYYY-MM-DD (ignored if period specified)

  • to_date (string): End date YYYY-MM-DD (ignored if period specified)

  • filter ('cancelled' | 'fullypaid' | 'unpaid' | 'unpaidoverdue' | 'unbooked'): Filter by invoice status

  • customer_number (string): Filter by specific customer

  • group_by ('customer' | 'month' | 'status'): Group statistics by dimension

  • include_details (boolean): Include individual invoice list (default: false)

  • response_format ('markdown' | 'json'): Output format

Returns: For JSON: { period, date_range, summary: { count, total, average, min, max, ... }, groups?: [...], invoices?: [...] } For Markdown: Formatted summary with totals and optional breakdown

Examples:

  • Monthly revenue: period="this_month"

  • Revenue by customer this year: period="this_year", group_by="customer"

  • Unpaid invoice totals: filter="unpaid"

Error Handling:

  • Returns truncation warning if >10,000 invoices

  • Returns "Error: ..." if API call fails

Inputs: filter, period, to_date, group_by, +4 more.

fortnox_list_accountsList Fortnox AccountsA
Read-onlyIdempotent

List accounts from the chart of accounts in Fortnox.

Retrieves a paginated list of accounts with optional filtering.

Args:

  • limit (number): Max results per page, 1-100 (default: 20)

  • page (number): Page number for pagination (default: 1)

  • search_description (string): Search accounts by description

  • from_account (number): Filter accounts from this number (1000-9999)

  • to_account (number): Filter accounts to this number (1000-9999)

  • response_format ('markdown' | 'json'): Output format

Returns: List of accounts with account number, description, and active status.

Examples:

  • List revenue accounts: from_account=3000, to_account=3999

  • List expense accounts: from_account=4000, to_account=8999

Inputs: page, limit, to_account, from_account, +2 more.

fortnox_list_customersList Fortnox CustomersA
Read-onlyIdempotent

List customers from Fortnox accounting system.

Retrieves a paginated list of customers with optional filtering by status, name, or customer number.

Args:

  • limit (number): Max results per page, 1-100 (default: 20)

  • page (number): Page number for pagination (default: 1)

  • filter ('active' | 'inactive'): Filter by customer status

  • search_name (string): Search customers by name (partial match)

  • customer_number (string): Filter by specific customer number

  • organisation_number (string): Filter by organisation number

  • response_format ('markdown' | 'json'): Output format

Returns: List of customers with customer number, name, email, city, and organisation number.

Examples:

  • List all active customers: filter="active"

  • Search by name: search_name="Acme"

  • Get specific customer: customer_number="1001"

Inputs: page, limit, filter, search_name, +3 more.

fortnox_list_financial_yearsList Financial YearsA
Read-onlyIdempotent

List all financial years configured in Fortnox.

IMPORTANT: Voucher tools (fortnox_list_vouchers, fortnox_account_activity, etc.) use Fortnox sequential IDs (1, 2, 3...) NOT calendar years. Use this tool first to find the correct ID.

Example: If ID 4 maps to 2025-01-01 to 2025-12-31, use financial_year=4 in voucher tools.

Args:

  • response_format ('markdown' | 'json'): Output format

Returns: List of financial years with ID, date range, and accounting method.

Inputs: response_format.

fortnox_list_invoicesList Fortnox InvoicesA
Read-onlyIdempotent

List invoices from Fortnox accounting system.

Retrieves a paginated list of invoices with optional filtering by status, customer, date range, or amount. Supports convenience period filters and can fetch all results for large datasets.

Args:

  • limit (number): Max results per page, 1-100 (default: 20)

  • page (number): Page number for pagination (default: 1)

  • filter ('cancelled' | 'fullypaid' | 'unpaid' | 'unpaidoverdue' | 'unbooked'): Filter by invoice status

  • customer_number (string): Filter by customer number

  • from_date (string): Filter invoices from this date (YYYY-MM-DD)

  • to_date (string): Filter invoices to this date (YYYY-MM-DD)

  • period ('today' | 'yesterday' | 'this_week' | 'last_week' | 'this_month' | 'last_month' | 'this_quarter' | 'last_quarter' | 'this_year' | 'last_year'): Convenience date period, overrides from_date/to_date

  • from_final_pay_date (string): Filter by due date from (YYYY-MM-DD)

  • to_final_pay_date (string): Filter by due date to (YYYY-MM-DD)

  • sortby ('customername' | 'customernumber' | 'documentnumber' | 'invoicedate' | 'total'): Field to sort by

  • sortorder ('ascending' | 'descending'): Sort order (default: ascending)

  • fetch_all (boolean): Fetch all results by auto-paginating (max 10,000 results)

  • min_amount (number): Filter invoices >= this amount (client-side)

  • max_amount (number): Filter invoices <= this amount (client-side)

  • response_format ('markdown' | 'json'): Output format

Returns: For JSON: { total, page, limit, count, has_more, total_pages, next_offset?, truncated?, invoices: [...] } For Markdown: Formatted list with pagination info

Examples:

  • List unpaid invoices: filter="unpaid"

  • Last month's invoices: period="last_month"

  • Top invoices by amount: sortby="total", sortorder="descending"

  • All invoices over 10000: fetch_all=true, min_amount=10000

  • Customer invoices this year: customer_number="1001", period="this_year"

Error Handling:

  • Returns "Error: Rate limit exceeded..." if API limit hit

  • Returns truncation info if fetch_all hits safety limits

Inputs: page, limit, filter, period, +11 more.

fortnox_list_offersList Fortnox OffersA
Read-onlyIdempotent

List sales offers/quotes with filtering by status, customer, date range. Filter: cancelled, expired, ordercreated, ordernotcreated.

Inputs: page, limit, filter, period, +7 more.

fortnox_list_ordersList Fortnox OrdersA
Read-onlyIdempotent

List sales orders with filtering by status, customer, date range. Filter: cancelled, expired, invoicecreated, invoicenotcreated.

Inputs: page, limit, filter, period, +7 more.

fortnox_list_supplier_invoicesList Fortnox Supplier InvoicesA
Read-onlyIdempotent

List supplier invoices (accounts payable) from Fortnox.

Retrieves a paginated list of supplier invoices with optional filtering by status, supplier, date range, or amount.

Args:

  • limit (number): Max results per page, 1-100 (default: 20)

  • page (number): Page number for pagination (default: 1)

  • filter ('cancelled' | 'fullypaid' | 'unpaid' | 'unpaidoverdue' | 'unbooked' | 'pendingpayment'): Filter by invoice status

  • supplier_number (string): Filter by supplier number

  • from_date (string): Filter invoices from this date (YYYY-MM-DD)

  • to_date (string): Filter invoices to this date (YYYY-MM-DD)

  • period ('today' | 'yesterday' | ... | 'last_year'): Convenience date period, overrides from_date/to_date

  • from_final_pay_date (string): Filter by due date from (YYYY-MM-DD)

  • to_final_pay_date (string): Filter by due date to (YYYY-MM-DD)

  • sortby ('suppliername' | 'suppliernumber' | 'invoicenumber' | 'invoicedate' | 'total'): Field to sort by

  • sortorder ('ascending' | 'descending'): Sort order (default: ascending)

  • fetch_all (boolean): Fetch all results by auto-paginating (max 10,000 results)

  • min_amount (number): Filter invoices >= this amount (client-side)

  • max_amount (number): Filter invoices <= this amount (client-side)

  • response_format ('markdown' | 'json'): Output format

Returns: List of supplier invoices with supplier, dates, amounts, and status.

Examples:

  • List unpaid supplier invoices: filter="unpaid"

  • Last month's supplier invoices: period="last_month"

  • Supplier invoices this year: supplier_number="1", period="this_year"

Inputs: page, limit, filter, period, +11 more.

fortnox_list_suppliersList Fortnox SuppliersA
Read-onlyIdempotent

List suppliers from Fortnox accounting system.

Retrieves a paginated list of suppliers with optional filtering.

Args:

  • limit (number): Max results per page, 1-100 (default: 20)

  • page (number): Page number for pagination (default: 1)

  • filter ('active' | 'inactive'): Filter by supplier status

  • search_name (string): Search suppliers by name (partial match)

  • response_format ('markdown' | 'json'): Output format

Returns: List of suppliers with supplier number, name, email, city, and organisation number.

Inputs: page, limit, filter, search_name, +1 more.

fortnox_list_vouchersList Fortnox VouchersA
Read-onlyIdempotent

List vouchers (accounting entries) from Fortnox.

Retrieves a paginated list of vouchers with optional filtering.

IMPORTANT: The financial_year parameter uses Fortnox sequential IDs (1, 2, 3...), NOT calendar years. Use fortnox_list_financial_years first to find the correct ID for your target year.

Args:

  • limit (number): Max results per page, 1-100 (default: 20)

  • page (number): Page number for pagination (default: 1)

  • voucher_series (string): Filter by voucher series (e.g., 'A', 'B')

  • financial_year (number): Fortnox financial year ID (use fortnox_list_financial_years to find)

  • from_date (string): Filter vouchers from this date (YYYY-MM-DD)

  • to_date (string): Filter vouchers to this date (YYYY-MM-DD)

  • response_format ('markdown' | 'json'): Output format

Returns: List of vouchers with series, number, description, and date.

Examples:

  • First call fortnox_list_financial_years to find that ID 4 = 2025

  • List vouchers for 2025: financial_year=4

  • List manual vouchers: voucher_series="A", financial_year=4

Inputs: page, limit, to_date, from_date, +3 more.

fortnox_list_voucher_seriesList Fortnox Voucher SeriesA
Read-onlyIdempotent

List available voucher series in Fortnox.

Voucher series are used to categorize vouchers (e.g., 'A' for manual entries, 'B' for bank, etc.).

Args:

  • response_format ('markdown' | 'json'): Output format

Returns: List of voucher series with code, description, and whether manual entries are allowed.

Inputs: response_format.

fortnox_order_pipelineOrder Pipeline AnalyticsA
Read-onlyIdempotent

Analyze order pipeline and backlog. Shows pending vs invoiced orders grouped by status, customer, or month.

Inputs: period, to_date, group_by, from_date, +1 more.

fortnox_payables_reportAccounts Payable Aging ReportA
Read-onlyIdempotent

Generate an accounts payable aging report for unpaid supplier invoices.

Answers questions like:

  • "What supplier invoices are overdue?"

  • "How much do we owe each supplier?"

  • "Show me aging breakdown of payables"

  • "Which supplier invoices over 10,000 SEK are unpaid?"

Args:

  • min_amount (number): Only include invoices >= this amount

  • supplier_number (string): Filter by specific supplier

  • group_by ('supplier' | 'age_bucket' | 'both'): How to group report (default: both)

  • include_details (boolean): Include individual invoice list (default: true)

  • response_format ('markdown' | 'json'): Output format

Returns: Aging report with summary, breakdowns by supplier and age bucket.

Age Buckets:

  • not_due: Due date is in the future

  • 1-30 days: Overdue 1-30 days

  • 31-60 days: Overdue 31-60 days

  • 61-90 days: Overdue 61-90 days

  • 90+ days: Overdue more than 90 days

Examples:

  • Full payables report: (use defaults)

  • Large unpaid invoices: min_amount=50000

  • Specific supplier: supplier_number="1"

Inputs: group_by, min_amount, include_details, response_format, +1 more.

fortnox_period_comparisonPeriod Comparison AnalyticsA
Read-onlyIdempotent

Compare business metrics (revenue, invoice count, etc.) between two time periods with percentage changes.

Inputs: current_period (required), metrics, compare_to, response_format.

fortnox_product_performanceProduct Performance AnalyticsA
Read-onlyIdempotent

Analyze product/customer sales performance. Returns top performers ranked by revenue, quantity, or invoice count.

Inputs: top_n, metric, period, to_date, +3 more.

fortnox_project_profitabilityProject Profitability AnalyticsA
Read-onlyIdempotent

[LIMITED] Analyze profitability by project. Returns project list only.

For actual project financials, use fortnox_account_activity with project filtering on vouchers.

Inputs: period, to_date, from_date, project_number, +2 more.

fortnox_sales_funnelSales Funnel AnalyticsA
Read-onlyIdempotent

Analyze sales funnel from offers to orders to invoices. Shows counts, values, and conversion rates at each stage.

Inputs: period, to_date, from_date, response_format.

fortnox_search_vouchersSearch VouchersA
Read-onlyIdempotent

Search vouchers by description text.

IMPORTANT: The financial_year parameter uses Fortnox sequential IDs (1, 2, 3...), NOT calendar years. Use fortnox_list_financial_years first to find the correct ID for your target year.

Performs client-side text search across voucher descriptions.

Args:

  • search_text (string): Text to search for in voucher descriptions (min 2 chars)

  • financial_year (number): Fortnox financial year ID (use fortnox_list_financial_years to find)

  • period ('today' | ... | 'last_year'): Convenience date period filter

  • from_date (string): Filter vouchers from this date (YYYY-MM-DD)

  • to_date (string): Filter vouchers to this date (YYYY-MM-DD)

  • voucher_series (string): Filter by voucher series (e.g., 'A')

  • case_sensitive (boolean): Case-sensitive search (default: false)

  • include_rows (boolean): Include voucher row details (default: false)

  • max_vouchers (number): Max vouchers to scan, 10-500 (default: 500)

  • response_format ('markdown' | 'json'): Output format

Returns: Vouchers with descriptions matching the search text.

Examples:

  • First call fortnox_list_financial_years to find that ID 4 = 2025

  • Find salary vouchers: search_text="salary", financial_year=4, period="this_year"

  • Find rent payments: search_text="rent", financial_year=4, voucher_series="B"

Inputs: search_text (required), period, to_date, from_date, +6 more.

fortnox_send_invoice_emailSend Fortnox Invoice by EmailA

Send an invoice to the customer via email.

The invoice will be sent to the email address configured for the customer.

Args:

  • document_number (string): Invoice document number to send (required)

  • response_format ('markdown' | 'json'): Output format

Returns: Confirmation that the email was sent.

Inputs: document_number (required), response_format.

fortnox_top_customersTop Customers AnalyticsA
Read-onlyIdempotent

Identify top customers by various metrics.

Answers questions like:

  • "Who are my top 10 customers by revenue?"

  • "Which customers have the most invoices?"

  • "Who has the highest unpaid balance?"

  • "What's the average invoice size per customer?"

Args:

  • metric ('total_amount' | 'invoice_count' | 'unpaid_amount' | 'average_invoice'): How to rank customers (default: total_amount)

  • period ('today' | ... | 'last_year'): Date period to analyze

  • from_date (string): Start date YYYY-MM-DD (ignored if period specified)

  • to_date (string): End date YYYY-MM-DD (ignored if period specified)

  • top_n (number): Number of customers to return, 1-50 (default: 10)

  • include_details (boolean): Include invoice breakdown per customer (default: false)

  • response_format ('markdown' | 'json'): Output format

Returns: For JSON: { metric, period, customers: [{ rank, customer_number, customer_name, value, invoice_count, ... }] } For Markdown: Ranked table of top customers

Examples:

  • Top 10 by revenue this year: period="this_year", top_n=10

  • Customers with most unpaid: metric="unpaid_amount"

  • Top 5 by invoice count last month: metric="invoice_count", period="last_month", top_n=5

Error Handling:

  • Returns truncation warning if >10,000 invoices analyzed

  • Returns "Error: ..." if API call fails

Inputs: top_n, metric, period, to_date, +3 more.

fortnox_unpaid_reportUnpaid Invoices ReportA
Read-onlyIdempotent

Generate an accounts receivable aging report for unpaid invoices.

Answers questions like:

  • "What invoices are overdue?"

  • "How much is owed by each customer?"

  • "Show me aging breakdown of receivables"

  • "Which invoices over 10,000 SEK are unpaid?"

Args:

  • min_amount (number): Only include invoices >= this amount

  • customer_number (string): Filter by specific customer

  • group_by ('customer' | 'age_bucket' | 'both'): How to group report (default: both)

  • include_details (boolean): Include individual invoice list (default: true)

  • response_format ('markdown' | 'json'): Output format

Returns: For JSON: { summary, by_customer?, by_age_bucket?, invoices? } For Markdown: Formatted aging report with totals

Age Buckets:

  • not_due: Due date is in the future

  • 1-30 days: Overdue 1-30 days

  • 31-60 days: Overdue 31-60 days

  • 61-90 days: Overdue 61-90 days

  • 90+ days: Overdue more than 90 days

Examples:

  • Full aging report: (use defaults)

  • Large unpaid invoices: min_amount=50000

  • Specific customer aging: customer_number="1001"

Error Handling:

  • Returns truncation warning if >10,000 invoices

  • Returns "Error: ..." if API call fails

Inputs: group_by, min_amount, customer_number, include_details, +1 more.

fortnox_update_accountUpdate Fortnox AccountB
Idempotent

Update an existing account in the chart of accounts.

Args:

  • account_number (number): Account number to update (required)

  • description (string): Account description

  • vat_code (string): VAT code

  • active (boolean): Whether the account is active

  • cost_center_settings ('ALLOWED' | 'MANDATORY' | 'NOTALLOWED'): Cost center settings

  • project_settings ('ALLOWED' | 'MANDATORY' | 'NOTALLOWED'): Project settings

Returns: The updated account details.

Inputs: account_number (required), active, vat_code, description, +3 more.

fortnox_update_customerUpdate Fortnox CustomerA
Idempotent

Update an existing customer in Fortnox.

Args:

  • customer_number (string): Customer number to update (required)

  • name, email, phone, address fields, etc.: Fields to update (only provided fields are changed)

Returns: The updated customer details.

Inputs: customer_number (required), city, name, email, +13 more.

fortnox_update_invoiceUpdate Fortnox InvoiceA
Idempotent

Update an existing invoice in Fortnox. Only unbooked invoices can be updated.

Args:

  • document_number (string): Invoice document number to update (required)

  • rows (array): Updated line items (replaces all existing rows)

  • Other fields: Same as create_invoice

Returns: The updated invoice details.

Inputs: document_number (required), rows, freight, remarks, +7 more.

fortnox_update_supplierUpdate Fortnox SupplierA
Idempotent

Update an existing supplier in Fortnox.

Args:

  • supplier_number (string): Supplier number to update (required)

  • All other fields from create_supplier (only provided fields are updated)

Returns: The updated supplier details.

Inputs: supplier_number (required), city, name, email, +13 more.

fortnox_yearly_comparisonYearly Comparison AnalyticsA
Read-onlyIdempotent

Compare revenue and metrics across multiple years (2-5). Shows year-over-year growth trends.

Inputs: years, metrics, response_format.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 51 tools

    Disambiguation3/5

    The CRUD tools for customers, suppliers, invoices, and accounts are clearly distinct, but the large set of analytical tools creates ambiguity. Tools like period_comparison vs yearly_comparison, customer_growth vs period_comparison, and several 'LIMITED' tools that all defer to account_activity have overlapping or unclear boundaries.

    Naming Consistency4/5

    All tools share the fortnox_ prefix and consistently use lowercase with underscores. However, the pattern is not strictly verb_noun: CRUD tools use list_/get_/create_/update_/delete_, while analytics use noun-based names like invoice_summary, order_pipeline, and cash_flow_forecast. The style is predictable but not uniform.

    Tool Count2/5

    With 51 tools, the server is heavily oversized. Many analytics overlap or are stubs (e.g., five 'LIMITED' tools that just point to account_activity), suggesting the tool count could be reduced significantly without losing functionality. This exceeds the 25+ threshold for 'too many'.

    Completeness3/5

    Core financial entities (customers, suppliers, invoices, accounts, vouchers) have solid lifecycle coverage, but there are notable gaps: order and offer tools are list-only with no create/get/update/delete, supplier invoices lack creation/update, and several analytics return only metadata or structure rather than actual data, causing dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the FreeAgent accounting API, enabling LLMs to securely access and manage accounting data including contacts, invoices, bills, bank transactions, and more.
      5 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to manage invoices, customers, suppliers, accounting entries, orders, and more through Fortnox's cloud accounting platform via natural language.
      20
      68 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      An MCP server for Danish accounting via Billy.dk API, enabling natural-language control over invoices, bank lines, reports, and more, with a write-guard for safety.
      65
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for the Elorus invoicing and accounting platform, enabling AI assistants to create invoices, manage contacts, and query financial data through natural language.
      43
      5
      MIT