Skip to main content
Glama
vvitovec

ABRA Flexi MCP Server

by vvitovec

Related Servers

Alternatives to ABRA Flexi MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Provides a comprehensive MCP interface to the AbraFlexi ERP REST API, enabling management of invoices, contacts, products, bank transactions, and other evidence through natural language.
      68
      2
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with the sevDesk accounting API for managing contacts, invoices, credit notes, orders, vouchers, transactions, and parts.
      3 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only interaction with the FakturaXL API for querying invoices, clients, products, and stock levels with pagination, date chunking, and rate limiting.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides read-only access to Xledger accounting data via GraphQL API for querying invoices, balances, projects, timesheets, and more.
      2
      MIT
    • 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
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Frappe Framework sites through comprehensive document operations, schema introspection, report generation, and method execution. Provides secure API-based access to create, read, update, and delete Frappe documents while supporting financial reporting and DocType management.
      24
      16
      ISC

    TDQS

    C2.3/5.0

    Scored across 29 tools

    Disambiguation3/5

    Many tools have distinct roles but there is overlap between flexi_get_record_detail and get_document_detail, and similar pairs. The descriptions help, but the prefix split adds ambiguity.

    Naming Consistency2/5

    Inconsistent use of 'flexi_' prefix on some tools while others use plain snake_case. Patterns like 'get_partner_summary' vs 'flexi_get_record_summary' break uniformity.

    Tool Count3/5

    29 tools is high but covers a broad domain. Each tool seems justified, but the count could be reduced by consolidating similar summary/detail pairs.

    Completeness3/5

    Document workflow is well-covered (create, update, validate, post) but missing delete/cancel. Partners and products only have read/search, lacking create/update/delete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues