Skip to main content
Glama
PaddleHQ

Paddle MCP Server

Official
by PaddleHQ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Paddle MCP Server

No user-submitted related servers found.

    Related Servers

    • PayPal MCP Server

      arbuthnot-eth
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides comprehensive integration with PayPal's APIs, enabling seamless interaction with payment processing, invoicing, subscription management, and business operations through a standardized interface.
      7
      Apache 2.0

    • Tradovate MCP Server

      alexanimal
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables interaction with the Tradovate API for managing trading contracts, positions, orders, and accounts.
      1
      MIT

    • Ryft MCP

      bkawk
      A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server that enables interaction with the Ryft API to manage financial resources such as payment sessions, customers, and subscriptions. It supports comprehensive operations including payouts, disputes, and account-scoped requests through a secure stdio interface.
      69
      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 63 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific resources and actions in the Paddle ecosystem. For example, create_address, get_address, and list_addresses are distinct from create_adjustment, get_adjustment_credit_note, and list_adjustments, with no overlap in functionality. The descriptions provide clear boundaries, making it easy for an agent to differentiate between tools like create_transaction and preview_transaction_create.

    Naming Consistency5/5

    Tool names follow a highly consistent verb_noun pattern throughout, such as create_address, get_address, list_addresses, and preview_transaction_create. All tools use snake_case uniformly, with verbs like create, get, list, preview, replay, and update applied predictably across different entities like customer, subscription, and notification. This consistency aids in readability and predictability.

    Tool Count2/5

    With 63 tools, the count is excessive for typical MCP server purposes, making it overwhelming and heavy for agents to navigate. While Paddle's API is comprehensive, this many tools suggests poor scoping for an MCP interface, where a more streamlined set (e.g., 15-25 tools) would be more appropriate. The high count increases cognitive load and potential for misselection.

    Completeness5/5

    The tool set provides complete CRUD and lifecycle coverage for Paddle's domain, including entities like addresses, adjustments, businesses, customers, discounts, notifications, prices, products, reports, simulations, subscriptions, and transactions. It includes create, get, list, preview, and update operations where applicable, with no obvious gaps—agents can perform all core workflows from creation to management and reporting without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources