Mcp Epayco

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

MCP server for ePayco — Colombian gateway: cards, PSE, Daviplata and cash networks

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

MCP server for the ePayco Colombian payment gateway, letting an assistant tokenize cards, charge them, start PSE bank debits and create cash vouchers.

What you can do
  • Tokenize cards and create customers bound to a card token
  • Charge tokenized cards and look up transaction details by reference
  • Create PSE bank debit payments, check their status and list PSE banks
  • Create cash payment vouchers on Efecty, Gana, Red Servi, Punto Red and Su Red
When to use it
Useful when an assistant needs to drive ePayco payment flows from a local session: testing checkout integrations, creating charges or PSE and cash payment intents, and checking transaction status.
Requirements
Runs locally via npx from the npm package @codespar/mcp-epayco (Node.js required). Needs the EPAYCO_PUBLIC_KEY and EPAYCO_PRIVATE_KEY environment variables; EPAYCO_TEST defaults to "true" and must be set to "false" for production. Network access to ePayco hosts is required. Desktop client only.
Before you install
The private key EPAYCO_PRIVATE_KEY is a payment credential that can move real money; keep it out of shared configs. Test mode is only a payload flag, so a wrong EPAYCO_TEST value can create real charges, PSE debits or cash vouchers. Card data and payment details are sent to ePayco. The README also advertises a paid managed and enterprise tier.

Installation

In SourceWeft

  1. Open Mcp Epayco 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-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).

[npm] [License: MIT]

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:

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

bash
claude mcp add epayco --env EPAYCO_PUBLIC_KEY=pk --env EPAYCO_PRIVATE_KEY=sk -- npx -y @codespar/mcp-epayco

Tools (8)

ToolDescription
tokenize_cardCreate a card token (POST /v1/tokens)
create_customerCreate a customer bound to a card token
charge_cardCharge a tokenized card (POST /payment/v1/charge/create)
get_transactionTransaction detail by referencePayco
create_pse_paymentPSE bank debit — returns the bank redirect URL
get_pse_transactionPSE transaction status by transaction id
list_pse_banksPSE bank list
create_cash_paymentCash voucher on efecty / gana / redservi / puntored / sured

Environment

VariableRequiredDescription
EPAYCO_PUBLIC_KEYyesPublic key
EPAYCO_PRIVATE_KEYyesPrivate key
EPAYCO_TESTno"true" (default) flags payloads as test mode

Docs

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

Source: packages/colombia/epayco/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