Skip to main content
Glama
gronnmann

fiken-mcp

by gronnmann
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to fiken-mcp

No user-submitted related servers found.

    Related Servers

    • Fiken MCP

      wollum-as
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects Claude or ChatGPT to Fiken accounting through Fiken login with no API keys, enabling read-only or read/write access to company, invoice, report, and bookkeeping data. It can also perform confirmed actions such as posting documents and sending invoices.
      14 npm
      Apache 2.0

    • 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

    • fortnox-mcp-server

      Proviscale
      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
      94 npm
      1
      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
      -

    • PowerOffice Go MCP

      sjurebass
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to read and write accounting data in PowerOffice Go, including bookkeeping, sales, purchases, payroll, time tracking, and read-only bank access, with support for multiple companies and strict isolation.
      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

    C2.7/5.0

    Scored across 106 tools

    Disambiguation3/5

    Most tools are clearly separated by resource and action, but the domain contains several easy-to-confuse pairs: invoices vs sales, generic transactions vs purchases/sales/journal entries, and bank balances vs account balances. Descriptions provide enough hints, but an agent often needs accounting domain knowledge to pick the right one.

    Naming Consistency5/5

    All tools share the fiken_ prefix and follow a predictable verb_noun pattern (list/get/create/update/delete/send), with regular conventions for drafts, attachments, counters, and 'from_draft' conversions. The naming is highly consistent across all 106 tools.

    Tool Count1/5

    106 tools is an extreme mismatch for an MCP server surface; it exposes the entire Fiken REST API as individual tools and will overwhelm agent context and selection. Even if every endpoint is useful, this should be split into multiple focused servers or consolidated where possible.

    Completeness3/5

    Core workflows are well covered: contacts, invoices, credit notes, offers, purchases, sales, drafts, attachments, and counters all have substantial CRUD/lifecycle support. However, several exposed resources are list-only (groups, projects, time entries, activities, time users, inbox), and finalized purchases/sales/credit notes have no update path, so the surface has notable gaps.

    Maintenance

    ActivityStale
    ResponsivenessSlow

    Resources