Mcp Flow Cl

io.github.codesparPublished by GitHub account codesparv0.1.0Updated Oct 24, 2026

MCP server for Flow.cl — Chilean PSP: hosted payment orders, Webpay, refunds, HMAC-signed API

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Local MCP server for Flow.cl, Chile's payment service provider, letting an assistant create hosted payment orders, check payment status and issue refunds.

What you can do
Create hosted payment orders and get a payment link the customer pays at, or have Flow email the customer a collection link. Look up payment status by Flow token, commerce order or Flow order number. List payments received on a given date, with paging. Create full or partial refunds and check refund status.
When to use it
Useful when an assistant should help a Chilean merchant take payments through Flow, for example generating a payment link for an order, reconciling which orders were paid, or starting a refund, without hand-writing the signed API calls.
Requirements
Runs locally via npx from the npm package @codespar/mcp-flow-cl, so Node.js is needed. Requires a Flow merchant account with an API key and secret key, set as FLOW_API_KEY and FLOW_SECRET_KEY. FLOW_ENV selects sandbox (default) or production; the sandbox issues its own key pair. Network access to Flow's API.
Before you install
The server holds merchant credentials that can create payments and refunds; FLOW_SECRET_KEY signs every request and should be kept private. Setting FLOW_ENV to production moves real money and refunds real transactions, so test in sandbox first. Creating payments and refunds changes data on the Flow account.

Installation

In SourceWeft

  1. Open Mcp Flow Cl in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@codespar/mcp-flow-cl

MCP server for Flow (flow.cl) — the Chile-native PSP: one hosted payment order covers Webpay (credit/debit), ETpay bank transfer, cash networks and international cards. Refunds included. Every API call is HMAC-SHA256 signed.

[npm] [License: MIT]

Quick Start

Claude Desktop

Add to ~/.config/claude/claude_desktop_config.json:

json
{  "mcpServers": {    "flow-cl": {      "command": "npx",      "args": ["-y", "@codespar/mcp-flow-cl"],      "env": {        "FLOW_API_KEY": "your-flow-api-key",        "FLOW_SECRET_KEY": "your-flow-secret-key",        "FLOW_ENV": "sandbox"      }    }  }}

Claude Code

bash
claude mcp add flow-cl --env FLOW_API_KEY=... --env FLOW_SECRET_KEY=... -- npx -y @codespar/mcp-flow-cl

Cursor / VS Code

Add the same block to .cursor/mcp.json or .vscode/mcp.json.

Tools (8)

ToolEndpointWhat it does
create_paymentPOST /payment/createHosted payment order; returns url + token the customer pays at
create_payment_by_emailPOST /payment/createEmailFlow emails the customer a collection link
get_payment_statusGET /payment/getStatusStatus by Flow token (1 pending, 2 paid, 3 rejected, 4 canceled)
get_payment_status_by_commerce_idGET /payment/getStatusByCommerceIdStatus by your commerceOrder
get_payment_status_by_flow_orderGET /payment/getStatusByFlowOrderStatus by Flow order number
list_paymentsGET /payment/getPaymentsPayments received on a date (paged)
create_refundPOST /refund/createFull or partial refund order
get_refund_statusGET /refund/getStatusRefund status by refund token

Authentication

Flow signs every request: parameters are sorted alphabetically, concatenated as name+value, and signed with HMAC-SHA256 using your secretKey. This server does the signing for you — set the two env vars and call tools with plain arguments.

VariableRequiredDescription
FLOW_API_KEYyesFlow merchant API key
FLOW_SECRET_KEYyesHMAC signing secret (never sent on the wire)
FLOW_ENVnosandbox (default) or production

Sandbox: register at sandbox.flow.cl — the sandbox issues its own key pair.

Example

"Create a Flow payment order for CLP 25,000, subject 'Plan Pro mensual', email [email protected], and give me the payment link."

The agent calls create_payment and returns url?token=... — the customer picks Webpay, ETpay or cash at Flow's hosted page.

Enterprise

Need governance, budget limits, and audit trails for agent payments? CodeSpar Enterprise adds policy engine, payment routing, and compliance templates on top of these MCP servers.

Managed tier

This open-source server calls Flow's API directly with your credentials. CodeSpar's managed tier routes one interface across every LATAM provider with automatic failover, governance, audit and a credential vault: codespar.dev/agents.

License

MIT

Source: packages/payments/flow-cl/README.md at commit d0a519a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts