How to integrate Flutterwave MCP with CrewAI

This guide walks you through connecting Flutterwave to CrewAI using the Composio tool router. By the end, you'll have a working Flutterwave agent that can create a payment link for a new order, generate virtual account numbers for customers, fetch details of a specific subaccount through natural language commands. This guide will help you understand how to give your CrewAI agent real control over a Flutterwave account through Composio's Flutterwave MCP server. Before we dive in, let's take a quick look at the key ideas and tools involved.

Get started for freeGet a demo
Flutterwave logoFlutterwave
Api Key

Flutterwave is a global payments platform enabling businesses to accept and send payments across Africa and beyond. Its robust APIs simplify cross-border transactions and financial operations.

53 Tools

Introduction

This guide walks you through connecting Flutterwave to CrewAI using the Composio tool router. By the end, you'll have a working Flutterwave agent that can create a payment link for a new order, generate virtual account numbers for customers, fetch details of a specific subaccount through natural language commands.

This guide will help you understand how to give your CrewAI agent real control over a Flutterwave account through Composio's Flutterwave MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

Also integrate Flutterwave with

OpenAI Agents SDKClaude Agent SDKClaude CodeClaude CoworkCodexOpenClawHermesCLIGoogle ADKLangChainVercel AI SDKMastra AILlamaIndex

TL;DR

Here's what you'll learn:
  • Get a Composio API key and configure your Flutterwave connection
  • Set up CrewAI with an MCP enabled agent
  • Create a Tool Router session or standalone MCP server for Flutterwave
  • Build a conversational loop where your agent can execute Flutterwave operations

What is CrewAI?

CrewAI is a powerful framework for building multi-agent AI systems. It provides primitives for defining agents with specific roles, creating tasks, and orchestrating workflows through crews.

Key features include:

  • Agent Roles: Define specialized agents with specific goals and backstories
  • Task Management: Create tasks with clear descriptions and expected outputs
  • Crew Orchestration: Combine agents and tasks into collaborative workflows
  • MCP Integration: Connect to external tools through Model Context Protocol

What is the Flutterwave MCP server, and what's possible with it?

The Flutterwave MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Flutterwave account. It provides structured and secure access to your payment infrastructure, so your agent can perform actions like creating payment links, managing beneficiaries, setting up virtual accounts, and handling subaccounts on your behalf.

  • Instant payment link creation: Let your agent generate hosted payment URLs for one-time or recurring transactions, making it easy to collect payments from customers.
  • Beneficiary management: Add, fetch, or remove transfer beneficiaries directly through your agent, streamlining the process of managing who receives your payouts.
  • Virtual account generation: Automatically create single or bulk virtual bank accounts for customers, enabling seamless and trackable bank transfers.
  • Subaccount setup and retrieval: Have your agent create, configure, or fetch subaccounts to manage split payments and disbursements for complex business needs.
  • Payment link control: Disable active payment links when necessary to prevent further transactions, ensuring you stay in control of your payment flows.

What is the Composio tool router, and how does it fit here?

What is Composio SDK?

Composio's Composio SDK helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Composio SDK

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Composio SDK works

The Composio SDK follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Step by step08 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Python 3.9 or higher
  • A Composio account and API key
  • A Flutterwave connection authorized in Composio
  • An OpenAI API key for the CrewAI LLM
  • Basic familiarity with Python
2

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.
3

Install dependencies

bash
pip install composio crewai crewai-tools[mcp] python-dotenv
What's happening:
  • composio connects your agent to Flutterwave via MCP
  • crewai provides Agent, Task, Crew, and LLM primitives
  • crewai-tools[mcp] includes MCP helpers
  • python-dotenv loads environment variables from .env
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
OPENAI_API_KEY=your_openai_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID scopes the session to your account
  • OPENAI_API_KEY lets CrewAI use your chosen OpenAI model
5

Import dependencies

python
import os
from composio import Composio
from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
import dotenv

dotenv.load_dotenv()

COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set")
What's happening:
  • CrewAI classes define agents and tasks, and run the workflow
  • MCPServerHTTP connects the agent to an MCP endpoint
  • Composio will give you a short lived Flutterwave MCP URL
6

Create a Composio Tool Router session for Flutterwave

python
composio_client = Composio(api_key=COMPOSIO_API_KEY)
session = composio_client.create(user_id=COMPOSIO_USER_ID, toolkits=["flutterwave"])

url = session.mcp.url
What's happening:
  • You create a Flutterwave only session through Composio
  • Composio returns an MCP HTTP URL that exposes Flutterwave tools
7

Initialize the MCP Server

python
server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users search the internet effectively",
        backstory="You are a helpful assistant with access to search tools.",
        tools=tools,
        verbose=False,
        max_iter=10,
    )
What's Happening:
  • Server Configuration: The code sets up connection parameters including the MCP server URL, streamable HTTP transport, and Composio API key authentication.
  • MCP Adapter Bridge: MCPServerAdapter acts as a context manager that converts Composio MCP tools into a CrewAI-compatible format.
  • Agent Setup: Creates a CrewAI Agent with a defined role (Search Assistant), goal (help with internet searches), and access to the MCP tools.
  • Configuration Options: The agent includes settings like verbose=False for clean output and max_iter=10 to prevent infinite loops.
  • Dynamic Tool Usage: Once created, the agent automatically accesses all Composio Search tools and decides when to use them based on user queries.
8

Create a CLI Chatloop and define the Crew

python
print("Chat started! Type 'exit' or 'quit' to end.\n")

conversation_context = ""

while True:
    user_input = input("You: ").strip()

    if user_input.lower() in ["exit", "quit", "bye"]:
        print("\nGoodbye!")
        break

    if not user_input:
        continue

    conversation_context += f"\nUser: {user_input}\n"
    print("\nAgent is thinking...\n")

    task = Task(
        description=(
            f"Conversation history:\n{conversation_context}\n\n"
            f"Current request: {user_input}"
        ),
        expected_output="A helpful response addressing the user's request",
        agent=agent,
    )

    crew = Crew(agents=[agent], tasks=[task], verbose=False)
    result = crew.kickoff()
    response = str(result)

    conversation_context += f"Agent: {response}\n"
    print(f"Agent: {response}\n")
What's Happening:
  • Interactive CLI Setup: The code creates an infinite loop that continuously prompts for user input and maintains the entire conversation history in a string variable.
  • Input Validation: Empty inputs are ignored to prevent processing blank messages and keep the conversation clean.
  • Context Building: Each user message is appended to the conversation context, which preserves the full dialogue history for better agent responses.
  • Dynamic Task Creation: For every user input, a new Task is created that includes both the full conversation history and the current request as context.
  • Crew Execution: A Crew is instantiated with the agent and task, then kicked off to process the request and generate a response.
  • Response Management: The agent's response is converted to a string, added to the conversation context, and displayed to the user, maintaining conversational continuity.

Complete Code

Here's the complete code to get you started with Flutterwave and CrewAI:

python
from crewai import Agent, Task, Crew, LLM
from crewai_tools import MCPServerAdapter
from composio import Composio
from dotenv import load_dotenv
import os

load_dotenv()

GOOGLE_API_KEY = os.getenv("GOOGLE_API_KEY")
COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY")
COMPOSIO_USER_ID = os.getenv("COMPOSIO_USER_ID")

if not GOOGLE_API_KEY:
    raise ValueError("GOOGLE_API_KEY is not set in the environment.")
if not COMPOSIO_API_KEY:
    raise ValueError("COMPOSIO_API_KEY is not set in the environment.")
if not COMPOSIO_USER_ID:
    raise ValueError("COMPOSIO_USER_ID is not set in the environment.")

# Initialize Composio and create a session
composio = Composio(api_key=COMPOSIO_API_KEY)
session = composio.create(
    user_id=COMPOSIO_USER_ID,
    toolkits=["flutterwave"],
)
url = session.mcp.url

# Configure LLM
llm = LLM(
    model="gpt-5",
    api_key=os.getenv("OPENAI_API_KEY"),
)

