Server facts
inflow-cli MCP Server
Project
- Author
- inflowpayai
- Repository
- github.com/inflowpayai/inflow-cli
- License
- Not specified
- Category
- Blockchain & Web3
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 10
- Last commit
- Data as of
Tags
- agent skills
- agentic commerce
- agentic payments
- ai agents
- cli
- http 402
- mcp
- mcp server
- mpp
- onboarding
- payments
- stablecoins
- wallet
- x402
Overview
Payment workflows in inflow-cli start with identifying how a seller expects to be paid. A combined inspection tool checks a URL for MPP and x402 challenges without signing in or sending payment, with MPP preferred when both appear. Separate inspection and decoding tools expose each protocol's payment details. Buyers can also check supported MPP methods across intents, settlement rails, and currencies, or examine cached x402 capabilities by scheme and network.
Account tools handle login, logout, authentication checks, current-user retrieval, balance listing, and configured deposit addresses. For protected resources, the MPP and x402 payment tools submit payment and return the seller's response. Follow-up tools poll MPP transaction progress or x402 signing state, while cancellation tools attempt to cancel approvals on a best-effort basis. These workflows are available through the command-line interface and an MCP server using stdio. For agent hosts, the repository also offers a payment skill and plugin packaging that combines the skill with the MCP server, including integration paths for Claude Code, Cursor, and Codex.
inflow-cli setup notes
- inflow-cli records stdio only; confirm a network transport upstream before planning remote access.
- inflow-cli has no recorded license; confirm reuse terms in its repository.