Visma MCP Server

MCP server for Visma eAccounting — manage invoices, customers, suppliers, and accounting via AI agents. Covers Norway, Finland, Netherlands, UK.

Local serverstdio

What is the Visma MCP server?

Connect Visma to Claude, Cursor or any other MCP client and it stops being a tab you switch to. MCP server for Visma eAccounting — manage invoices, customers, suppliers, and accounting via AI agents. Covers Norway, Finland, Netherlands, UK. The visma mcp server is what makes that connection.

What the server does

Connect AI agents to Visma eAccounting — used by businesses across Norway, Finland, Netherlands, and UK.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • Category — Tools
  • Invoices — list_invoices, get_invoice, create_invoice, send_invoice, list_invoice_payments
  • Customers — list_customers, get_customer, create_customer
  • Suppliers — list_supplier_invoices, get_supplier, create_supplier_invoice
  • Accounting — list_vouchers, create_voucher, list_accounts, list_fiscal_years
  • Reports — get_company_info, list_projects, list_cost_centers
  • Orders — list_orders, create_quote

Credentials and setup notes

Configuration is passed through the environment: VISMA_ACCESS_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

Where it fits

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Visma's toolset — Category, Invoices, Customers and 4 more — is a fair guide to whether it matches your workflow. It is maintained by proviscale; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
CategoryTools
Invoiceslist_invoices, get_invoice, create_invoice, send_invoice, list_invoice_payments
Customerslist_customers, get_customer, create_customer
Supplierslist_supplier_invoices, get_supplier, create_supplier_invoice
Accountinglist_vouchers, create_voucher, list_accounts, list_fiscal_years
Reportsget_company_info, list_projects, list_cost_centers
Orderslist_orders, create_quote

How to install the Visma MCP server

{
  "mcpServers": {
    "visma": {
      "command": "npx",
      "args": ["-y", "visma-eaccounting-mcp-server"],
      "env": {
        "VISMA_ACCESS_TOKEN": "your-access-token-here"
      }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
VISMA_ACCESS_TOKENCredential the server authenticates with.Yes

Example prompts to try

  • Use Visma to Category.
  • Use Visma to Invoices.
  • Use Visma to Customers.

Frequently asked questions

It connects Visma to MCP-compatible AI assistants such as Claude and Cursor, exposing 7 tools (Category, Invoices, Customers, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Visma directly.