Skip to main content
Glama
paystack-mcp

paystack-mcp

by si-essence

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoOptional. HTTP listen port when transport is http. Default 3000.
MCP_TRANSPORTNoOptional. Transport to use: stdio or http. Default stdio. --http also selects HTTP.
PAYSTACK_CONTACTNoOptional. Contact string included in the User-Agent.
PAYSTACK_BASE_URLNoOptional. Paystack API origin only. Defaults to https://api.paystack.co. http is allowed only for a loopback host. A live key is refused when the base URL is loopback.
PAYSTACK_PER_MINUTENoOptional. Local request-per-minute cap. Default 60. Paystack 429 responses are returned and not retried.
PAYSTACK_SECRET_KEYYesRequired Paystack secret key. Accepts sk_test_…, or sk_live_… only when PAYSTACK_ALLOW_LIVE_KEY is exactly true. pk_ public keys and rk_ restricted keys are refused.
PAYSTACK_TIMEOUT_MSNoOptional. Per-request timeout in milliseconds. Default 20000.
PAYSTACK_ALLOW_WRITESNoOptional. Must be exact true or every write and money action is a preview. Default off.
PAYSTACK_CACHE_TTL_SECNoOptional. Cache GET responses for this many seconds. Default 0. Payments remain uncached unless this is set.
PAYSTACK_ALLOW_LIVE_KEYNoOptional. Must be the exact string true before an sk_live_ key is accepted. Default off; values like 1, yes, and TRUE do not enable it.
PAYSTACK_ALLOW_MONEY_MOVEMENTNoOptional. Must be exact true or money actions stay a preview even when writes are enabled. Default off.

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
paystack_balanceC

paystack_balance. Actions: balance (read), ledger (read). Read-only. Amounts are positive integers in subunits.

paystack_catalogC

paystack_catalog. Actions: list_subaccounts (read), fetch_subaccount (read), list_plans (read), fetch_plan (read), list_subscriptions (read), fetch_subscription (read), list_products (read), fetch_product (read), list_pages (read), fetch_page (read). Read-only. Amounts are positive integers in subunits.

paystack_customersB

paystack_customers. Actions: list (read), fetch (read), create (write), update (write), validate (write), set_risk_action (write). Writes need confirm:true and PAYSTACK_ALLOW_WRITES=true. Money actions also need PAYSTACK_ALLOW_MONEY_MOVEMENT=true. Otherwise this is a preview and no request is sent. Amounts are positive integers in subunits.

paystack_disputesA

paystack_disputes. Actions: list (read), fetch (read), transaction (read), export (read), update (write), evidence (write), resolve (write). Writes need confirm:true and PAYSTACK_ALLOW_WRITES=true. Money actions also need PAYSTACK_ALLOW_MONEY_MOVEMENT=true. Otherwise this is a preview and no request is sent. Amounts are positive integers in subunits.

paystack_invoicesB

paystack_invoices. Actions: list (read), fetch (read), create (write), update (write), verify (read), notify (write), finalize (write), archive (write), totals (read). Writes need confirm:true and PAYSTACK_ALLOW_WRITES=true. Money actions also need PAYSTACK_ALLOW_MONEY_MOVEMENT=true. Otherwise this is a preview and no request is sent. Amounts are positive integers in subunits.

paystack_lookupsC

paystack_lookups. Actions: banks (read), resolve_account (read), countries (read), states (read), verify_account (read). Read-only. Amounts are positive integers in subunits.

paystack_recipientsB

paystack_recipients. Actions: list (read), fetch (read), create (write), update (write), delete (write). Writes need confirm:true and PAYSTACK_ALLOW_WRITES=true. Money actions also need PAYSTACK_ALLOW_MONEY_MOVEMENT=true. Otherwise this is a preview and no request is sent. Amounts are positive integers in subunits.

paystack_refundsA

paystack_refunds. Actions: list (read), fetch (read), create (money). Writes need confirm:true and PAYSTACK_ALLOW_WRITES=true. Money actions also need PAYSTACK_ALLOW_MONEY_MOVEMENT=true. Otherwise this is a preview and no request is sent. Amounts are positive integers in subunits.

paystack_settlementsC

paystack_settlements. Actions: list (read), transactions (read). Read-only. Amounts are positive integers in subunits.

paystack_transactionsB

paystack_transactions. Actions: list (read), fetch (read), verify (read), timeline (read), totals (read), export (read), initialize (money), charge_authorization (money), partial_debit (money). Writes need confirm:true and PAYSTACK_ALLOW_WRITES=true. Money actions also need PAYSTACK_ALLOW_MONEY_MOVEMENT=true. Otherwise this is a preview and no request is sent. Amounts are positive integers in subunits.

paystack_transfersA

paystack_transfers. Actions: list (read), fetch (read), verify (read), initiate (money), finalize (money), bulk (money). Writes need confirm:true and PAYSTACK_ALLOW_WRITES=true. Money actions also need PAYSTACK_ALLOW_MONEY_MOVEMENT=true. Otherwise this is a preview and no request is sent. Amounts are positive integers in subunits.

paystack_webhookA

Verify an x-paystack-signature header locally. HMAC-SHA512 of the raw body with the configured secret key, compared in constant time. No network call. The key is never returned.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

B3.4/5.0

Scored across 12 tools

Disambiguation4/5

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.

Naming Consistency5/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues