How to Use the Mercury MCP in Cursor

Q: How do I configure the Mercury MCP Server in Cursor?

Add the Vinkius server URL to your global Cursor /.cursor/mcp.json file. Once saved, your Cursor agent instantly gains access to your Mercury tools in Chat and Composer modes.

Write code using live financial data by connecting Mercury to Cursor for real-time sandbox testing and context.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Mercury MCP to Cursor

Create your Vinkius account to connect Mercury 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 Mercury with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Inject live banking context into Cursor

Stop writing financial integrations in Cursor against stale mock data or fake JSON stubs. By using this Mercury MCP Server, your Cursor agent pulls live account details using `list_accounts` directly into your active coding session. Your agent writes code against the actual shape of your real Mercury banking responses. When you work in Cursor's Agent mode, the editor runs `get_account` to verify Mercury API payloads on the fly. This means you catch Mercury schema mismatches inside Cursor rather than waiting for a production crash.

Real-time transaction debugging in your editor

Debugging Mercury payment reconciliation logic is notoriously painful when you cannot see the actual ledger inside Cursor. Cursor can execute `list_transactions` to pull your recent Mercury bank feed directly into the chat sidebar. This lets you compare your local database entries with real-world Mercury records without leaving your editor. If a specific Mercury payment fails to parse, your Cursor agent can call `get_transaction` to inspect the raw metadata. You fix the parsing bug inside Cursor immediately because the exact Mercury API response is sitting right next to your code.

Generate recipient logic with Cursor

Building Mercury payout workflows requires exact payload structures for vendor management in Cursor. Your Cursor agent can call `list_recipients` to understand how your existing Mercury payees are structured. This lets you generate accurate integration code inside Cursor without constantly reading the external Mercury API docs. You can even test payload generation by running `create_recipient` within your Cursor agent terminal. It speeds up your development loop because you verify the schema limits against your actual Mercury setup inside Cursor.

Setup guide

Set up Mercury 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 Mercury 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 Mercury transactions." If the MCP tools are loaded correctly, Cursor will call the Mercury tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "mercury-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 Mercury. 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 Mercury 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 Mercury MCP in Cursor

Add the Vinkius server URL to your global Cursor ~/.cursor/mcp.json file. Once saved, your Cursor agent instantly gains access to your Mercury tools in Chat and Composer modes.

No, the editor only exposes specific operational tools. Your Cursor agent can query balances via `get_treasury_balance` or draft payees with `create_recipient`, but it has no permission to change Mercury security settings.

Vinkius manages your Mercury credentials using a zero-trust architecture, passing a single secure endpoint token to Cursor. Your actual banking credentials are never exposed to Cursor or stored in your local code repository.

Yes, Agent mode allows Cursor to autonomously call Mercury tools like `list_payments` to help you write, test, and debug your financial automation scripts. You retain full visibility as the editor displays each Mercury tool call in the chat window.

All communication between Cursor and Mercury goes through an ephemeral, zero-trust V8 sandbox. Your private transaction details and treasury balances are processed strictly in-memory, leaving no traces behind once the Cursor tool call is completed.

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