Clip

What your agent can do

Clip gives your agent 6 tools it calls directly — pick the ones it needs, in Claude, Cursor, or any MCP client.

• →create_payment_link — Create a hosted checkout / payment link (POST /v2/checkout). The buyer opens the returned payment_request_url and pays with card, Clip account or other enabled MX methods. Amount is in MXN pesos (decimal, e.g. 150.00).
• →get_payment_link — Fetch a checkout / payment link by id (GET /v2/checkout/{id}) — status, amount, payment outcome.
• →create_payment — Create a transparent card charge (POST /payments) using a card token generated by Clip's client-side SDK. Use create_payment_link instead when you have no tokenization front-end — raw card numbers are never accepted here.

// Your agent calls a tool directly — no glue code.
// CodeSpar's managed tier handles OAuth2, token rotation and rate limits.
const result = await session.call("create_payment_link", { /* ... */ });

Install

$ npm install @codespar/mcp-clip

Quickstart

Add this entry to your claude_desktop_config.json (or any MCP-compatible client config).

{
  "mcpServers": {
    "clip": {
      "command": "npx",
      "args": [
        "-y",
        "@codespar/mcp-clip"
      ],
      "env": {
        "CLIP_AUTH_TOKEN": "<your_clip_auth_token>"
      }
    }
  }
}

After restart, your agent can call any of the 6 tools below — try create_payment_link first.

Environment variables · 2

Required to authenticate the server. Stored encrypted when using CodeSpar managed hosting.

Available tools · 6

Each tool is independent — your agent loads only what it needs to reduce context and response time.

Compatible frameworks

MCP is a protocol — any framework that speaks it can mount this server.

Frequently asked questions