Mcp Clip

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

MCP server for Clip (PayClip) — Mexico's leading acquirer: payment links, card charges, refunds

VerifiedSTDIODesktop onlyFinance Business & Commerce

Server details

Identifier: io.github.codespar/mcp-clip
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account codespar for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.codespar%2Fmcp-clip.svg)](https://sourceweft.com/mcp/io.github.codespar%2Fmcp-clip?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that lets an assistant create Clip (PayClip) payment links, card-token charges, payment lookups and refunds in MXN.

What you can do: Create and check hosted checkout payment links, returning the URL for a buyer to pay in MXN. Create transparent card charges using a client-side card token, and retrieve payment details. List payments with pagination. Issue full or partial refunds on an existing payment.
When to use it: Useful when you want an assistant to take payments in Mexico through Clip — sending a checkout link for an invoice or service, checking whether a payment went through, or processing a refund — without building a separate integration.
Requirements: Runs locally via npx from the npm package @codespar/mcp-clip on a desktop machine. Requires a Clip developer account and a Basic auth token supplied in the CLIP_AUTH_TOKEN environment variable. CLIP_BASE_URL optionally overrides the API base URL, which defaults to the Clip production API. Network access to Clip is needed.

Before you install

The token grants payment authority: charges and refunds move real money, so treat CLIP_AUTH_TOKEN as a sensitive secret. Test versus live behavior is determined by the token itself, so a live token can create real charges. Refunds and charges write to the account; review amounts before confirming. Raw card numbers are not accepted, only client-side tokens.

Installation

In SourceWeft

Open Mcp Clip in the dashboard and add it to a workspace.
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-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:

json

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

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

Claude Code

Environment

Variable	Required	Description
`CLIP_AUTH_TOKEN`	yes	Basic auth token from the Clip developer dashboard (sent as `Authorization: Basic <token>`)
`CLIP_BASE_URL`	no	API 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)

Tool	What it does
`create_payment_link`	Hosted checkout link (`POST /v2/checkout`) — the no-PCI path
`get_payment_link`	Checkout status by id
`create_payment`	Transparent charge with a client-side card token (`POST /payments`)
`get_payment`	Payment detail
`list_payments`	List payments, paginated
`refund_payment`	Full 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

Source: packages/mexico/clip/README.md at commit d0a519a

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

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