paystack-mcp
Related Servers
Alternatives to paystack-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to accept payments, verify transactions, and manage customers via Paystack API through natural language.MIT

paystack-mcp-serverofficial
AlicenseAqualityDmaintenanceEnables AI assistants to interact with the full range of Paystack APIs, allowing operations like transaction management, customer creation, and payments through natural language.2152 npm56MIT- AlicenseNot gradedqualityCmaintenanceEnables 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.6 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to interact with the Paylo commerce ecosystem, allowing them to discover merchants, search products, manage shopping carts, and facilitate transactions through Paystack.6MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables 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-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to accept payments in South Africa using Paystack's hosted checkout for cards and instant EFT.MIT
TDQS
Scored across 28 tools
Most tools have distinct resource-action pairs, but a few could be confused, such as verify_transaction vs fetch_transaction (reference vs ID) and charge_authorization vs partial_debit (full vs partial charge). Descriptions help clarify these differences, making the boundaries mostly clear.
The vast majority of tools follow a consistent verb_noun pattern (e.g., list_products, create_customer, initialize_transaction). However, a few tools like balance_ledger and transaction_totals use noun compounds instead of verb-first names, which is a minor deviation from an otherwise consistent style.
With 28 tools, this server is above the typical well-scoped range (3-15) and exceeds the 25-tool threshold for being considered too heavy. While the broad Paystack domain justifies many operations, the count feels excessive for a single MCP server and may overwhelm agents.
The tool set covers core workflows for products, customers, transactions, balances, and OTP settings. However, notable gaps exist: there is no delete operation for products or customers, no refund tool for transactions, and transfer OTP management tools without corresponding transfer initiation/list tools. These gaps could force agents to work around missing functionality.