
Mcp Khipu
io.github.codesparPublished by GitHub account codesparv0.2.0-alpha.3Updated Nov 3, 2026
MCP server for Khipu — Chilean instant bank-transfer payments (complements Transbank cards)
Overview
MCP server for Khipu, Chile's instant bank-transfer payment provider, letting an assistant create, track, refund and reconcile payments.
- What you can do
- Create, retrieve, list, confirm, cancel and refund Khipu bank-transfer payments, including recurring automatic payments.
- Predict payment success and list supported Chilean banks.
- Inspect merchant receivers and their collection bank accounts, and onboard new receivers under an integrator account.
- Review settlement/conciliation records and payer reviews.
- Register, list and delete webhook endpoints for payment notifications.
- Create and check in-person terminal (POS) sessions for bank-transfer checkout.
- When to use it
- Useful when building or operating a Chilean checkout that accepts bank transfers, or when an assistant should handle payment status, refunds, reconciliation and webhook setup for a Khipu merchant account.
- Requirements
- Runs locally via npx from the npm package @codespar/mcp-khipu (Node.js). Needs a Khipu merchant account and an API key in KHIPU_API_KEY; legacy v2 auth instead uses KHIPU_RECEIVER_ID and KHIPU_SECRET. KHIPU_BASE_URL is optional and defaults to the Khipu v3 endpoint. Network access to Khipu is required.
Installation
In SourceWeft
- Open Mcp Khipu in the dashboard and add it to a workspace.
- 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-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)
Install
Environment
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
Why Khipu + Transbank
Chile has two dominant checkout rails:
- Card (Transbank Webpay) — universal, works everywhere, interchange fees apply.
- 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
@codespar/mcp-transbank— Chilean card acquiring (Webpay Plus, Oneclick, Full Transaction)@codespar/mcp-dlocal— cross-border LatAm coverage when you need CL + other countries through one API
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
Source: packages/payments/khipu/README.md at commit d0a519a
Tools
0Version history
1- v0.2.0-alpha.3LatestSep 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