Paystack MCP server

What the model can do

Paystack payments for one business: transactions (amount, status, channel, card type and last four, customer, paid date), totals by currency, customers, refunds, disputes, payment requests (invoices) and the balance. Can add or rename a customer, make a payment link, raise, finalise, remind about or archive a payment request, and refund a transaction, each only when asked. Amounts are in the lowest currency unit (kobo, pesewas, cents).

Reads

• paystack_list_transactionsPaystack transactions dated in a window: reference, status (success, failed, abandoned, reversed), amount and currency, fees, channel…
• paystack_get_transactionOne Paystack transaction by its numeric id: the same fields as the list.
• paystack_transaction_totalsPaystack totals for a window: number of transactions, volume by currency, and transfers still pending by currency.
• paystack_list_customersPaystack customers created in a window: id, code (CUS_…), email, name and created date.
• paystack_list_refundsPaystack refunds dated in a window: transaction, status, amount and currency, how much was deducted, type, reason, customer and dates.
• paystack_list_disputesPaystack disputes (chargebacks) customers have raised: status (awaiting merchant feedback, awaiting bank feedback, pending, resolved), category…
• paystack_list_payment_requestsPaystack payment requests (invoices): id, code, status (draft, pending, success, failed), paid, amount and currency, description, invoice number…
• paystack_balanceThe Paystack business's available balance in each currency.

Acts, when you ask

These change something in Paystack. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• paystack_create_customerAdd a customer to Paystack with an email and optional name.
• paystack_update_customerChange a Paystack customer's first or last name.
• paystack_initialize_transactionCreate a Paystack payment page link for an amount, tied to a customer email.
• paystack_create_payment_requestRaise a Paystack payment request (invoice) for a customer.
• paystack_finalize_payment_requestFinalise a draft Paystack payment request so it is issued to the customer and can be paid.
• paystack_send_payment_request_reminderHave Paystack email the customer a reminder to pay a payment request.
• paystack_archive_payment_requestArchive a Paystack payment request: it is no longer listed and cannot be verified or paid.
• paystack_create_refundRefund a completed Paystack transaction to the customer, in full or, with amount, in part (never more than was paid).

Connect it

First connect Paystack on Dashboard → Connections, then add Memtro to your client once. The Paystack tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Paystack connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › How much did we take through Paystack this week?
• › Which transactions failed yesterday?
• › Which disputes are awaiting our feedback?
• › Which payment requests are still unpaid?
• › Refund half of transaction 4099260516 to the customer

Questions

Is this an official Paystack MCP server?

No. It is Memtro's MCP server with Memtro's Paystack connector behind it: the connector reads Paystack through its API with the credentials you connect on Dashboard → Connections, and Paystack publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Paystack?

Only when you ask, and only what it has been granted: add a customer; change a customer's name; create a payment link for an amount (nothing is sent; the link is returned); raise a payment request (invoice), as a draft or emailed to the customer; finalise a draft payment request (the customer may be emailed); email a customer a reminder about a payment request; archive a payment request (it stops being listed or payable); refund a transaction, in full or in part (moves money back to the customer). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Finance and commerce

• Xero MCP server
• Stripe MCP server
• Felloh MCP server
• Wise MCP server
• Starling Bank MCP server
• QuickBooks Online MCP server