Skip to main content
Glama
t4dhg

@t4dhg/mcp-holded

by t4dhg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @t4dhg/mcp-holded

No user-submitted related servers found.

    Related Servers

    • holded-mcp

      YerayRodri
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Holded invoicing and treasury management, enabling creation and management of invoices, purchases, estimates, contacts, bank accounts, and cashflow forecasts.
      MIT

    • MCP Holded

      nubiia-dev
      A
      license
      B
      quality
      B
      maintenance
      A Model Context Protocol (MCP) server for the Holded Invoice API. This server allows AI assistants like Claude to interact with Holded's invoicing, contacts, products, and more.
      78
      10 npm
      19
      MIT

    • Holded API MCP

      alexfdez1010
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to search and execute 360 operations across Holded's accounting, sales, inventory, contacts, CRM, projects, team, calendar, inbox, and developer APIs. Supports read and write calls with an API key, including a read-only mode.
      MIT

    • billingo-mcp

      bartadaniel
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for the Billingo V3 Hungarian invoicing API. Manage invoices, partners, products, spendings, and bank accounts from any MCP client.
      14 npm
      1
      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 15 tools

    Disambiguation4/5

    Each top-level tool maps to a distinct Holded domain, so the primary purposes are clear. A few action names recur across domains (e.g., list_accounts in accounting vs. treasury, task actions in CRM vs. projects), which could cause occasional misselection without careful attention to the tool context.

    Naming Consistency5/5

    All tools follow the same `holded_<domain>` snake_case pattern, and actions within each tool use consistent lowercase snake_case verbs and nouns. The meta tools holded_discover and holded_request also fit the prefix convention cleanly.

    Tool Count5/5

    15 tools is at the upper end of the ideal range but appropriate for a broad ERP suite covering contacts, sales, purchases, payments, treasury, accounting, catalog, team, CRM, projects, calendar, inbox, and webhooks. Each domain tool earns its place, and the discover and request tools provide useful navigation and escape-hatch roles.

    Completeness5/5

    The domain tools provide broad lifecycle coverage: create, read, update, delete, list, and domain-specific actions like approve, send, reconcile, and attach. The low-level holded_request tool also covers the remaining ~350 v2 operations, so there are no dead ends and the set is effectively complete for the stated API surface.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources