Skip to main content
Glama
Walma-Labs

fortnox-mcp

by Walma-Labs

Related Servers

Alternatives to fortnox-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables MCP clients to read and write Bokio accounting data for one company through 85 tools covering invoices, customers, suppliers, journal entries, chart of accounts, fiscal years, items, tags, uploads, SIE export, and bank payments.
      40
      463 npm
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to read Fortnox invoices and customers, validate receipts, and optionally perform approved write operations with strict safety controls.
      3
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server for integrating with the Fortnox Swedish accounting system. Enables LLMs to manage invoices, customers, suppliers, orders, accounts, vouchers, and provides business intelligence analytics.
      51
      49 npm
      45
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Exposes Visma e-conomic REST API as 73 MCP tools for managing customers, suppliers, products, invoices, quotes, orders, accounting, and reference data, with secure authentication, allowlist, read-only mode, and audit logging.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable clients to read and write directly in epago accounting, including chart of accounts, transactions, invoices, payments, receipts, and tax reports.
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Multi-tenant MCP server connecting accounting software to AI assistants via ~87 tools. Supports Bokio (Swedish accounting) with mock mode for development.
      -

    TDQS

    B3/5.0

    Scored across 26 tools

    Disambiguation4/5

    Most tools target distinct resources or actions, with clear list-vs-get pairs for invoices, suppliers, customers, vouchers, and supplier invoices. The generic list_endpoints/fortnox_get pair overlaps somewhat with the specific list/get tools, which could cause occasional misselection, but descriptions distinguish their intended use.

    Naming Consistency4/5

    The resource tools consistently use snake_case with list_* for collections and get_* for single records, which is predictable. Report tools use noun phrases such as income_statement and balance_sheet, and fortnox_get uses a provider-prefixed verb-last form, creating minor deviations from the dominant pattern.

    Tool Count3/5

    26 tools is on the heavy side for an MCP server, and the generic fortnox_get tool means some specific list/get tools could be consolidated. However, the broad Fortnox accounting domain legitimately covers many resources, so most tools have a defensible place.

    Completeness4/5

    The server provides broad read-only coverage across core accounting resources, including registers, transactions, reports, aging, and a generic read-only endpoint fallback. Some resources lack dedicated get/list tools, but agents can usually work around this via list_endpoints/fortnox_get; write operations are absent but appear intentionally out of scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues