Skip to main content
Glama
Proviscale

fortnox-mcp-server

by Proviscale
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to fortnox-mcp-server

No user-submitted related servers found.

    Related Servers

    • Tripletex MCP Server

      cwvedvik
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with the Tripletex accounting system via 56 tools and 18 skills for orders, invoices, bookkeeping, reports, projects, and travel expenses.
      23
      MIT

    • fiken-mcp

      gronnmann
      A
      license
      C
      quality
      C
      maintenance
      Enables AI assistants to manage invoices, contacts, purchases, journal entries, and other accounting operations via the Fiken API.
      100
      7 npm
      1
      MIT

    • manager-mcp

      onexurOSS
      A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants to query and manage self-hosted accounting data—invoices, balances, and books—through natural language, with read-only tools by default and optional scoped write operations.
      10
      MIT

    • Tripletex MCP Server

      adriantr
      F
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with the Tripletex accounting API to manage time tracking, projects, and timesheet approvals through natural language. It also supports searching and managing outgoing invoices and processing supplier invoice approvals.
      31
      2
      -

    • Zoho Books MCP Server

      kkeeling
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage Zoho Books accounting tasks such as invoices, contacts, expenses, and sales orders through natural language.
      40
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 20 tools

    Disambiguation5/5

    Every tool targets a distinct resource-action combination. Invoices, customers, suppliers, accounting entries, projects, cost centers, orders, and offers are clearly separated with no overlap.

    Naming Consistency5/5

    All tools use a consistent verb_noun pattern in snake_case (e.g., get_invoice, list_customers, create_voucher). Variations like 'get_accounts' vs 'get_customer' follow the same pattern.

    Tool Count5/5

    20 tools cover a broad ERP domain (invoicing, customers, suppliers, accounting, projects, orders, offers) without being excessive. Each tool earns its place.

    Completeness3/5

    Core operations are present (create, read, list for key entities), but notable gaps exist: no update or delete for invoices, customers, suppliers, or orders. Offers lack list/get/update. The surface is functional but incomplete for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources