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.

data

Flutterwave CLI for AI Agents

Use the Flutterwave CLI from KosmoKrator to call Flutterwave tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.

Flutterwave CLI Setup

Flutterwave can be configured headlessly with `kosmokrator integrations:configure flutterwave`.

Install, configure, and verify

# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash

# Configure and verify this integration.
kosmokrator integrations:configure flutterwave --set secret_key="$FLUTTERWAVE_SECRET_KEY" --enable --read allow --write ask --json
kosmokrator integrations:doctor flutterwave --json
kosmokrator integrations:status --json

Credentials

Authentication type: Bearer token bearer_token. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.

Key	Env var	Type	Required	Label
`secret_key`	`FLUTTERWAVE_SECRET_KEY`	Secret `secret`	yes	Secret Key

Command Patterns

The generic command is stable across every integration. The provider shortcut is shorter for humans.

Generic CLI call

kosmo integrations:call flutterwave.flutterwave_list_transactions '{"page":1,"status":"example_status","from":"example_from","to":"example_to","customer_email":"example_customer_email","tx_ref":"example_tx_ref","customer_fullname":"example_customer_fullname","currency":"example_currency"}' --json

Provider shortcut

kosmo integrations:flutterwave flutterwave_list_transactions '{"page":1,"status":"example_status","from":"example_from","to":"example_to","customer_email":"example_customer_email","tx_ref":"example_tx_ref","customer_fullname":"example_customer_fullname","currency":"example_currency"}' --json

Discovery

These commands return structured output for coding agents that need to inspect capabilities before choosing a function.

Discovery commands

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

Automation Contexts

The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.

CI Run integration calls from CI jobs with JSON output, explicit credentials, and predictable exit status. Cron Jobs Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config. Shell Scripts Call integration functions from shell scripts with stable JSON input and output. Headless Automation Use KosmoKrator as a non-interactive integration runtime for local automations and wrappers. Coding Agents Let coding agents discover schemas and execute integration functions through CLI commands or MCP.

CLI Functions

Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.

`flutterwave.flutterwave_list_transactions`

List transactions from your Flutterwave account. Supports filtering by status and date range, with pagination.

Read read

Parameters: page, status, from, to, customer_email, tx_ref, customer_fullname, currency

Generic call

kosmo integrations:call flutterwave.flutterwave_list_transactions '{"page":1,"status":"example_status","from":"example_from","to":"example_to","customer_email":"example_customer_email","tx_ref":"example_tx_ref","customer_fullname":"example_customer_fullname","currency":"example_currency"}' --json

Shortcut

kosmo integrations:flutterwave flutterwave_list_transactions '{"page":1,"status":"example_status","from":"example_from","to":"example_to","customer_email":"example_customer_email","tx_ref":"example_tx_ref","customer_fullname":"example_customer_fullname","currency":"example_currency"}' --json

`flutterwave.flutterwave_get_transaction`

Retrieve full details of a specific Flutterwave transaction by its ID.

Read read

Parameters: id

Generic call

kosmo integrations:call flutterwave.flutterwave_get_transaction '{"id":1}' --json

Shortcut

kosmo integrations:flutterwave flutterwave_get_transaction '{"id":1}' --json

`flutterwave.flutterwave_initiate_payment`

Initiate a new payment on Flutterwave. Requires a transaction reference, amount, currency, and customer details.

Write write

Parameters: tx_ref, amount, currency, customer, redirect_url

Generic call

kosmo integrations:call flutterwave.flutterwave_initiate_payment '{"tx_ref":"example_tx_ref","amount":1,"currency":"example_currency","customer":"example_customer","redirect_url":"example_redirect_url"}' --json

Shortcut

kosmo integrations:flutterwave flutterwave_initiate_payment '{"tx_ref":"example_tx_ref","amount":1,"currency":"example_currency","customer":"example_customer","redirect_url":"example_redirect_url"}' --json

`flutterwave.flutterwave_verify_transaction`

Verify a Flutterwave transaction by its ID to confirm payment status and retrieve full details.

Read read

Parameters: id

Generic call

kosmo integrations:call flutterwave.flutterwave_verify_transaction '{"id":1}' --json

