# How to integrate Flutterwave MCP with Autogen ```json { "title": "How to integrate Flutterwave MCP with Autogen", "toolkit": "Flutterwave", "toolkit_slug": "flutterwave", "framework": "AutoGen", "framework_slug": "autogen", "url": "https://composio.dev/toolkits/flutterwave/framework/autogen", "markdown_url": "https://composio.dev/toolkits/flutterwave/framework/autogen.md", "updated_at": "2026-05-06T08:12:08.010Z" } ``` ## Introduction This guide walks you through connecting Flutterwave to AutoGen 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 AutoGen 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 SDK](https://composio.dev/toolkits/flutterwave/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/flutterwave/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/flutterwave/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/flutterwave/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/flutterwave/framework/codex) - [OpenClaw](https://composio.dev/toolkits/flutterwave/framework/openclaw) - [Hermes](https://composio.dev/toolkits/flutterwave/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/flutterwave/framework/cli) - [Google ADK](https://composio.dev/toolkits/flutterwave/framework/google-adk) - [LangChain](https://composio.dev/toolkits/flutterwave/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/flutterwave/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/flutterwave/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/flutterwave/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/flutterwave/framework/crew-ai) ## TL;DR Here's what you'll learn: - Get and set up your OpenAI and Composio API keys - Install the required dependencies for Autogen and Composio - Initialize Composio and create a Tool Router session for Flutterwave - Wire that MCP URL into Autogen using McpWorkbench and StreamableHttpServerParams - Configure an Autogen AssistantAgent that can call Flutterwave tools - Run a live chat loop where you ask the agent to perform Flutterwave operations ## What is AutoGen? Autogen is a framework for building multi-agent conversational AI systems from Microsoft. It enables you to create agents that can collaborate, use tools, and maintain complex workflows. Key features include: - Multi-Agent Systems: Build collaborative agent workflows - MCP Workbench: Native support for Model Context Protocol tools - Streaming HTTP: Connect to external services through streamable HTTP - AssistantAgent: Pre-built agent class for tool-using assistants ## 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. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `FLUTTERWAVE_CREATE_BENEFICIARY` | Create Beneficiary | Tool to create a new transfer beneficiary. use when you need to add a beneficiary before making a transfer. | | `FLUTTERWAVE_CREATE_BULK_VIRTUAL_ACCOUNT_NUMBERS` | Create Bulk Virtual Account Numbers | Tool to create multiple virtual account numbers. use when you need to generate multiple static virtual accounts for customers in a single request. | | `FLUTTERWAVE_CREATE_PAYMENT_LINK` | Create Payment Link | Tool to create a hosted payment link. use when you need a shareable payment url for one-time transactions. | | `FLUTTERWAVE_CREATE_PAYMENT_PLAN` | Create Payment Plan | Tool to create a new payment plan. use after confirming plan and customer details. | | `FLUTTERWAVE_CREATE_SUBACCOUNT` | Create Subaccount | Tool to create a new subaccount. use when you need to configure split disbursement accounts. | | `FLUTTERWAVE_CREATE_VIRTUAL_ACCOUNT` | Create Virtual Account | Tool to create a new virtual account number. use after confirming customer details when assigning a unique account for bank transfers. | | `FLUTTERWAVE_DELETE_BENEFICIARY` | Delete Beneficiary | Tool to delete a beneficiary by id. use when you need to remove a saved transfer beneficiary by its unique id after confirming the id. | | `FLUTTERWAVE_DISABLE_PAYMENT_LINK` | Disable Payment Link | Tool to disable a flutterwave payment link. use when you need to prevent further payments from an existing link after confirming the link is valid. | | `FLUTTERWAVE_FETCH_BENEFICIARY` | Fetch Beneficiary | Tool to retrieve details of a specific beneficiary by id. use after obtaining a beneficiary id to fetch its full details from flutterwave. | | `FLUTTERWAVE_FETCH_SUBACCOUNT` | Fetch Subaccount | Tool to retrieve details of a specific subaccount by id. use when you need full subaccount info after creating or updating splits. | | `FLUTTERWAVE_GENERATE_TRANSACTION_REFERENCE` | Generate Transaction Reference | Tool to generate a unique transaction reference. use when initiating a new flutterwave transaction requires a unique reference to prevent duplication. | | `FLUTTERWAVE_GET_ALL_SUBSCRIPTIONS` | Get All Subscriptions | Tool to retrieve all subscriptions, including cancelled ones. use when you need a comprehensive list of subscription records for auditing or reporting. | | `FLUTTERWAVE_GET_ALL_TRANSACTIONS` | Retrieve all transactions | Tool to retrieve a list of all transactions with optional filters. use when you need to paginate or filter transaction history after confirming valid api credentials. | | `FLUTTERWAVE_GET_ALL_WALLET_BALANCES` | Get All Wallet Balances | Tool to retrieve all wallet balances across currencies. use when reconciling balances after authentication. | | `FLUTTERWAVE_GET_BALANCES_PER_CURRENCY` | Get Balances per Currency | Tool to retrieve wallet balance for a specific currency. use after transactions to confirm available and ledger balances in a given currency. | | `FLUTTERWAVE_GET_BILL_CATEGORIES` | Get Bill Categories | Tool to retrieve available bill categories. use after authenticating to flutterwave to display bill payment options to users. | | `FLUTTERWAVE_GET_MULTIPLE_REFUND_TRANSACTIONS` | Get Multiple Refund Transactions | Tool to retrieve multiple refund transactions with optional filters. use when you need to fetch paginated refund data after confirming valid api credentials. | | `FLUTTERWAVE_GET_PAYMENT_PLANS` | Get Payment Plans | Tool to retrieve a list of all payment plans. use when you need to fetch and present your account’s configured billing plans. | | `FLUTTERWAVE_GET_TRANSACTION` | Get Transaction | Tool to retrieve details of a specific transaction by id. use after obtaining the transaction id to fetch its details from flutterwave. | | `FLUTTERWAVE_GET_TRANSACTION_FEE` | Get Transaction Fee | Tool to retrieve the fee for a specific transaction. use when you need to calculate the total charge including fees before initiating the transaction. | | `FLUTTERWAVE_GET_TRANSFER_FEE` | Get Transfer Fee | Tool to retrieve the fee for initiating a transfer. use when you need to estimate transfer costs before creating a transfer. example: "calculate the fee for transferring ngn 5000 to an account." | | `FLUTTERWAVE_INITIATE_MOBILE_MONEY_TANZANIA` | Initiate Mobile Money Tanzania | Tool to initiate a mobile money payment in tanzania. use after collecting customer details to charge via tanzanian mobile money networks. | | `FLUTTERWAVE_LIST_ALL_BENEFICIARIES` | List All Beneficiaries | Tool to list all saved beneficiaries. use when you need to retrieve all transfer beneficiaries associated with your account. | | `FLUTTERWAVE_VIEW_TRANSACTION_TIMELINE` | View Transaction Timeline | Tool to retrieve the event timeline for a transaction. use after obtaining the transaction id to audit or track the sequence of events. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Flutterwave MCP server is an implementation of the Model Context Protocol that connects your AI agents and assistants directly to Flutterwave. Instead of manually wiring Flutterwave APIs, OAuth, and scopes yourself, you get a structured, tool-based interface that an LLM can call safely. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites You will need: - A Composio API key - An OpenAI API key (used by Autogen's OpenAIChatCompletionClient) - A Flutterwave account you can connect to Composio - Some basic familiarity with Autogen and Python async ### 1. Getting API Keys for OpenAI and Composio OpenAI API Key - Go to the [OpenAI dashboard](https://platform.openai.com/settings/organization/api-keys) 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](https://dashboard.composio.dev?utm_source=toolkits&utm_medium=framework_docs). - Navigate to your API settings and generate a new API key. - Store this key securely as you'll need it for authentication. ### 2. Install dependencies Install Composio, Autogen extensions, and dotenv. What's happening: - composio connects your agent to Flutterwave via MCP - autogen-agentchat provides the AssistantAgent class - autogen-ext-openai provides the OpenAI model client - autogen-ext-tools provides MCP workbench support ```bash pip install composio python-dotenv pip install autogen-agentchat autogen-ext-openai autogen-ext-tools ``` ### 3. Set up environment variables Create a .env file in your project folder. What's happening: - COMPOSIO_API_KEY is required to talk to Composio - OPENAI_API_KEY is used by Autogen's OpenAI client - USER_ID is how Composio identifies which user's Flutterwave connections to use ```bash COMPOSIO_API_KEY=your-composio-api-key OPENAI_API_KEY=your-openai-api-key USER_ID=your-user-identifier@example.com ``` ### 4. Import dependencies and create Tool Router session What's happening: - load_dotenv() reads your .env file - Composio(api_key=...) initializes the SDK - create(...) creates a Tool Router session that exposes Flutterwave tools - session.mcp.url is the MCP endpoint that Autogen will connect to ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Flutterwave session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["flutterwave"] ) url = session.mcp.url ``` ### 5. Configure MCP parameters for Autogen Autogen expects parameters describing how to talk to the MCP server. That is what StreamableHttpServerParams is for. What's happening: - url points to the Tool Router MCP endpoint from Composio - timeout is the HTTP timeout for requests - sse_read_timeout controls how long to wait when streaming responses - terminate_on_close=True cleans up the MCP server process when the workbench is closed ```python # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) ``` ### 6. Create the model client and agent What's happening: - OpenAIChatCompletionClient wraps the OpenAI model for Autogen - McpWorkbench connects the agent to the MCP tools - AssistantAgent is configured with the Flutterwave tools from the workbench ```python # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Flutterwave assistant agent with MCP tools agent = AssistantAgent( name="flutterwave_assistant", description="An AI assistant that helps with Flutterwave operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) ``` ### 7. Run the interactive chat loop What's happening: - The script prompts you in a loop with You: - Autogen passes your input to the model, which decides which Flutterwave tools to call via MCP - agent.run_stream(...) yields streaming messages as the agent thinks and calls tools - Typing exit, quit, or bye ends the loop ```python print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Flutterwave related question or task to the agent.\n") # Conversation loop while True: user_input = input("You: ").strip() if user_input.lower() in ["exit", "quit", "bye"]: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, "content") and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") ``` ## Complete Code ```python import asyncio import os from dotenv import load_dotenv from composio import Composio from autogen_agentchat.agents import AssistantAgent from autogen_ext.models.openai import OpenAIChatCompletionClient from autogen_ext.tools.mcp import McpWorkbench, StreamableHttpServerParams load_dotenv() async def main(): # Initialize Composio and create a Flutterwave session composio = Composio(api_key=os.getenv("COMPOSIO_API_KEY")) session = composio.create( user_id=os.getenv("USER_ID"), toolkits=["flutterwave"] ) url = session.mcp.url # Configure MCP server parameters for Streamable HTTP server_params = StreamableHttpServerParams( url=url, timeout=30.0, sse_read_timeout=300.0, terminate_on_close=True, headers={"x-api-key": os.getenv("COMPOSIO_API_KEY")} ) # Create model client model_client = OpenAIChatCompletionClient( model="gpt-5", api_key=os.getenv("OPENAI_API_KEY") ) # Use McpWorkbench as context manager async with McpWorkbench(server_params) as workbench: # Create Flutterwave assistant agent with MCP tools agent = AssistantAgent( name="flutterwave_assistant", description="An AI assistant that helps with Flutterwave operations.", model_client=model_client, workbench=workbench, model_client_stream=True, max_tool_iterations=10 ) print("Chat started! Type 'exit' or 'quit' to end the conversation.\n") print("Ask any Flutterwave related question or task to the agent.\n") # Conversation loop while True: user_input = input("You: ").strip() if user_input.lower() in ['exit', 'quit', 'bye']: print("\nGoodbye!") break if not user_input: continue print("\nAgent is thinking...\n") # Run the agent with streaming try: response_text = "" async for message in agent.run_stream(task=user_input): if hasattr(message, 'content') and message.content: response_text = message.content # Print the final response if response_text: print(f"Agent: {response_text}\n") else: print("Agent: I encountered an issue processing your request.\n") except Exception as e: print(f"Agent: Sorry, I encountered an error: {str(e)}\n") if __name__ == "__main__": asyncio.run(main()) ``` ## Conclusion You now have an Autogen assistant wired into Flutterwave through Composio's Tool Router and MCP. From here you can: - Add more toolkits to the toolkits list, for example notion or hubspot - Refine the agent description to point it at specific workflows - Wrap this script behind a UI, Slack bot, or internal tool Once the pattern is clear for Flutterwave, you can reuse the same structure for other MCP-enabled apps with minimal code changes. ## How to build Flutterwave MCP Agent with another framework - [OpenAI Agents SDK](https://composio.dev/toolkits/flutterwave/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/flutterwave/framework/claude-agents-sdk) - [Claude Code](https://composio.dev/toolkits/flutterwave/framework/claude-code) - [Claude Cowork](https://composio.dev/toolkits/flutterwave/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/flutterwave/framework/codex) - [OpenClaw](https://composio.dev/toolkits/flutterwave/framework/openclaw) - [Hermes](https://composio.dev/toolkits/flutterwave/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/flutterwave/framework/cli) - [Google ADK](https://composio.dev/toolkits/flutterwave/framework/google-adk) - [LangChain](https://composio.dev/toolkits/flutterwave/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/flutterwave/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/flutterwave/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/flutterwave/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/flutterwave/framework/crew-ai) ## Related Toolkits - [Stripe](https://composio.dev/toolkits/stripe) - Stripe is a global online payments platform offering APIs for managing payments, customers, and subscriptions. Trusted by businesses for secure, efficient, and scalable payment processing worldwide. - [Alpha vantage](https://composio.dev/toolkits/alpha_vantage) - Alpha Vantage is a financial data platform offering real-time and historical stock market APIs. Get instant, reliable access to equities, forex, and technical analysis data for smarter trading decisions. - [Altoviz](https://composio.dev/toolkits/altoviz) - Altoviz is a cloud-based billing and invoicing platform for businesses. It streamlines online payments, expense tracking, and customizable invoice management. - [Benzinga](https://composio.dev/toolkits/benzinga) - Benzinga provides real-time financial news and data APIs for market coverage. It helps you track breaking news and actionable market insights instantly. - [Brex](https://composio.dev/toolkits/brex) - Brex provides corporate credit cards and spend management tailored for startups and tech businesses. It helps optimize company cash flow, streamline accounting, and accelerate business growth. - [Chaser](https://composio.dev/toolkits/chaser) - Chaser is accounts receivable automation software that sends invoice reminders and helps businesses get paid faster. It streamlines the collections process to save time and improve cash flow. - [Clientary](https://composio.dev/toolkits/clientary) - Clientary is a platform for managing clients, invoices, projects, proposals, and more. It streamlines client work and saves you serious admin time. - [Coinbase](https://composio.dev/toolkits/coinbase) - Coinbase is a platform for buying, selling, and storing cryptocurrency. It makes exchanging and managing crypto simple and secure for everyone. - [Coinranking](https://composio.dev/toolkits/coinranking) - Coinranking is a comprehensive cryptocurrency market data platform offering access to real-time coin prices, market caps, and historical data. Get accurate, up-to-date stats for thousands of digital assets in one place. - [Coupa](https://composio.dev/toolkits/coupa) - Coupa is a business spend management platform for procurement, invoicing, and expenses. It helps organizations streamline purchasing, control costs, and gain complete visibility over financial operations. - [CurrencyScoop](https://composio.dev/toolkits/currencyscoop) - CurrencyScoop is a developer-friendly API for real-time and historical currency exchange rates. Easily access fiat and crypto data for smart, up-to-date financial applications. - [Daffy](https://composio.dev/toolkits/daffy) - Daffy is a modern charitable giving platform with a donor-advised fund. Easily set aside funds, grow them tax-free, and donate to over 1.7 million U.S. charities. - [Eagle doc](https://composio.dev/toolkits/eagle_doc) - Eagle doc is an AI-powered OCR API for invoices and receipts. It delivers fast, reliable, and accurate document data extraction for seamless automation. - [Elorus](https://composio.dev/toolkits/elorus) - Elorus is an online invoicing and time-tracking software for freelancers and small businesses. Easily manage finances, bill clients, and track work in one place. - [Eodhd apis](https://composio.dev/toolkits/eodhd_apis) - Eodhd apis delivers comprehensive financial data, including live and historical stock prices, via robust APIs. Easily access reliable, up-to-date market insights to power your apps, dashboards, and analytics. - [Fidel api](https://composio.dev/toolkits/fidel_api) - Fidel api is a secure platform for linking payment cards to web and mobile apps. It enables real-time card transaction monitoring and event-based automation for businesses. - [Finage](https://composio.dev/toolkits/finage) - Finage is a secure API platform delivering real-time and historical financial data for stocks, forex, crypto, indices, and commodities. It empowers developers and businesses to access, analyze, and act on market data instantly. - [Finmei](https://composio.dev/toolkits/finmei) - Finmei is an invoicing tool that simplifies billing, invoice management, and expense tracking. Ideal for automating and organizing your business finances in one place. - [Fixer](https://composio.dev/toolkits/fixer) - Fixer is a currency data API offering real-time and historical exchange rates for 170 currencies. Instantly access accurate, up-to-date forex data for your applications and workflows. - [Fixer io](https://composio.dev/toolkits/fixer_io) - Fixer.io is a lightweight API for real-time and historical foreign exchange rates. It makes global currency conversion fast, accurate, and hassle-free. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Flutterwave MCP? 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. ### Can I use Tool Router MCP with Autogen? Yes, you can. Autogen 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. ### Can I manage the permissions and scopes for Flutterwave while using Tool Router? 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. ### How safe is my data with Composio Tool Router? 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. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)