Skip to content

Flutterwave MCP connector

The Flutterwave connector brings customers, charges, payment methods, wallet balances and transfers into Claude, ChatGPT, Cursor and any MCP client, so your team can look up a payment or start a payout while signed in as themselves.

  • How it connects. App credentials. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Flutterwave to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Flutterwave once

  1. Open Connections, choose Add connection, and pick Flutterwave.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste your Flutterwave app credentials. Flutterwave authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

flutterwave
Flutterwave
Airwallex
Cashfree Payments
ChargeDesk
Chimoney
Circle
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Flutterwave MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Flutterwave MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Flutterwave MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Flutterwave to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Flutterwave through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Finance

    Check a payment before you reply

    Ask for a customer's recent Flutterwave charges by name or email and see whether the payment went through, how much was collected and when, before writing back.

  • Support

    Find the customer behind a failed charge

    Search Flutterwave customers from a support ticket, pull the charge in question and update the customer's details if the email or phone number on file was wrong.

  • Treasury

    Know what is in every wallet

    Read Flutterwave wallet balances across currencies and pull a statement for the period, so the morning cash position is a question rather than a spreadsheet.

  • Operations

    Send a payout without the bank form

    Resolve the recipient's account, pick the right bank or branch from the Flutterwave list, and create the transfer, then check its status a few minutes later.

  • Sales

    Set up a new customer to bill

    Create the Flutterwave customer when a deal closes, add their payment method and raise the first charge from the same conversation.

  • Finance

    Reconcile transfers at month end

    List the Flutterwave transfers that went out this month, pull any single transfer by ID and match it against the wallet statement without opening the dashboard.

Try asking

  • “Show Flutterwave charges created this week by payment method.”
  • “Find the Flutterwave customer for this email address.”
  • “List failed charges over 50,000 from the last 30 days.”

See all 57 Flutterwave tools below

Compare

Elaichi vs Zapier MCP vs Composio for Flutterwave

All three can connect Flutterwave to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Flutterwave, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Flutterwave tools Allow or restrict single Flutterwave tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Flutterwave call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Flutterwave tools for your AI agents

57 tools are ready to call through Elaichi's MCP endpoint the moment you connect Flutterwave, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Flutterwave gets you

6 screens from the product, each doing one job for your Flutterwave account.

The agent

Ask about charges, read the answer.

Plain language questions return live Flutterwave customers, charges and payment methods.

  • customers
  • charges
  • payment methods
  • mobile networks

Ask Elaichi to work across your apps.

Show Flutterwave charges created this week by payment method.

Find the Flutterwave customer for this email address.

List failed charges over 50,000 from the last 30 days.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor share one endpoint.

Every client reaches Flutterwave through one org endpoint, no SDK, no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

57 Flutterwave tools are ready to call.

Customers, charges, payment methods and mobile networks, with no custom code written.

  • List all Flutterwave customers
  • Create a Flutterwave customer
  • Get single Flutterwave customer by ID
  • Flutterwave customers search
ElaichiTools
Tool Action Description
List all Flutterwave customers List List Flutterwave customers. Returns: id, email, address, name, phone, meta, created_datetime. Max 10 records per page.
Create a Flutterwave customer Create Create a new Flutterwave customer. Returns the created customer object including id, email, address, name, phone, and created_datetime.
Get single Flutterwave customer by ID Get Retrieve a single Flutterwave customer by id. Returns the customer object including id, email, name, phone, address, meta, and created_datetime. Required: id.
Flutterwave customers search Search Search Flutterwave customers. Returns: id, email, address, name, phone, meta, created_datetime.
Update a Flutterwave customer by ID Update Update a Flutterwave customer by id. Returns the updated customer object including id, email, address, name, phone, and created_datetime. Required: id.

Toolboxes

Each team gets its own toolbox.

Finance, Support and Engineering each open a Flutterwave toolbox scoped to their work.

  • Finance
  • Support
  • Engineering
  • Revenue Operations
ElaichiToolboxes
Name Source template Tools Created

Finance toolbox

Flutterwave · charges and settlements

Flutterwave starter 18 Mar 4, 2026

Support toolbox

Flutterwave · customers and refunds

— 9 Mar 2, 2026

Engineering toolbox

Flutterwave · payment methods and charge creation

— 24 Feb 27, 2026

Revenue Operations toolbox

Flutterwave · charge reporting and reconciliation

Flutterwave starter 6 Feb 19, 2026

Risk toolbox

Flutterwave · failed charges and reviews

— 31 Jan 30, 2026

Growth toolbox

Flutterwave · customers and mobile networks

— 12 Jan 22, 2026

Shared connections

Teammates charge without holding a secret key.

See who connected each Flutterwave account and how many teams and members use it.

  • Finance NG
  • Support
  • Engineering Sandbox
  • Risk Review
ElaichiConnections
Connection Scope Status Access
FL

Flutterwave (Finance NG)

Connected by Emily Carter

Personal • Active 1 team · 6 members
FL

Flutterwave (Support)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
FL

Flutterwave (Engineering Sandbox)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
FL

Flutterwave (Risk Review)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
FL

Flutterwave (Revenue Operations)

Connected by Ryan Hayes

Personal • Active Not shared
FL

Flutterwave (Growth Africa)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Flutterwave call has a name on it.

When, who, what happened, type and resource, appended for each charge and customer.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Flutterwave Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Flutterwave Customers Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Flutterwave Customers List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires, a digest ships.

Fetch Flutterwave charges, group them, draft a digest, approve, then post it back.

Flutterwave digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch customers

    Flutterwave

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Flutterwave

    Queued

Collections and dashboards

Charge numbers arrive before anyone asks.

Four metrics, 14 days of Flutterwave records created, split by team, refreshed on schedule.

Flutterwave health

Refreshed 4 minutes ago · every 15 minutes · from the customers collection

Live

Customers

1,284 ↓ 12%

Charges

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Customers created

Last 14 days

By team

Share of activity

Finance NG 34%

Support 27%

Engineering Sandbox 21%

Risk Review 18%

FAQ

Frequently asked questions

How do I connect Flutterwave to Claude?

First connect Flutterwave in Elaichi by pasting the app credentials from your Flutterwave dashboard; there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the Elaichi endpoint https://api.elaichi.ai/mcp. Sign in to Elaichi as yourself when Claude asks, and Flutterwave customers, charges, wallets and transfers are available in the chat.

Does Flutterwave work with ChatGPT and Cursor as well as Claude?

Yes. Once Flutterwave is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Flutterwave once and every client you use picks it up.

What can an AI agent actually do with my Flutterwave data?

It can search Flutterwave customers, create or update a customer, list and create charges and payment methods, read wallet balances and statements, look up banks and branches, resolve an account number and create or check transfers. In practice that means asking whether a customer paid, what a wallet holds today or where a payout is. Flutterwave exposes many actions, so short, specific asks like "show this week's transfers" work better than long paragraphs.

Does connecting Flutterwave give the AI access to our whole account and balances?

No. Everything the AI does in Flutterwave runs through the connection your organization set up and the Elaichi account of the person asking, so it can reach only what those Flutterwave credentials already reach. Elaichi can narrow that further with roles and restrictions, and it never widens it beyond what Flutterwave itself allows.

Can my team share one Flutterwave connection?

Yes. One person connects Flutterwave in Elaichi and shares the connection with a team, and nobody else ever handles the credentials. Each teammate still signs in to Elaichi as themselves, so every charge, customer change or transfer in the audit log names the person who did it.

Can I stop an agent from moving money or changing things in Flutterwave?

Yes. Restrictions in Elaichi work per action, so you can allow reading Flutterwave customers, charges and balances while blocking creating transfers or updating charges. A blocked action is never shown to Claude, ChatGPT or any other client at all, so no prompt, however worded, can reach it.

What happens to a Flutterwave connection when someone leaves?

Offboarding that person in Elaichi ends their access to Flutterwave at once, in every client they used. A shared Flutterwave connection keeps working for everyone else on the team. If you later want Flutterwave gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client together.

Does the Flutterwave MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Flutterwave is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Flutterwave?

Yes. Both let Claude, ChatGPT or Cursor use Flutterwave. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Flutterwave call.

How is Elaichi different from Composio for Flutterwave?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Flutterwave: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Flutterwave in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.