Mcp Flutterwave
Connect your agent to Flutterwave APIs so you can implement payments, payouts, and money APIs without hand-reading every endpoint.
Overview
io.github.bajoski34/mcp-flutterwave is a Build-phase MCP server that exposes Flutterwave payment APIs to AI agents via an authenticated stdio npm integration.
What is this MCP server?
- MCP stdio server (mcp-flutterwave npm v1.2.0) for Flutterwave REST APIs
- Requires FLW_SECRET_KEY so the agent can call authenticated Flutterwave operations safely via env config
- stdio transport for Claude Code, Cursor, and other MCP clients—no separate gateway required
- Speeds payment feature scaffolding for SaaS, marketplaces, and African-market checkout flows
- Open-source entry at bajoski34/mcp-flutterwave for indie payment integrations
- Version 1.2.0
- 1 required secret environment variable: FLW_SECRET_KEY
- npm identifier mcp-flutterwave, stdio transport, registry.npmjs.org
What problem does it solve?
Implementing Flutterwave means juggling secret keys, endpoint shapes, and docs while your agent cannot call the API context you already trust.
Who is it for?
Solo builders adding Flutterwave checkout, transfers, or subscriptions who want agent-assisted API exploration inside Claude Code or Cursor.
Skip if: Products on Stripe-only stacks, or anyone unwilling to put a live secret key in a local MCP environment.
What do I get? / Deliverables
Once FLW_SECRET_KEY is set and the MCP server is registered, your agent can propose and validate Flutterwave API interactions aligned with your live credentials model.
- Agent-callable Flutterwave API surface via MCP
- Faster payment endpoint discovery and integration drafts
- Documented env-based secret handling for local agent sessions
Recommended MCP Servers
Journey fit
Payment provider wiring is classic Build work when the product needs charge, transfer, or wallet flows before Ship. Integrations fits because the server is an API bridge to Flutterwave, not pricing strategy (validate) or production monitoring (operate).
How it compares
Flutterwave API MCP connector, not a billing analytics dashboard or a Validate-phase pricing skill.
Common Questions / FAQ
Who is io.github.bajoski34/mcp-flutterwave for?
Indie developers and small teams building paid products on Flutterwave who want their coding agent to work against real API semantics with MCP.
When should I use io.github.bajoski34/mcp-flutterwave?
Use it during Build integrations while you wire payments, verify Flutterwave endpoints, or generate server-side payment code before production hardening.
How do I add io.github.bajoski34/mcp-flutterwave to my agent?
Install mcp-flutterwave from npm, set FLW_SECRET_KEY in the MCP server environment, register stdio transport in your agent host, and use Flutterwave sandbox or live keys per your policy.