How to integrate Flutterwave MCP with Codex

Framework Integration Gradient
Flutterwave Logo
Codex Logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Flutterwave MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or app, whichever you prefer.

Composio removes the Authentication handling completely from you. We handle the entire integration lifecycle, and all you need to do is just copy the URL below, authenticate inside Codex, and start using it.

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Flutterwave MCP in Codex

Codex CLI

Run the command in your terminal.

Terminal

This will auto-redirect you to the Rube authentication page.

Rube authentication redirect page

Once you're authenticated, you will be able to access the tools.

Verify the installation by running:

codex mcp list

If you otherwise prefer to use config.toml, add the following URL to it. You can get the bearer token from rube.app → Use Rube → MCP URL → Generate token

[projects."/home/user/composio"]
trust_level = "untrusted"

[mcp_servers.rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex in VS Code

If you have installed Codex in VS Code.

Then: ⚙️ → MCP Settings → + Add servers → Streamable HTTP:

Add the Rube MCP URL: https://rube.app/mcp and the bearer token.

VS Code MCP Settings

To verify, click on the Open config.toml

Open config toml in Codex

Make sure it's there:

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
Codex App MCP Settings
  1. Restart and verify if it's there in .codex/config.toml
[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"
  1. Save, restart the extension, and start working.

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 & Triggers

Tools
Create BeneficiaryTool to create a new transfer beneficiary.
Create Bulk Virtual Account NumbersTool to create multiple virtual account numbers.
Create Payment LinkTool to create a hosted payment link.
Create Payment PlanTool to create a new payment plan.
Create SubaccountTool to create a new subaccount.
Create Virtual AccountTool to create a new virtual account number.
Delete BeneficiaryTool to delete a beneficiary by id.
Disable Payment LinkTool to disable a flutterwave payment link.
Fetch BeneficiaryTool to retrieve details of a specific beneficiary by id.
Fetch SubaccountTool to retrieve details of a specific subaccount by id.
Generate Transaction ReferenceTool to generate a unique transaction reference.
Get All SubscriptionsTool to retrieve all subscriptions, including cancelled ones.
Retrieve all transactionsTool to retrieve a list of all transactions with optional filters.
Get All Wallet BalancesTool to retrieve all wallet balances across currencies.
Get Balances per CurrencyTool to retrieve wallet balance for a specific currency.
Get Bill CategoriesTool to retrieve available bill categories.
Get Multiple Refund TransactionsTool to retrieve multiple refund transactions with optional filters.
Get Payment PlansTool to retrieve a list of all payment plans.
Get TransactionTool to retrieve details of a specific transaction by id.
Get Transaction FeeTool to retrieve the fee for a specific transaction.
Get Transfer FeeTool to retrieve the fee for initiating a transfer.
Initiate Mobile Money TanzaniaTool to initiate a mobile money payment in tanzania.
List All BeneficiariesTool to list all saved beneficiaries.
View Transaction TimelineTool to retrieve the event timeline for a transaction.

Conclusion

You've successfully integrated Flutterwave with Codex using Composio's Rube MCP server. Now you can interact with Flutterwave directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Flutterwave operations
  • Managed authentication through Composio's Rube
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Flutterwave operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Flutterwave MCP Agent with another framework

FAQ

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 Codex?

Yes, you can. Codex 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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.