Skip to main content
W

Wompi

@codespar/mcp-wompi · v0.2.2

🇨🇴 ColombiaPaymentsAuth · API Keybeta22 tools4 env vars

Colombian payment gateway by Bancolombia: cards, PSE bank transfers, and Nequi wallet. Your agent accepts COP with local checkout.

Get started · freeView docs

MIT · runs locally or through the CodeSpar runtime

Limitations

  • The package manifest does not declare 1 of the 4 variables the code reads.
  • The npm package ships no server.json manifest.
Package
@codespar/mcp-wompi
Version
0.2.2
npm dist-tag
latest
Category
Payments
Auth
API Key
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 variables4 variables read by this server's code, listed below.
Restart and make the first callThe agent can call any of the 22 tools. Try create_transaction first.
terminal
# Claude Code claude mcp add wompi -e WOMPI_EVENTS_SECRET=… -e WOMPI_PRIVATE_KEY=… -e WOMPI_PUBLIC_KEY=… -e WOMPI_SANDBOX=… -- npx -y @codespar/mcp-wompi@0.2.2 # then: /mcp to confirm the server is connected
Environment variables4 variables
WOMPI_EVENTS_SECRETEvents/webhook secret for signature validationoptionalsecret
WOMPI_PRIVATE_KEYPrivate key for Wompirequiredsecret
WOMPI_PUBLIC_KEYPublic key for Wompirequired
WOMPI_SANDBOXRead by the code; the package manifest does not declare it.

Names read from the package code (@codespar/mcp-wompi@0.2.2). 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 democreate_transaction

"Create a payment transaction"

tools/callcreate_transactionresult returned

Tools

What your agent can call.

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

create_transaction

Create a payment transaction

get_transaction

Get transaction details by ID

list_transactions

List transactions

search_transaction_by_reference

Find transaction(s) by merchant reference

void_transaction

Void a transaction

create_payment_link

Create a payment link

get_payment_link

Get payment link details

update_payment_link

Update a payment link

list_payment_links

List payment links

list_payment_methods

List available payment methods for the merchant

get_acceptance_token

Get merchant acceptance token (required for transactions)

create_tokenized_card

Tokenize a credit/debit card

Names and descriptions come from the package's tools/list (@codespar/mcp-wompi@0.2.2). 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 Wompi MCP server?

Run npx -y @codespar/mcp-wompi@0.2.2 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 Wompi in your project; codespar_discover finds its tools.

What can my agent do with Wompi?

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

How does Wompi authenticate, and how are credentials stored?

Wompi uses API Key. 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, and the runtime adds it to each provider call, so the agent never handles it.

How does Wompi handle upstream API changes?

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

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

Yes. Wompi is MIT-licensed and published on npm as @codespar/mcp-wompi, 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 adds it to each call. 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 Wompi in your project and ask your agent for the first call.
Wompi — MCP server · 22 tools | CodeSpar