server_params = {
    "url": url,
    "transport": "streamable-http",
    "headers": {"x-api-key": COMPOSIO_API_KEY},
}

with MCPServerAdapter(server_params) as tools:
    agent = Agent(
        role="Search Assistant",
        goal="Help users with internet searches",
        backstory="You are an expert assistant with access to Composio Search tools.",
        tools=tools,
        llm=llm,
        verbose=False,
        max_iter=10,
    )

    print("Chat started! Type 'exit' or 'quit' to end.\n")

    conversation_context = ""

    while True:
        user_input = input("You: ").strip()

        if user_input.lower() in ["exit", "quit", "bye"]:
            print("\nGoodbye!")
            break

        if not user_input:
            continue

        conversation_context += f"\nUser: {user_input}\n"
        print("\nAgent is thinking...\n")

        task = Task(
            description=(
                f"Conversation history:\n{conversation_context}\n\n"
                f"Current request: {user_input}"
            ),
            expected_output="A helpful response addressing the user's request",
            agent=agent,
        )

        crew = Crew(agents=[agent], tasks=[task], verbose=False)
        result = crew.kickoff()
        response = str(result)

        conversation_context += f"Agent: {response}\n"
        print(f"Agent: {response}\n")

Conclusion

You now have a CrewAI agent connected to Flutterwave through Composio's Tool Router. The agent can perform Flutterwave operations through natural language commands.

Next steps:

  • Add role-specific instructions to customize agent behavior
  • Plug in more toolkits for multi-app workflows
  • Chain tasks for complex multi-step operations
TOOLS

Supported Tools

Every Flutterwave action and event your agent gets out of the box.

Cancel Payment Plan

Tool to cancel a payment plan.

Create Beneficiary

Tool to create a new transfer beneficiary.

Create Bulk Tokenized Charge

Tool to create a bulk tokenized charge batch for charging multiple previously tokenized cards.

Create Bulk Virtual Account Numbers

Tool to create multiple virtual account numbers.

Create Payment Link

Tool to create a hosted payment link.

Create Payment Plan

Tool to create a new payment plan.

Create Refund

Tool to create a refund for a transaction.

Create Subaccount

Tool to create a new subaccount.

Create Virtual Account

Tool to create a new virtual account number.

Delete Beneficiary

Tool to delete a beneficiary by ID.

Delete Subaccount

Tool to delete a subaccount by ID.

Disable Payment Link

Tool to disable a Flutterwave payment link.

Fetch Beneficiary

Tool to retrieve details of a specific beneficiary by ID.

Fetch Subaccount

Tool to retrieve details of a specific subaccount by ID.

Generate Transaction Reference

Tool to generate a unique transaction reference.

Get All Subscriptions

Tool to retrieve all subscriptions, including cancelled ones.

Retrieve all transactions

Tool to retrieve a list of all transactions with optional filters.

Get All Wallet Balances

Tool to retrieve all wallet balances across currencies.

Get Balances per Currency

Tool to retrieve wallet balance for a specific currency.

Get Bank Branches

Tool to retrieve branch codes for a specific bank.

Get Banks by Country

Tool to retrieve all banks in a specified country.

Get Bill Categories

Tool to retrieve available bill categories.

Get Bulk Tokenized Charge Status

Tool to retrieve the status of a bulk tokenized charge operation by ID.

Get Bulk Virtual Account

Tool to fetch bulk virtual account details using batch ID.

Get Multiple Refund Transactions

Tool to retrieve multiple refund transactions with optional filters.

Get Payment Plan

Tool to retrieve details of a specific payment plan by ID.

Get Payment Plans

Tool to retrieve a list of all payment plans.

Get Refund

Tool to retrieve details of a specific refund by ID.

Get Transaction

Tool to retrieve details of a specific transaction by ID.

Get Transaction Fee

Tool to retrieve the fee for a specific transaction.

Get Transfer Fee

Tool to retrieve the fee for initiating a transfer.

Get Transfer Rates

Tool to retrieve exchange rates for transfers between currencies.

Get Virtual Account Number

Tool to fetch details of a virtual account number by order reference.

Get Wallet Statement

Tool to retrieve wallet balance history with optional filters.

Initiate BVN Verification

Tool to initiate BVN verification consent.

Initiate Mobile Money Tanzania

Tool to initiate a mobile money payment in Tanzania.

List All Beneficiaries

Tool to list all saved beneficiaries.

List Biller Products

Tool to retrieve all products available under a specific biller.

List Billers

Tool to retrieve available billers.

List Chargebacks

Tool to retrieve a list of chargebacks with optional filtering by Flutterwave reference.

List Payout Subaccount Refunds

Tool to list all payout subaccount refunds with pagination support.

List Payout Subaccounts

Tool to list all payout subaccounts.

List Recurring Bills

Tool to retrieve all recurring bill payments.

List all settlements

Tool to retrieve all settlements with optional filters.

List All Subaccounts

Tool to fetch all collection subaccounts.

List Transfers

Tool to fetch a list of bulk transfers from your Flutterwave account.

Resolve Bank Account

Tool to verify and resolve bank account details.

Resolve Card BIN

Tool to resolve and retrieve card BIN information from Flutterwave.

Update Payment Plan

Tool to update an existing payment plan.

Update Subaccount

Tool to update an existing subaccount.

Validate Bill Item

Tool to validate a bill service before payment.

Verify Transaction by Reference

Tool to verify a transaction using its transaction reference.

View Transaction Timeline

Tool to retrieve the event timeline for a transaction.

FRAMEWORKS

How to build Flutterwave MCP Agent with another framework

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Flutterwave MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Flutterwave MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Flutterwave MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Flutterwave MCP with Claude Cowork

Codex logo

Codex

Use Flutterwave MCP with Codex

OpenClaw logo

OpenClaw

Use Flutterwave MCP with OpenClaw

Hermes logo

Hermes

Use Flutterwave MCP with Hermes

CLI logo

CLI

Use Flutterwave MCP with CLI

Google ADK logo

Google ADK

Use Flutterwave MCP with Google ADK

LangChain logo

LangChain

Use Flutterwave MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Flutterwave MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Flutterwave MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Flutterwave MCP with LlamaIndex

FAQ

Frequently asked questions

With a standalone Flutterwave MCP server, the agents and LLMs can only access a fixed set of Flutterwave tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Flutterwave and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. CrewAI fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Flutterwave tools.

Yes, absolutely. You can configure which Flutterwave scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Flutterwave data and credentials are handled as safely as possible.

Start with Flutterwave.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Flutterwave tool your agent needs.Free to start.

Start building
Customer stories

Teams ship real agents on Composio

GET STARTED FOR FREEBOOK A DEMO
agent.aiZoomLettaGleanHubSpotAWSWabi

Karan skipped his own birthday party to fix our critical issue. It was 10pm and he diverted his Waymo to help us instead. This really sets the bar — it shows the commitment you need when users rely on your software.

Harsha Gaddipati
Harsha Gaddipati
Co-founder, Slashy

A lot of students tell us that the moment their connected tools start talking to each other inside Opennote feels almost magical. The agent just knows them, and it's immensely helped keep new users on the platform.

Abhi Arya
Abhi Arya
Co-founder, Opennote

We chose Composio over Pipedream because it delivered depth where it mattered — niche tools and tricky edge cases other platforms simply ignored. That gave us confidence to scale without compromising.

Nirman Dave
Nirman Dave
CEO, Zams

As a solo builder, shipping fast is life or death. The only way I can outcompete incumbents is by outmanoeuvring them. Getting bogged down managing agent auth would have been a death sentence.

Ryan Yu
Ryan Yu
Founder, Extra Thursday

Before Composio, adding tool integrations was slow and resource-intensive. Each one could take weeks of engineering time, and maintaining them meant constantly keeping up with API changes.

Tomisin Jenrola
Tomisin Jenrola
Founder & CEO, SwarmZero

With hands-on help from their founder, we integrated Gmail and Google Drive in just 30 minutes. This level of personal support and commitment is exactly what startups should strive for.

Jerome Leclanche
Jerome Leclanche
Co-Founder, Ingram Technologies