Skip to main content
E

ePayco

@codespar/mcp-epayco · v0.1.0

🇨🇴 ColombiaPaymentsAuth · OAuth2beta8 tools3 env vars

Colombian gateway (Davivienda-owned) with broad inbound coverage: cards, PSE bank debit, Daviplata wallet and cash networks.

Get started · freeView docs

MIT · runs locally or through the CodeSpar runtime

Limitations

  • The npm package ships no server.json manifest.
Package
@codespar/mcp-epayco
Version
0.1.0
npm dist-tag
latest
Category
Payments
Auth
OAuth2
Country
🇨🇴 Colombia
License
MIT
Transport
stdio · streamable-http

Quickstart

Install, set the credentials, make the first call.

Pick your client. The server runs locally over stdio, or through the hosted runtime.

Add the server to your clientOne config entry. No build step, no SDK required.
Set the environment variables3 variables read by this server's code, listed below.
Restart and make the first callThe agent can call any of the 8 tools. Try tokenize_card first.
terminal
# Claude Code claude mcp add epayco -e EPAYCO_PRIVATE_KEY=… -e EPAYCO_PUBLIC_KEY=… -e EPAYCO_TEST=… -- npx -y @codespar/mcp-epayco@0.1.0 # then: /mcp to confirm the server is connected
Environment variables3 variables
EPAYCO_PRIVATE_KEYePayco private keyrequiredsecret
EPAYCO_PUBLIC_KEYePayco public keyrequired
EPAYCO_TEST"true" flags payloads as test mode. Defaults to "true" — set "false" for production.optional

Names read from the package code (@codespar/mcp-epayco@0.1.0). Descriptions and flags come from its manifest. Self-hosted, you hold the credentials. On the CodeSpar runtime the credential you connect is stored encrypted (AES-256-GCM, key derived per organization), and the runtime adds it to the provider call itself; the agent never receives it.

First call demotokenize_card

"Create a one-time card token"

tools/calltokenize_cardresult returned

Tools

What your agent can call.

8 tools, as the package's tools/list returns them.

tokenize_card

Create a one-time card token (POST /v1/tokens on api.secure.payco.co). The token is then bound to a customer via create_customer and charged via charge_card.

create_customer

Create an ePayco customer bound to a card token (POST /payment/v1/customer/create). Returns customer_id used by charge_card.

charge_card

Charge a tokenized card (POST /payment/v1/charge/create). Amounts in COP unless currency says otherwise. Test mode is controlled by EPAYCO_TEST.

get_transaction

Get transaction detail by referencePayco (GET https://secure.epayco.co/validation/v1/reference/{ref}). Works for card, PSE and cash payments.

create_pse_payment

Create a PSE bank-debit payment (POST /restpagos/pagos/debitos.json on secure.payco.co). Returns a bank redirect URL the payer must open to authorize the debit.

get_pse_transaction

Get a PSE transaction's status by transaction id (GET /restpagos/pse/transactioninfo.json on secure.payco.co).

list_pse_banks

List PSE banks available for bank debit (GET /restpagos/pse/bancos.json on secure.payco.co).

create_cash_payment

Create a cash payment voucher on a Colombian cash network (POST /restpagos/v2/efectivo/{network} on secure.payco.co). The payer takes the voucher code to a physical point to pay.

Names and descriptions come from the package's tools/list (@codespar/mcp-epayco@0.1.0). A kind (read, write, delete) is shown only when the package annotates its tools or each tool was verified one by one; neither exists for this server yet.

Compatibility

MCP is a protocol. Any client that speaks it can mount this server.

Through the CodeSpar runtime, codespar_discover finds this server's tools, and a tools/call runs with the credential connected in your project, a test key included.

hostedhttps://connect.codespar.dev/mcp15 meta-tools

Protocol

Any MCP client

stdio · streamable-http

Questions

Before you install.

How do I install the ePayco MCP server?

Run npx -y @codespar/mcp-epayco@0.1.0 and add the config block above to your MCP client: Claude Code, Cursor, Claude Desktop, VS Code, or any MCP-compatible client. No build step, no SDK required. Prefer hosted? Add the CodeSpar endpoint with a test key and connect ePayco in your project; codespar_discover finds its tools.

What can my agent do with ePayco?

ePayco exposes 8 tools for payments. Your agent calls them directly; the full list is above.

How does ePayco authenticate, and how are credentials stored?

ePayco uses OAuth2. Self-hosted, you hold the credentials: the server reads them from its environment variables. On the CodeSpar runtime the credential you connect is stored encrypted for your organization, the runtime renews the OAuth2 access token, and it adds the token to each provider call, so the agent never handles it.

How does ePayco handle upstream API changes?

Every server is versioned independently on npm. The command on this page pins 0.1.0, the version whose tools are listed here; your agent keeps running it until you change the version.

Is ePayco open source? How do I report a bug?

Yes. ePayco is MIT-licensed and published on npm as @codespar/mcp-epayco, source on GitHub (link in the Details panel). Report issues on the package repository; security issues go to security@codespar.dev, and we respond within 24 hours.

Start in seconds.

On the CodeSpar runtime, the credential you connect stays encrypted for your organization and the runtime renews the OAuth2 access token. You just call the tool.

Start in seconds demo
Create an account and copy a test key.
Add the hosted endpoint to your client with the config above.
Connect ePayco in your project and ask your agent for the first call.
ePayco — MCP server · 8 tools | CodeSpar