Shortcut

kosmo integrations:flutterwave flutterwave_verify_transaction '{"id":1}' --json

`flutterwave.flutterwave_list_customers`

List customers registered on your Flutterwave account, with pagination support.

Read read

Parameters: page

Generic call

kosmo integrations:call flutterwave.flutterwave_list_customers '{"page":1}' --json

Shortcut

kosmo integrations:flutterwave flutterwave_list_customers '{"page":1}' --json

`flutterwave.flutterwave_create_customer`

Create a new customer record on Flutterwave. Requires an email address.

Write write

Parameters: email, first_name, last_name, phone

Generic call

kosmo integrations:call flutterwave.flutterwave_create_customer '{"email":"example_email","first_name":"example_first_name","last_name":"example_last_name","phone":"example_phone"}' --json

Shortcut

kosmo integrations:flutterwave flutterwave_create_customer '{"email":"example_email","first_name":"example_first_name","last_name":"example_last_name","phone":"example_phone"}' --json

`flutterwave.flutterwave_get_banks`

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.

Read read

Parameters: country

Generic call

kosmo integrations:call flutterwave.flutterwave_get_banks '{"country":"example_country"}' --json

Shortcut

kosmo integrations:flutterwave flutterwave_get_banks '{"country":"example_country"}' --json

Function Schemas

Use these parameter tables when building CLI payloads without calling integrations:schema first.

flutterwave.flutterwave_list_transactions 8 parameters

Schema command

kosmo integrations:schema flutterwave.flutterwave_list_transactions --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (default: 1).
`status`	string	no	Filter by transaction status (e.g. "successful", "failed", "pending").
`from`	string	no	Start date for filtering transactions (YYYY-MM-DD).
`to`	string	no	End date for filtering transactions (YYYY-MM-DD).
`customer_email`	string	no	Filter by the customer email address.
`tx_ref`	string	no	Filter by merchant transaction reference.
`customer_fullname`	string	no	Filter by the customer full name.
`currency`	string	no	Filter by transaction currency.

flutterwave.flutterwave_get_transaction 1 parameters

Schema command

kosmo integrations:schema flutterwave.flutterwave_get_transaction --json

Parameter	Type	Required	Description
`id`	integer	yes	The Flutterwave transaction ID.

flutterwave.flutterwave_initiate_payment 5 parameters

Schema command

kosmo integrations:schema flutterwave.flutterwave_initiate_payment --json

Parameter	Type	Required	Description
`tx_ref`	string	yes	Your unique transaction reference (e.g. "txn-001").
`amount`	number	yes	Payment amount (e.g. 5000).
`currency`	string	yes	Three-letter currency code (e.g. "NGN", "USD", "KES").
`customer`	object	yes	Customer object with at least an "email" field. May also include "name" and "phonenumber".
`redirect_url`	string	no	URL to redirect the customer after payment completion.

flutterwave.flutterwave_verify_transaction 1 parameters

Schema command

kosmo integrations:schema flutterwave.flutterwave_verify_transaction --json

Parameter	Type	Required	Description
`id`	integer	yes	The Flutterwave transaction ID to verify.

flutterwave.flutterwave_list_customers 1 parameters

Schema command

kosmo integrations:schema flutterwave.flutterwave_list_customers --json

Parameter	Type	Required	Description
`page`	integer	no	Page number for pagination (default: 1).

flutterwave.flutterwave_create_customer 4 parameters

Schema command

kosmo integrations:schema flutterwave.flutterwave_create_customer --json

Parameter	Type	Required	Description
`email`	string	yes	Customer email address.
`first_name`	string	no	Customer first name.
`last_name`	string	no	Customer last name.
`phone`	string	no	Customer phone number.

flutterwave.flutterwave_get_banks 1 parameters

Schema command

kosmo integrations:schema flutterwave.flutterwave_get_banks --json

Parameter	Type	Required	Description
`country`	string	yes	ISO country code (e.g. "NG", "KE", "GH", "ZA").

Permissions

Headless calls still follow the integration read/write permission policy. Configure read/write defaults with integrations:configure. Add --force only for trusted automation that should bypass that policy.