Can I use Flutterwave as a CLI?

Yes. KosmoKrator exposes a Flutterwave CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Flutterwave through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Flutterwave tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Flutterwave credentials stored?

Flutterwave credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Flutterwave MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

other

Flutterwave CLI for Headless Automation

Use the Flutterwave CLI for headless automation with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 5 read 2 write API key auth

Submit Flutterwave feedback View package source

Flutterwave CLI for Headless Automation

Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers.

Use headless automation when another tool needs a stable local command surface. The Flutterwave CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Flutterwave CLI for Headless Automation
kosmokrator integrations:configure flutterwave --set secret_key="$FLUTTERWAVE_SECRET_KEY" --enable --read allow --write ask --json
kosmo integrations:call flutterwave.flutterwave_list_transactions '{"page":1,"status":"example_status","from":"example_from","to":"example_to"}' --json

Discovery Before Execution

Agents and scripts can inspect Flutterwave docs and schemas before choosing a function.

kosmo integrations:docs flutterwave --json
kosmo integrations:docs flutterwave.flutterwave_list_transactions --json
kosmo integrations:schema flutterwave.flutterwave_list_transactions --json
kosmo integrations:search "Flutterwave" --json
kosmo integrations:list --json

Useful Flutterwave CLI Functions

Function	Type	Parameters	Description
`flutterwave.flutterwave_list_transactions`	Read	page, status, from, to	List transactions from your Flutterwave account. Supports filtering by status and date range, with pagination.
`flutterwave.flutterwave_get_transaction`	Read	id	Retrieve full details of a specific Flutterwave transaction by its ID.
`flutterwave.flutterwave_initiate_payment`	Write	tx_ref, amount, currency, customer, redirect_url	Initiate a new payment on Flutterwave. Requires a transaction reference, amount, currency, and customer details.
`flutterwave.flutterwave_verify_transaction`	Read	id	Verify a Flutterwave transaction by its ID to confirm payment status and retrieve full details.
`flutterwave.flutterwave_list_customers`	Read	page	List customers registered on your Flutterwave account, with pagination support.
`flutterwave.flutterwave_create_customer`	Write	email, first_name, last_name, phone	Create a new customer record on Flutterwave. Requires an email address.
`flutterwave.flutterwave_get_banks`	Read	country	Get a list of supported banks for a given country from Flutterwave. Provide a country code like "NG" for Nigeria, "KE" for Kenya, "GH" for Ghana.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Flutterwave CLI Pages

CI Flutterwave CLI for CI. Cron Jobs Flutterwave CLI for cron jobs. Shell Scripts Flutterwave CLI for shell scripts. Coding Agents Flutterwave CLI for coding agents.