How to Use the Mercury MCP in VS Code Copilot

Equip your team's VS Code Copilot with secure Mercury tools to build and audit payment workflows directly in the editor.

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 VS Code Copilot

Create your Vinkius account to connect Mercury to VS Code Copilot 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 VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Team-wide Mercury tools in VS Code Copilot

Share your Mercury financial context across your entire engineering team without sharing raw API keys in VS Code Copilot. By committing a shared configuration to your repository, every developer using VS Code Copilot can access this MCP Server instantly. Your developers can run `list_accounts` inside VS Code Copilot to verify Mercury ledger schemas without manual onboarding. This shared environment ensures everyone works with the same Mercury data shapes inside VS Code Copilot. Your team writes more accurate integration tests because Copilot uses real structures from `get_account` to suggest Mercury code.

Audit payments directly from the editor

Investigating Mercury payment discrepancies shouldn't require developers to request dashboard access when they have VS Code Copilot. VS Code Copilot can call `list_payments` to pull active Mercury transaction logs straight into the terminal panel. Developers resolve API bugs faster when they can see the Mercury payment history directly in VS Code Copilot. When a specific payout goes missing, the agent runs `get_transaction` inside VS Code Copilot to inspect the exact bank status. It bridges the gap between your backend code in VS Code Copilot and actual Mercury ledger states.

Validate recipient schemas inline

Writing clean payment routing code is difficult when Mercury recipient schemas are complex. Your developers can use VS Code Copilot to run `list_recipients` and inspect how payees are formatted in your actual Mercury account. This provides immediate, real-world context for writing Mercury validation scripts in VS Code Copilot. Copilot can also run `create_recipient` to test your automated onboarding pipelines inside VS Code Copilot. It ensures your code formats Mercury bank details correctly before you deploy to production.

Setup guide

Set up Mercury MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Mercury MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Mercury tools listed. Try asking: "List my recent Mercury transactions" and Copilot will invoke them automatically.

.vscode/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 VS Code Copilot

Create an mcp.json file inside your project's .vscode folder and commit it to your Git repository. Every team member with the VS Code Copilot extension will automatically get access to the Mercury tools using your shared Vinkius token.

No, actual fund transfers are impossible through this VS Code Copilot setup. The agent can only draft recipients using `create_recipient` or pull read-only data, while actual Mercury capital movement requires manual approval.

You need VS Code version 1.96 or higher with the Copilot Chat extension enabled. This setup supports the full suite of Mercury tools, including `get_treasury_balance` and `list_statements` inside VS Code.

Yes, you can configure granular access policies within your Vinkius dashboard for VS Code Copilot. This allows you to restrict Copilot to read-only tools like `list_transactions` while blocking write tools entirely.

Your Mercury banking details and transaction records are protected by enterprise-grade encryption inside VS Code Copilot. Vinkius processes all API requests in ephemeral V8 isolates, meaning your sensitive financial data is never stored, cached, or used to train models.

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