Bring Payment Gateway
to Cursor
Learn how to connect Payrexx to Cursor and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Payrexx MCP Server?
Connect your Payrexx account to any AI agent and take full control of your payment orchestration and checkout flows through natural conversation. Payrexx is the leading payment provider in Switzerland and Europe, and this integration allows you to create payment gateways, monitor real-time transaction metadata, and manage recurring subscriptions directly from your chat interface.
What you can do
- Gateway & Link Orchestration — Create custom payment gateways and multi-use payment links programmatically to ensure your sales flow is always synchronized.
- Transaction Lifecycle Management — Access and monitor real-time transaction statuses and retrieve detailed financial metadata directly from the AI interface to track revenue health.
- Subscription & Recurring Control — Manage recurring billing cycles and list active subscriptions via natural language to drive better customer retention.
- Payout & Invoice Oversight — Access organizational payouts and list invoices to maintain a clear overview of your cash flow using simple AI commands.
- Operational Monitoring — Track system responses and manage webhook metadata to ensure your automation workflows are always optimized.
How it works
1. Subscribe to this server
2. Enter your Payrexx Instance Name and API Secret from your merchant settings
3. Start managing your payment operations from Claude, Cursor, or any MCP-compatible client
No more manual status checks in the dashboard. Your AI acts as a dedicated payments coordinator or finance coordinator.
Who is this for?
- Swiss & European Merchants — quickly retrieve payment summaries and monitor transaction status without switching apps.
- Finance Operations Teams — automate the retrieval of payout metadata and track organizational billing via natural conversation.
- Developers — integrate real-time payment data and gateway management directly within the chat.
Built-in capabilities (11)
Verify API connectivity and signature
Create a new payment gateway (hosted payment page)
Get details of a specific gateway
Get details of a specific transaction
List all payment gateways
List invoices
List available payment methods
List payouts
List recurring subscriptions
List recent transactions
List configured webhooks
Why Cursor?
Cursor's Agent mode turns Payrexx into an in-editor superpower. Ask Cursor to generate code using live data from Payrexx and it fetches, processes, and writes. all in a single agentic loop. 11 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
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
Payrexx in Cursor
Payrexx and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Payrexx to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Payrexx in Cursor
The Payrexx 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. All 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Payrexx for Cursor
Every tool call from Cursor to the Payrexx MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the status for a specific transaction by its ID?
Yes! Use the get_transaction tool with the Transaction ID. Your agent will respond with complete metadata, including payment method, currency, amount, and final status in seconds.
How do I find my Payrexx API Secret and Instance Name?
Log in to your Payrexx merchant dashboard, navigate to Settings > API, and you will find your unique secret key and instance name (e.g., yourname.payrexx.com) there.
Does this work for recurring payments?
Absolutely. You can use the list_subscriptions tool to monitor active recurring billing cycles and orchestrate multi-use gateways for recurring customer payments.
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.
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.