Skip to main content
Glama
Sign In
Holded API MCP

Holded API MCP

by alexfdez1010
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Holded API MCP

No user-submitted related servers found.

    Related Servers

    • @t4dhg/mcp-holded

      t4dhg
      A
      license
      B
      quality
      B
      maintenance
      MCP server for Holded API v2, enabling listing and querying of contacts, invoices, purchases, products, services, and payments, with low-level access to any endpoint.
      15
      76 npm
      1
      MIT

    • contasimple-mcp

      fervalnav
      A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to query and register invoices, suppliers, and payments through the Contasimple API v2, including optional write access for creating records, attaching files, and managing payments.
      16
      MIT

    • 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

    • bokio-mcp

      straycatse
      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
      465 npm
      MIT

    • agentpay-gateway

      Rumblingb
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides a single MCP endpoint for 90+ tools across 42 backend servers (search, legal, domain, etc.) with per-call credit billing and a single API key.
      1
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    The four tools have clearly distinct roles: search the catalog, inspect an operation schema, execute GET operations, and execute mutating operations. There is little risk of confusing read and write execution because the descriptions explicitly separate GET from POST/PUT/PATCH/DELETE.

    Naming Consistency4/5

    All tools share the holded_ prefix and use readable verb/object-style names. The set is mostly consistent, though search_operations, get_operation, read, and write use slightly different granularity conventions.

    Tool Count5/5

    Four tools are well-scoped for a catalog-backed API gateway: discovery, schema inspection, read execution, and write execution. Each tool has a clear purpose and no obvious redundant surface.

    Completeness4/5

    The catalog-search plus schema-inspection plus execute-read/write pattern can cover the full Holded API surface generically. Minor gaps may exist around authentication/setup guidance or catalog browsing beyond search, but the core lifecycle is present.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources