Skip to main content
Glama
tajchert

wfirma-mcp

by tajchert
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to wfirma-mcp

No user-submitted related servers found.

    Related Servers

    • wFirma MCP

      agente-dev
      A
      license
      A
      quality
      B
      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
      17 npm
      1
      MIT

    • BizDesk MCP

      syedahmad0786
      A
      license
      Not graded
      quality
      C
      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

    • Inv.bg-MCP

      unbelievable-digital
      F
      license
      Not graded
      quality
      B
      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
      -

    • ordis-mcp-server

      NicoAraya1902
      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

    • 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
    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

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources