Skip to main content
Glama
COMR4D3B451L

fortnox-automation-mcp

by COMR4D3B451L

Related Servers

Alternatives to fortnox-automation-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible agents to securely access an Invoice4U account for searching documents and customers and creating receipts linked to paid invoices, with read-only behavior by default.
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables MCP-capable agents to read Fintaro invoices and transactions, and upload receipts, via a scoped API key with PII-safe projections.
      6
      Apache 2.0
    • 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
      71 npm
      40
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables managing Moneybird bookkeeping through MCP tools: look up contacts, read invoices, check bank mutations, log time, and pull reports, with optional write access.
      52
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables reading reports and accounting data, searching transactions, inspecting accounts, categories, payees, and rules, and optionally authorizing undoable bookkeeping changes through MCP.
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      Enables Codex to securely access PowerOffice Go API v2 with read-only tools and write operations that require explicit confirmation for customers and general ledger accounts.
      10
      1
      -

    TDQS

    B3/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count3/5

    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.

    Completeness2/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues