paystack-mcp
Related Servers
Alternatives to paystack-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI agents to manage Paystack payments, products, customers, and transactions through natural language.289MIT
- 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.20 npmMIT

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.294 npm56MIT- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to accept payments, verify transactions, and manage customers via Paystack API through natural language.MIT

Pletopay MCP Serverofficial
AlicenseBqualityCmaintenanceEnables 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.8576 npmMIT- 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-
TDQS
Scored across 12 tools
Tools are cleanly partitioned by resource domain (transactions, transfers, refunds, customers, disputes, etc.), so an agent can map intent to tool easily. There is minor overlap where 'verify' appears in transactions, invoices, transfers, and lookups, and where catalog bundles subscriptions/plans/products/pages/subaccounts, but descriptions make the target clear.
Every tool follows the same paystack_<resource> snake_case convention with a consistent prefix. The action-level verbs (list, fetch, create, update, verify) are applied uniformly inside each tool, giving a predictable structure throughout.
Twelve resource-grouped tools sit squarely in the well-scoped range, and each earns its place by covering a distinct Paystack domain. The grouping into action-dispatched tools keeps the count compact without omitting major areas.
Core money and lifecycle flows are covered: transactions, transfers, refunds, invoices, recipients, disputes, settlements, customers, plus webhook signature verification. The main gap is that paystack_catalog is read-only, so plans, products, pages, subaccounts, and subscriptions cannot be created or updated, and payment-page creation is absent.