mcpField
M
mcp-clip

mcp-clip

Local
github.com/codesparFinance275Updated 5w ago

About mcp-clip

mcp-clip is an MCP server for Clip (PayClip), a payment acquirer in Mexico. It is intended for merchants collecting payments in MXN and exposes hosted payment links, card-token charges and refunds as tools. Raw card numbers are not accepted by the server.

Key features

  1. 01Hosted payment link creation and status lookup
  2. 02Card-token charges from Clip's client-side SDK
  3. 03Payment detail lookup and paginated listing
  4. 04Full or partial refunds

Use cases

  1. 01Generating a payment link through an agent and sending it to a buyer
  2. 02Collecting payments without handling raw card data
  3. 03Checking payment records and issuing refunds for orders

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"codespar-mcp-clip": {
"command": "npx",
"args": [
"-y",
"@codespar/mcp-clip"
],
"env": {
"CLIP_AUTH_TOKEN": "<CLIP_AUTH_TOKEN>",
"CLIP_BASE_URL": "<CLIP_BASE_URL>"
}
}
}
}
Run commandnpx -y @codespar/mcp-clip
Environment variables to set
CLIP_AUTH_TOKENSecretBasic auth token from the Clip developer dashboard
CLIP_BASE_URLAPI base URL override. Defaults to https://api.payclip.com.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@codespar/mcp-clip0.1.0

Tools

6

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
amountnumberYesAmount in MXN (decimal pesos, e.g. 150.00)
currencystringNoCurrency code. Clip processes MXN.
metadataobjectNoOptional metadata echoed back on queries/webhooks
redirection_urlobjectNoWhere the buyer lands after paying
redirection_url.errorstringNoURL on failure
redirection_url.defaultstringNoFallback URL
redirection_url.successstringNoURL on success
purchase_descriptionstringYesWhat the buyer is paying for (shown at checkout)

Details

From the project README

@codespar/mcp-clip

MCP server for Clip (PayClip) — Mexico's leading native acquirer. Hosted payment links, transparent card-token charges, queries and refunds, in MXN.

npm License: MIT

Quick Start

Claude Desktop

Add to ~/.config/claude/claude_desktop_config.json:

{
  "mcpServers": {
    "clip": {
      "command": "npx",
      "args": ["-y", "@codespar/mcp-clip"],
      "env": {
        "CLIP_AUTH_TOKEN": "your-basic-token"
      }
    }
  }
}
Claude Code
claude mcp add clip -- npx @codespar/mcp-clip

Environment

VariableRequiredDescription
CLIP_AUTH_TOKENyesBasic auth token from the Clip developer dashboard (sent as Authorization: Basic <token>)
CLIP_BASE_URLnoAPI base override (default https://api.payclip.com)

Test mode: Clip distinguishes environments by the token itself — test tokens hit the sandbox processing path; there is no separate URL.

Tools (6)

ToolWhat it does
create_payment_linkHosted checkout link (POST /v2/checkout) — the no-PCI path
get_payment_linkCheckout status by id
create_paymentTransparent charge with a client-side card token (POST /payments)
get_paymentPayment detail
list_paymentsList payments, paginated
refund_paymentFull or partial refund (POST /payments/{id}/refund)

Raw card numbers are never accepted — create_payment takes a token from Clip's client-side SDK. When you have no tokenization front-end, use create_payment_link.

Example

"Cobra 450 pesos por la consultoría y mándame el link."

The agent calls create_payment_link (amount: 450.00, purchase_description: "Consultoría") and returns the payment_request_url for the buyer.

Authentication

Clip issues a single Basic auth token in the developer dashboard; the server sends it as Authorization: Basic <CLIP_AUTH_TOKEN> on every call.

Enterprise

Need governance, budget limits, and audit trails for agent-driven payments on Clip? CodeSpar Enterprise adds a policy engine, payment routing, and compliance templates on top of these MCP servers.

License

MIT

Comments

Markdown supported

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.