← All integrations

Flutterwave MCP server

53 operations0 webhooks

Payments API for accepting charges and payment links, and managing transfers, beneficiaries, subaccounts, virtual accounts, subscriptions, settlements, refunds, bills, banks, and wallet balances.

Try Flutterwave with your agent

Connect Flutterwave, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in Flutterwave on my account, then run one read-only example and show me the result.

Runs once, when you ask

Flutterwave tools and triggers

Tools are what your agent can do in Flutterwave through Corsair's MCP server. Triggers are the Flutterwave events a routine can start from.

Transactions

  • Generate ReferenceRead-only

    Generate a unique transaction reference.

    transactions.generateReference

  • GetRead-only

    Get a transaction by ID.

    transactions.get

  • Get FeeRead-only

    Get transaction fee estimate.

    transactions.getFee

  • ListRead-only

    Retrieve all transactions.

    transactions.list

  • Verify By ReferenceRead-only

    Verify a transaction by tx_ref.

    transactions.verifyByReference

  • View TimelineRead-only

    View transaction timeline.

    transactions.viewTimeline

Bills

  • Get CategoriesRead-only

    Get bill categories.

    bills.getCategories

  • List BillersRead-only

    List billers in a category.

    bills.listBillers

  • List ProductsRead-only

    List biller products.

    bills.listProducts

  • List RecurringRead-only

    List recurring bill payments.

    bills.listRecurring

  • Validate ItemRead-only

    Validate a bill item before payment.

    bills.validateItem

Payment Plans

  • CancelWrite

    Cancel a Flutterwave payment plan by ID.

    paymentPlans.cancel

Connect Flutterwave to Claude, ChatGPT or Cursor

  1. 1

    Connect Flutterwave in Corsair

    Add your Flutterwave API key once in Corsair. Corsair stores the credential encrypted and makes the Flutterwave API calls for your agent, so it never goes into a prompt or a config file. Connect Flutterwave

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs Flutterwave. On a ChatGPT personal plan, connect Flutterwave here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, Flutterwave's read and write operations run right away and its 2 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/flutterwave, add the Flutterwave plugin, and connect with an API key. Then call methods like corsair.flutterwave.api.banks.getBranches() from your app. Corsair keeps each tenant isolated.

Yes. Flutterwave requires an API key from your Flutterwave account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Flutterwave, GitHub, Notion, Stripe, and the rest. Trigger Flutterwave from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for payments api for accepting charges and payment links, and managing transfers, beneficiaries, subaccounts, virtual accounts, subscriptions, settlements, refunds, bills, banks, and wallet balances. Common builds include sync jobs, admin tooling, and agents that call Flutterwave APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Flutterwave API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/flutterwave in the open repo. When Flutterwave ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Flutterwave data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Flutterwave data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put Flutterwave on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 2 destructive Flutterwave operations. You can change a link's mode at hub.corsair.dev/me.