Skip to main content
Glama
spreedly

Spreedly MCP Server

Official
by spreedly

Related Servers

Alternatives to Spreedly MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to access Magpie Payment Platform APIs for processing payments, creating checkout sessions, sending invoices, and managing payment links through natural conversation.
      23 npm
      2
      MIT
    • F
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to securely interact with Payre's Web3 payment gateway for generating crypto checkout invoices, monitoring settlements, managing payout destinations, and inspecting analytics.
      18
      -
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to securely create payment references and requests for Multibanco, MB WAY, Payshop, Credit Card, PinPay, Cofidis Pay, PIX, and retrieve payment reports.
      -
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI agents to interact with multiple payment providers (Stripe, Paystack) through a unified API. Supports payment initialization, verification, refunds, customer management, and invoicing without requiring knowledge of specific provider implementations.
      2
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to interact with PayBridgeNP payment gateway accounts through natural language. Provides read-only access to payments, refunds, analytics, and account data, with write capabilities planned for future versions.
      31 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables integration with Stripe APIs through function calling, supporting operations on customers, products, invoices, subscriptions, and more.
      8,372 npm
      MIT

    TDQS

    B3.3/5.0

    Scored across 32 tools

    Disambiguation3/5

    Most tools are clearly separated by resource and action, but several list/show variants overlap in purpose, such as spreedly_gateway_list_transactions vs spreedly_transaction_list and spreedly_payment_method_list_all_events vs spreedly_event_list. The descriptions help, but an agent could easily select the wrong event or transaction listing tool.

    Naming Consistency4/5

    The dominant spreedly_<resource>_<action> pattern is consistent and readable. Minor deviations like spreedly_network_tokenization_card_metadata, spreedly_transaction_transcript, and spreedly_payment_method_update_gratis break the strict pattern but do not make the set chaotic.

    Tool Count2/5

    With 32 tools, the server exceeds the 25-tool threshold and much of the surface consists of repetitive list/show pairs across similar resources. The broad scope partly justifies the count, but the set feels heavy and redundant for an MCP server.

    Completeness2/5

    The tool set is heavily read-oriented and covers listing, showing, and some metadata updates, but core Spreedly operations such as creating payment methods, processing transactions, refunds, or managing gateways are missing. Agents attempting real payment workflows would hit significant dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive