About mcp-epayco
mcp-epayco is an MCP server for ePayco, a Colombian payment gateway, covering card tokenization and charges, PSE bank debit, and cash-network payments. Its tools mirror the official epayco-node SDK, and test mode is set through the EPAYCO_TEST payload flag.
Key features
- 01Card tokenization and customer creation
- 02Card charges and transaction lookup
- 03PSE bank debit and status queries
- 04Cash voucher creation for payment networks
- 05Test mode flag in payloads
Use cases
- 01Charging cards for Colombian online merchants from an AI agent
- 02Retrieving PSE bank redirect URLs and transaction status
- 03Generating cash vouchers for in-store payment networks
MCP support
The server exposes eight tools over MCP that wrap ePayco's card, PSE and cash payment endpoints.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y @codespar/mcp-epaycoEPAYCO_PUBLIC_KEYSecretePayco public keyEPAYCO_PRIVATE_KEYSecretePayco private keyEPAYCO_TEST"true" flags payloads as test mode. Defaults to "true" — set "false" for production.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
8Saved tool list · updated 2w ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| cvc | string | Yes | Card CVC |
| exp_year | string | Yes | Expiry year, e.g. 2027 |
| exp_month | string | Yes | Expiry month, e.g. 09 |
| card_number | string | Yes | Card PAN |
Details
From the project README@codespar/mcp-epayco
MCP server for ePayco — Colombian payment gateway (Davivienda-owned): card tokenization and charges, PSE bank debit, and cash networks (Efecty, Gana, Red Servi, Punto Red, Su Red).
The tool set mirrors the official ePayco SDKs (epayco-node): the card/token API on api.secure.payco.co and the restpagos API on secure.payco.co for PSE and cash. Test mode is a payload flag (EPAYCO_TEST), not a separate host.
Quick Start
Claude Desktop
Add to ~/.config/claude/claude_desktop_config.json:
{
"mcpServers": {
"epayco": {
"command": "npx",
"args": ["-y", "@codespar/mcp-epayco"],
"env": {
"EPAYCO_PUBLIC_KEY": "your-public-key",
"EPAYCO_PRIVATE_KEY": "your-private-key",
"EPAYCO_TEST": "true"
}
}
}
}
Claude Code
claude mcp add epayco --env EPAYCO_PUBLIC_KEY=pk --env EPAYCO_PRIVATE_KEY=sk -- npx -y @codespar/mcp-epayco
Tools (8)
| Tool | Description |
|---|---|
tokenize_card | Create a card token (POST /v1/tokens) |
create_customer | Create a customer bound to a card token |
charge_card | Charge a tokenized card (POST /payment/v1/charge/create) |
get_transaction | Transaction detail by referencePayco |
create_pse_payment | PSE bank debit — returns the bank redirect URL |
get_pse_transaction | PSE transaction status by transaction id |
list_pse_banks | PSE bank list |
create_cash_payment | Cash voucher on efecty / gana / redservi / puntored / sured |
Environment
| Variable | Required | Description |
|---|---|---|
EPAYCO_PUBLIC_KEY | yes | Public key |
EPAYCO_PRIVATE_KEY | yes | Private key |
EPAYCO_TEST | no | "true" (default) flags payloads as test mode |
Docs
- Provider docs: https://docs.epayco.com
- Managed tier (one interface across every LATAM provider, governance + audit): https://codespar.dev/agents
Enterprise
Need governance, budget limits, and audit trails for agent-driven payments on ePayco? CodeSpar Enterprise adds a policy engine, payment routing, and compliance templates on top of these MCP servers.
License
MIT
Comments
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.