home / mcp / flutterwave mcp server
MCP Server to interact with flutterwave
Configuration
View docs{
"mcpServers": {
"bajoski34-mcp-flutterwave": {
"command": "mcp-flutterwave",
"args": [
"--tools=create_checkout,disable_checkout,read_transaction,resend_transaction_webhook"
],
"env": {
"FLW_SECRET_KEY": "YOUR_SECRET_KEY"
}
}
}
}You enable AI assistants to interact with Flutterwave through the MCP server, offering transaction confirmation, failed webhook handling, and rich UI-enhanced responses to streamline payments and transfers within your MCP client.
You run the MCP server in a local or remote environment and connect it to your MCP client. Once active, you can ask questions about transactions, generate payment links, retry failed transactions, view transaction timelines, and manage beneficiaries and transfers. The server returns both textual responses and rich UI components that illustrate transaction details, payment links, and transfer data in an intuitive, branded UI.
Prerequisites: you need Node.js and npm installed on your machine.
Install the MCP Flutterwave package globally.
npm install -g mcp-flutterwaveObtain your Flutterwave secret key from your Flutterwave dashboard under Settings > API Keys. You will configure this key in your MCP client configuration to authorize requests.
Configure your Claude Desktop integration to load the Flutterwave MCP server with the appropriate tools and the secret key.
Starting the server can be done either from a global installation or from a local build. Choose one of the following configurations and place them in your Claude Desktop configuration file.
{
"mcpServers": {
"flutterwave": {
"command": "mcp-flutterwave",
"args": [
"--tools=create_checkout,disable_checkout,read_transaction,resend_transaction_webhook"
],
"env": {
"FLW_SECRET_KEY": "YOUR_SECRET_KEY"
}
}
}
}{
"mcpServers": {
"flutterwave": {
"command": "node",
"args": [
"/path/to/mcp-flutterwave/build/index.js",
"--tools=create_checkout,disable_checkout,read_transaction,resend_transaction_webhook"
],
"env": {
"FLW_SECRET_KEY": "YOUR_SECRET_KEY"
}
}
}
}Use the create_checkout tool to generate payment links for customers. Use get-transactions and get-transaction-timeline to analyze transaction histories. Retry failed transactions with retry-transaction and resend failed webhooks with resent-failed-webhook when needed. Manage beneficiaries and transfers with create-transfer, get-transfers, get-beneficiaries, and create-beneficiary to streamline payouts.
Keep your Flutterwave secret key secure. Do not share it in public configurations. Rotate keys periodically and use environment variables to inject secrets at runtime. Restrict server access to trusted MCP clients and monitor tool usage for unusual activity.
If you encounter issues with a webhook or a transaction not completing, check the transaction timeline and webhook delivery logs. Ensure the secret key is correctly configured in your MCP client and that the required tools are enabled in the server command line.
The server ships with branded UI components that render within compatible MCP clients. You will see transaction cards, payment links, and transfer details with responsive layouts, status badges, and interactive elements such as clickable payment links.
Fetch the final status of a transaction by its ID, including an accompanying UI card.
Resend a previously failed webhook for a specific transaction.
Create a payment link for customers, returning a UI card with a clickable link.
Disable an active checkout transaction link.
Analyze a failed transaction and provide guidance for retrying.
Retrieve the event timeline for a transaction, including a UI timeline.
List beneficiaries eligible for transfers.
List transfers for a customer.
Create a transfer for a customer, including a UI card.
Create a new beneficiary for future transfers.