Can I automatically refund payments without ever navigating to the Clip website?

Yes. The `refund_transaction` interface executes server-side cryptographic voiding. Pass the definitive transaction ID alongside an optional amount override, and the refund logic routes directly through Clip's banking partners unconditionally.

Are the payment links generated permanent or do they have expiration windows?

By default, Payment links created via this endpoint remain actively valid until either paid successfully or explicitly halted. You can seamlessly use the `cancel_payment_link` tool to kill rogue links manually blocking external vulnerability loopholes.

Can the agent check if physical POS terminals are active and connected to my account?

Yes. The `list_terminals` endpoint fetches the fleet array directly from Clip servers. It outputs device IDs mapped to your registry ensuring no unauthorized POS physical readers are leeching payments stealthily.

Clip API MCP Server for Cursor 10 tools — connect in under 2 minutes

Name: Clip API
Availability: InStock
Author: Vinkius

docs.cursor.com/context/model-context-protocol

Built by Vinkius GDPR 10 Tools IDE

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Clip API and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "clip-api": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Clip API MCP Server

Directly empower your intelligent agents with the Clip API, the undisputed champion of point-of-sale and card payment gateways across Mexico. Bypass clunky merchant dashboards by commanding 10 specialized financial tools built to execute transactions, force refunds, and reconcile bulk backend settlements securely through plain text.

Cursor's Agent mode turns Clip API into an in-editor superpower. Ask Cursor to generate code using live data from Clip API and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

What you can do

Payment Link Generation — Programmatically spin up highly secure payment links instantly firing off collection demands mapped directly to specific user workflows without manual UI clicks.
Transaction Auditing — Track pending authorizations scanning exact balances sniffing out potential fraud drops analyzing transaction statuses aggressively.
Automated Reconciliations — Pull bulk settlement reports extracting clean matrices charting precisely when cash pipelines hit your registered banks.
Inventory & Subscription — Manage deep catalog arrays syncing SKUs and dictating heavy recurring billing cycles charging Mexican cards passively.

The Clip API MCP Server exposes 10 tools through the Vinkius. Connect it to Cursor in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Clip API to Cursor via MCP

Follow these steps to integrate the Clip API MCP Server with Cursor.

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"

Add the server config

Paste the JSON configuration above into the mcp.json file that opens

Save the file

Cursor will automatically detect the new MCP server

Start using Clip API

Open Agent mode in chat and ask: "Using Clip API, help me...". 10 tools available

Why Use Cursor with the Clip API MCP Server

Cursor AI Code Editor provides unique advantages when paired with Clip API through the Model Context Protocol.

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

Clip API + Cursor Use Cases

Practical scenarios where Cursor combined with the Clip API MCP Server delivers measurable value.

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Clip API MCP Tools for Cursor (10)

These 10 tools become available when you connect Clip API to Cursor via MCP:

add_product_to_catalog

Add a new item to the Clip Point of Sale catalog

cancel_payment_link

Void an active payment link

create_payment_link

Generate a Clip payment link to charge customers via card

create_subscription_plan

Build a recurring billing cycle charging clients periodically

get_balance_summary

Retrieve cash balance awaiting settlement

get_settlement_reports

Fetch detailed historical settlement reports

get_transaction_status

Retrieve the status of a payment transaction

list_products_catalog

Pull the complete inventory catalog registered in Clip

list_terminals

List all registered physical POS Clip terminals

refund_transaction

Omit amount for full refund. Execute a full or partial refund for a settled transaction

Example Prompts for Clip API in Cursor

Ready-to-use prompts you can give your Cursor agent to start working with Clip API immediately.

"Generate a new custom MXN payment link exactly for 450.50 referenced as invoice #X-99T."

"Refund the latest transaction specifically identified as Txn_88Z to its origin card fully."

"Calculate my comprehensive real cash balance available anticipating the incoming bulk settlements today blindly."

Troubleshooting Clip API MCP Server with Cursor

Common issues when connecting Clip API to Cursor through the Vinkius, and how to resolve them.

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

Clip API + Cursor FAQ

Common questions about integrating Clip API MCP Server with Cursor.

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.