Skip to main content
Glama
Pletopay MCP Server

Pletopay MCP Server

Official
by pletopay

Related Servers

Alternatives to Pletopay MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI assistants with read and safe-write access to Alternative Payments customers, invoices, payment requests, transactions, payouts, and webhooks without directly moving money.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to interact with the full range of Paystack APIs, allowing operations like transaction management, customer creation, and payments through natural language.
      2
      86 npm
      56
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables developers and AI agents to create, verify, refund, and check payments across multiple Indian payment gateways through one unified MCP toolset, with subscriptions, customers, webhooks, settlements, capability discovery, and credential-free mock testing.
      17
      559 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to interact with Juspay's payment processing APIs and merchant dashboard for managing orders, transactions, refunds, customers, gateways, and reporting through natural language.
      21
      Apache 2.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables conversational AI agents to manage Razorpay payments directly, including payment lookups, order creation, refunds, UPI QR generation, and real-time webhook triage via the Model Context Protocol.
      -

    TDQS

    B3.2/5.0

    Scored across 85 tools

    Disambiguation4/5

    Most tools are clearly separated by resource and action, and the by-reference lookup variants are explicitly named. A few overlaps remain, notably create_payment versus dynamic create_virtual_account, which describe the same underlying operation, and the event/delivery tools require careful reading to distinguish.

    Naming Consistency5/5

    The tool set uses a consistent snake_case verb_noun pattern throughout: get_, list_, create_, update_, delete_, plus clear lifecycle verbs such as close_, expire_, finalize_, void_, cancel_, rotate_, and replay_. Reference lookups follow a predictable get_<resource>_by_reference pattern with only minor compound names.

    Tool Count1/5

    85 tools is far above a well-scoped MCP tool set and forces agents to choose among a very large number of resource-specific endpoints. Even for a broad payments platform, this surface is heavy and could be consolidated, especially reference-lookup variants, event delivery tools, and CRUD groups.

    Completeness5/5

    The surface covers full lifecycle operations for core domains: payments, virtual accounts, customers, subaccounts, splits, transfers, refunds, invoices, subscriptions, plans, checkout sessions, payment links, webhooks/events, reports, risk, settlements, docs, and sandbox tools. It includes create/get/list/update/lifecycle and reconciliation operations, with no obvious dead end for the stated payments purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues