Skip to main content
An AI agent can run the InFlow CLI for you. The CLI gives the agent discovery, enrollment, and payments. Connect the agent in one of four ways.

Ask the agent to set itself up

For the fastest setup, give your agent this instruction.
The agent installs the CLI, starts the login, and shows you the approval URL. The CLI prints the same setup guide.

Install the skills

The CLI has three skills. Each skill is a playbook for one task. Install all three for an agent that supports skills.
An agent can also load one skill from the installed CLI. This copy always matches the installed version.
The web copies are at inflowcli.ai/skills/<name>.md. They follow the latest release. Compare their version: header with inflow --version. Load the playbook before the task. Setup alone does not teach the agent the safe order of commands.

Run the CLI as an MCP server

The CLI can run as an MCP server that exposes its commands as tools.
Add a server named inflow to your MCP client configuration.
If your MCP client cannot find inflow, set command to the full path. To get the full path, run command -v inflow. The tool names replace the spaces in a command with underscores. Do not use npx @inflowpayai/inflow --mcp. The npm package does not start MCP. Install the CLI first. Then use inflow --mcp. Some MCP hosts do not load skills. For these hosts, put the output of inflow --skill <name> into the system prompt.

Install a plugin

The CLI repository includes plugins for Claude Code, Cursor, and Codex. In Claude Code, run these commands.

Let the agent read the CLI

An agent can read the current commands from the installed CLI. To set the output format, see --format in the CLI reference.

What stays with the owner

Three steps always need the owner.

Supported agents

Next step

Pay for a resource

Read how the agent pays, and what the owner approves.
Last modified on October 15, 2026