mcpField
M
mcp-khipu

mcp-khipu

Local
github.com/codesparFinance275Updated 4w ago

About mcp-khipu

mcp-khipu is an MCP server for Khipu, a Chilean instant bank-transfer payment provider. It is designed for Chilean merchants and agents that accept bank transfers alongside card payments such as mcp-transbank. It covers payments, refunds, reconciliation, webhooks and POS terminal sessions.

Key features

  1. 01Create, get, confirm and refund payments
  2. 02Filter payment records by date and status
  3. 03Bank and merchant account lookups
  4. 04Reconciliation and payer review queries
  5. 05Webhook registration and management
  6. 06POS terminal sessions and automatic payments

Use cases

  1. 01Offering bank-transfer checkout in Chilean e-commerce
  2. 02Collecting payments for larger purchases and B2B sales
  3. 03Combining bank transfer with card payments at checkout

MCP support

The server exposes Khipu's payment, merchant, webhook and terminal session endpoints as MCP tools that MCP clients can call directly.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"codespar-mcp-khipu": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-khipu"
],
"env": {
"KHIPU_API_KEY": "<KHIPU_API_KEY>",
"KHIPU_RECEIVER_ID": "<KHIPU_RECEIVER_ID>",
"KHIPU_SECRET": "<KHIPU_SECRET>",
"KHIPU_BASE_URL": "<KHIPU_BASE_URL>"
}
}
}
}
Run commandnpx -y @codespar/mcp-khipu
Environment variables to set
KHIPU_API_KEYSecretKhipu v3 API key (sent as x-api-key header). Obtain from Khipu merchant panel → Developers.
KHIPU_RECEIVER_IDKhipu receiver id (merchant id). Required only for legacy v2 HTTP Basic auth; not needed when KHIPU_API_KEY is set.
KHIPU_SECRETSecretKhipu receiver secret. Required only for legacy v2 HTTP Basic auth; not needed when KHIPU_API_KEY is set.
KHIPU_BASE_URLKhipu API base URL. Defaults to https://payment-api.khipu.com/v3.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@codespar/mcp-khipu0.2.0-alpha.3

Tools

21

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
bodystringNoLonger description of the payment (shown alongside subject)
amountnumberYesAmount in major units (CLP has no decimals — 1000 = 1000 pesos)
customstringNoArbitrary merchant string (JSON-encoded if you need structure) echoed back in webhooks
subjectstringYesShort human-readable purpose of the payment (shown to the payer at their bank)
currencystringYesISO-4217 currency code. Typically CLP for Chile; CLF supported for UF-denominated charges.
cancel_urlstringNoBrowser redirect target if the payer cancels
notify_urlstringNoWebhook URL Khipu POSTs to on status changes (receives a notification_token)
payer_namestringNoPayer display name
return_urlstringNoBrowser redirect target after a successful payment
send_emailbooleanNoIf true, Khipu emails the payer with the payment link
payer_emailstringNoPayer email — Khipu emails the payment instructions to this address
expires_datestringNoISO-8601 expiration timestamp for this payment request
integrator_feenumberNoIntegrator fee (for partners)
send_remindersbooleanNoIf true, Khipu sends the payer reminder emails before expiration
transaction_idstringNoMerchant-side order reference echoed back in webhooks
notify_api_versionstringNoWebhook API version. Use '3.0' for v3 notifications.
collect_account_uuidstringNoOverride the default collection account
confirm_timeout_datestringNoISO-8601 deadline after which an unconfirmed payment auto-reverses
responsible_user_emailstringNoInternal merchant user email shown in Khipu's dashboard as responsible for this charge
fixed_payer_personal_identifierstringNoLock this payment to a specific payer RUT

Details

From the project README

@codespar/mcp-khipu

MCP server for Khipu — Chilean instant bank-transfer PSP.

Khipu lets a payer pay from their Chilean bank account in real time: the merchant creates a payment, the payer is redirected to Khipu, logs into their bank, and the transfer lands instantly. No card, no credit limit, no interchange fees — the Chilean preferred rail for higher-ticket purchases.

Chilean agents typically bundle Khipu with @codespar/mcp-transbank: Webpay for cards, Khipu for bank transfers. Together they cover the vast majority of Chilean checkout preferences.

Tools (21)

ToolPurpose
create_paymentCreate a Khipu payment (bank-transfer charge).
get_paymentRetrieve a Khipu payment.
delete_paymentDelete (cancel) a pending Khipu payment.
confirm_paymentManually confirm a Khipu payment.
refund_paymentRefund a paid Khipu payment (full or partial).
list_paymentsList Khipu payments for the current merchant, optionally filtered by date range and status.
predict_paymentPredict whether a payment is likely to succeed for a given payer+amount+bank, and recommend the best bank/r...
get_merchantsList the merchant receiver accounts accessible with the current API key.
get_merchantFetch a single merchant by id.
list_merchant_accountsList the bank accounts registered for a merchant to collect into.
create_receiverCreate (onboard) a new receiver under an integrator account.
list_receiversList receivers onboarded under the current integrator account.
list_conciliationsList settlement / conciliation records for a date range.
list_reviewsList payer reviews / opinions left after a Khipu payment.
register_webhookRegister a webhook endpoint to receive Khipu notifications (payment.paid, payment.refunded, etc).
list_webhooksList registered webhook endpoints for the current merchant.
delete_webhookDelete (unregister) a webhook endpoint by id.
create_terminal_sessionCreate a Khipu terminal session for in-person / POS bank-transfer checkout.
get_terminal_sessionRetrieve the current status of a terminal (POS) session — whether the payer has scanned, paid, or the sessi...
get_banksList Chilean banks supported by Khipu for bank-transfer payments.
create_automatic_paymentCreate a Khipu automatic payment (recurring / subscription charge against a previously enrolled subscriptio...

Install

npm install @codespar/mcp-khipu@alpha

Environment

# Preferred — v3 API key auth
KHIPU_API_KEY="..."       # sent as x-api-key header

# Legacy — v2 HTTP Basic auth (only if no API key available)
KHIPU_RECEIVER_ID="..."   # merchant receiver id
KHIPU_SECRET="..."        # receiver secret

# Optional
KHIPU_BASE_URL="..."      # defaults to https://payment-api.khipu.com/v3

Authentication

Khipu v3 uses a single API key in the x-api-key header — no request signing, no HMAC. Obtain the key from the Khipu merchant panel under Developers → API keys.

If KHIPU_API_KEY is unset, the server falls back to v2 HTTP Basic with KHIPU_RECEIVER_ID:KHIPU_SECRET for merchants still on the legacy endpoints.

All request bodies are JSON (v3); the server sets Content-Type: application/json automatically.

Run

# stdio (default — for Claude Desktop, Cursor, etc)
npx @codespar/mcp-khipu

# HTTP (for server-to-server testing)
MCP_HTTP=true MCP_PORT=3000 npx @codespar/mcp-khipu

Why Khipu + Transbank

Chile has two dominant checkout rails:

  1. Card (Transbank Webpay) — universal, works everywhere, interchange fees apply.
  2. Bank transfer (Khipu) — no card needed, no credit limit, cheaper fees, preferred for larger purchases and B2B.

An agent that can offer both at checkout converts materially better than one that only takes cards. @codespar/mcp-transbank handles the first; this package handles the second.

Pair with

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.

License

MIT

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.