paystack-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PAYSTACK_SECRET_KEY | Yes | Your Paystack secret key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_productC | Create a new product on your Paystack integration |
| list_productsB | List products available on your Paystack integration with pagination support |
| get_productA | Get details of a specific product by ID |
| update_productB | Update an existing product by ID |
| create_customerB | Create a new customer in Paystack |
| list_customersB | List customers available on your Paystack integration |
| get_customerA | Get details of a specific customer by email or code |
| update_customerC | Update a customer's details |
| validate_customerC | Validate a customer's identity with bank account |
| set_customer_risk_actionC | Whitelist or blacklist a customer |
| deactivate_authorizationB | Deactivate a payment authorization when a card needs to be forgotten |
| initialize_transactionC | Initialize a transaction to accept payment on Paystack |
| verify_transactionC | Verify a transaction's status using the transaction reference |
| fetch_transactionB | Get details of a transaction by ID |
| list_transactionsC | List transactions with pagination and filtering options |
| charge_authorizationB | Charge a previously authorized card |
| partial_debitB | Charge a partial amount from a previously authorized card |
| transaction_totalsC | Get total amount received on your account |
| export_transactionsC | Export a list of transactions carried out on your integration |
| list_banksC | Get a list of all banks supported by Paystack and their properties |
| list_countriesA | Get a list of countries that Paystack currently supports |
| list_statesA | Get a list of states for a country for address verification |
| check_balanceB | Get the available balance on your Paystack integration |
| balance_ledgerC | Fetch all pay-ins and pay-outs that occurred on your Paystack integration |
| resend_transfers_otpC | Generates a new OTP and sends to customer for transfer verification |
| disable_transfers_otpC | Disable OTP requirement for transfers |
| finalize_disable_otpB | Finalize the request to disable OTP on your transfers |
| enable_transfers_otpB | Enable OTP requirement for transfers |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| show-top-selling-products | Show me the top-selling products this month |
| show-low-stock-products | Which products are running low on stock? |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.