Skip to main content
Glama
Sign In
paystack-mcp-server

paystack-mcp-server

Official
by PaystackOSS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to paystack-mcp-server

No user-submitted related servers found.

    Related Servers

    • paystack-mcp

      zerotaldev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to create Paystack checkout links, verify payments, read transaction history, and list supported banks across African markets, with test-mode enforcement and safety guards for live payments.
      20 npm
      MIT
    • Pletopay MCP Server

      Pletopay MCP Serverofficial

      pletopay
      A
      license
      B
      quality
      C
      maintenance
      Enables AI agents to manage payments, virtual accounts, customers, transfers, refunds, settlements, checkout, payment links, invoices, subscriptions, reports, webhooks, and sandbox operations through the API, with built-in safeguards for live money movement.
      85
      76 npm
      MIT

    • Fin-MCP Payment Server

      Veri5ied
      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
      -

    • Mono Banking MCP Server

      sin4ch
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to perform Nigerian banking operations including account management, payments, and identity verification through the Mono Open Banking API.
      59
      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.7/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: one retrieves details about a Paystack API operation, the other executes the actual request. No overlap in functionality.

    Naming Consistency5/5

    Both tool names follow a consistent verb_noun pattern: get_paystack_operation and make_paystack_request, making them predictable and easy to use.

    Tool Count3/5

    With only 2 tools, the server feels thin for a full Paystack API wrapper. However, the generic design allows coverage of many operations, but 2 is borderline for typical MCP servers.

    Completeness5/5

    The tool set covers all Paystack operations listed in the get_paystack_operation description. The discovery-and-execute pattern ensures no missing functionality.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Resources