Skip to main content
Glama
wfirma-mcp

wfirma-mcp

by tajchert

Related Servers

Alternatives to wfirma-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      Provides read-only access to wFirma company data, invoices, contractors, expenses, and payments, letting AI assistants query the wFirma API v2 without modifying records.
      9
      34 npm
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude Desktop and Claude Code to retrieve read-only accounting and sales-invoice data and build profit-and-loss statements, balance sheets, year-over-year comparisons, monthly trends, and dimension-filtered financial reports.
      12
      1
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Gives Claude direct, keyless access to Polish public registries: it validates NIP checksums, checks a company's VAT status and bank account against the VAT whitelist, pulls KRS court-registry extracts, and fetches the correct NBP exchange rate for an invoice date. Runs locally as an MCP server for Claude Desktop, Claude Code, Cursor and other MCP clients.
      5
      1
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides structured, read-mostly access to small-business back-office data including customers, invoices, and account notes, allowing Claude to query overdue invoices, revenue summaries, and more.
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to inv.bg invoicing data, enabling users to list clients and invoices and retrieve full document details and line items through natural language in Claude.
      1
      -
    • A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server for the Ordis accounting API, exposing 11 typed tools to query financial data such as invoices, tax forms, KPIs, and more directly from Claude.
      11
      MIT

    TDQS

    A3.9/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: get_* tools read singular details while list_* tools read collections, and the two register tools are separated by tax type. There is no meaningful overlap between tool purposes, and the descriptions reinforce the boundaries.

    Naming Consistency4/5

    The tools follow a consistent snake_case pattern with get_ for single-object reads and list_ for collection reads. The only deviation is session_status, which breaks the verb_noun pattern and would be more consistent as get_session_status.

    Tool Count5/5

    Nine tools is a well-scoped size for an accounting data integration. Each tool earns its place by covering a distinct aspect of the domain, and the count is neither bloated nor too thin.

    Completeness4/5

    The surface covers core read operations for invoices, declarations, expenses, registers, contractors, and session state. Minor gaps exist: there is no contractor listing, no expense detail tool, and writes are entirely absent, but this may be intentional for a read-only reporting bridge.

    Maintenance

    ActivityStale
    ResponsivenessOutdated data