How to Use the Blink Payment MCP in Cursor

Q: How do I add the Blink Payment MCP Server to Cursor?

Create a .cursor/mcp.json file in your project root and add the MCP config under the mcpServers key. Once saved, Cursor will immediately recognize the tools in your chat sidebar.

Q: Can Cursor write code using real Blink Payment responses?

Yes, Cursor runs tools like listpayments in Agent mode to fetch real-time payloads. The AI then uses these exact JSON structures to write highly accurate integration code.

Q: How does Cursor handle refunds using Blink Payment?

The editor uses the refundpayment tool to trigger refunds directly from your Cursor chat panel. This lets you verify refund webhook behavior without manual dashboard intervention.

Q: Can I create customers while testing my app?

Yes, you can ask the editor to run createcustomer to insert test records. This helps you verify that your billing integration handles customer creation correctly.

Generate working code in Cursor using live Blink Payment data to test checkout flows and manage customers.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Blink Payment MCP to Cursor

Create your Vinkius account to connect Blink Payment to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Blink Payment with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build checkout features in Cursor with live payment data

The `create_payment_intent` tool fetches actual transaction tokens and injects them directly into your Cursor editor. Having live API responses means you can write accurate frontend code that handles real payment states. The editor gets exact payloads from `get_payment` so your error handling and success pages work correctly on the first run.

Generate and test paylinks inside your editor

The `create_paylink` tool generates live sandbox URLs right inside your Cursor coding workspace. With this MCP Server, you can tell Cursor to run `list_paylinks` or check specific statuses with `get_paylink` to debug your database synchronization. It cuts down your context-switching time to zero.

Sync customer profiles directly in your codebase

The `list_customers` tool pulls the exact JSON structure of your user profiles directly into Cursor using the MCP protocol. You can even test signup webhooks by asking the editor to execute `create_customer` or look up a specific user with `get_customer`. This gives you instant feedback on how your backend handles new registration events.

Setup guide

Set up Blink Payment MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Blink Payment MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Blink Payment transactions." If the MCP tools are loaded correctly, Cursor will call the Blink Payment tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

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

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Blink Payment. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Blink Payment now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Blink Payment MCP in Cursor

Create a `.cursor/mcp.json` file in your project root and add the MCP config under the `mcpServers` key. Once saved, Cursor will immediately recognize the tools in your chat sidebar.

Yes, Cursor runs tools like `list_payments` in Agent mode to fetch real-time payloads. The AI then uses these exact JSON structures to write highly accurate integration code.

The editor uses the `refund_payment` tool to trigger refunds directly from your Cursor chat panel. This lets you verify refund webhook behavior without manual dashboard intervention.

Yes, you can ask the editor to run `create_customer` to insert test records. This helps you verify that your billing integration handles customer creation correctly.

All interactions with payment intents and customer records are protected because Vinkius runs this MCP Server in an isolated sandbox. Your API keys are encrypted, and data never persists on disk, keeping your financial transactions private.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript