2,500+ MCP servers ready to use
Vinkius

Copperx MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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 Copperx and 2,500+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "copperx": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Copperx
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 Copperx MCP Server

Integrate Copperx, the API-first crypto payment processor, directly into your AI workflow. Automate your web3 billing, manage customer subscriptions, and track payouts using natural language.

GitHub Copilot Agent mode brings Copperx data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

  • Payment Links — Create and manage checkout links for products or services instantly.
  • Subscription Management — List and monitor active recurring billing cycles.
  • Invoicing — Generate and track crypto invoices for your global customers.
  • Wallet Insights — Check your account balances across multiple chains and currencies.

The Copperx MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot 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 Copperx to VS Code Copilot via MCP

Follow these steps to integrate the Copperx MCP Server with VS Code Copilot.

01

Create MCP config

Create a .vscode/mcp.json file in your project root

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

04

Start using Copperx

Ask Copilot: "Using Copperx, help me..."10 tools available

Why Use VS Code Copilot with the Copperx MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Copperx through the Model Context Protocol.

01

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

02

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

03

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

04

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Copperx + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Copperx MCP Server delivers measurable value.

01

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

02

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

03

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

04

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Copperx MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Copperx to VS Code Copilot via MCP:

01

create_customer

Creates a new customer record with identity properties (email, name) for future payment associations. Register a new customer in Copperx

02

create_payment_link

Resolves product identity and pricing configuration to generate a unique payment URL. Create a new payment link for customers to pay

03

get_payment_details

Resolves granular transaction data, including blockchain tx hashes, fee breakdowns, and customer linkages. Get details for a specific payment intent

04

get_wallet_balance

Resolves real-time wallet balances across various supported cryptocurrencies and networks. Check current crypto wallet balances in Copperx

05

list_customers

Resolves customer identity properties such as unique identifiers, email addresses, and registered names. List all customers registered in Copperx

06

list_invoices

Resolves billing document properties including invoice numbers, totals, and payment status links. List all invoices generated

07

list_payment_links

Resolves link metadata including checkout URLs, pricing data, and usage statistics. List all payment links created

08

list_payments

Resolves payment identity properties including transaction IDs, amounts, currencies, and processing status across the crypto-payment boundary. List all payment intents in Copperx

09

list_payouts

Resolves disbursement data including payout IDs, destination wallet addresses, and settlement status. List all payouts processed

10

list_subscriptions

Resolves subscription properties including plan IDs, billing cycles, and current subscription state. List all active and past subscriptions

Example Prompts for Copperx in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Copperx immediately.

01

"Create a crypto payment link for 'Consulting Service' worth 100 USDC."

02

"Check my current account balances across all crypto wallets."

03

"List all active subscriptions and their monthly revenue."

Troubleshooting Copperx MCP Server with VS Code Copilot

Common issues when connecting Copperx to VS Code Copilot through the Vinkius, and how to resolve them.

01

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Copperx + VS Code Copilot FAQ

Common questions about integrating Copperx MCP Server with VS Code Copilot.

01

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.
02

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.
03

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.
04

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

Connect Copperx to VS Code Copilot

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.