Which API Key do I use?

You must use your Secret Key (Live or Test mode). Do not use the Publishable Key as it lacks permission to perform backend actions across the Ping++ network.

How do payment channels differ?

Each channel (e.g. `alipay_web`, `wx_pub`, `upacp`) corresponds to a specific environment (Web, WeChat Official Account, UnionPay App). Provide the appropriate channel string when creating a charge.

Does this handle RSA Signatures automatically?

For core operations covered by the standard MCP, API keys are sufficient. Operations requiring dedicated RSA enterprise signing may need custom webhook verifications.

Ping++ MCP Server for VS Code Copilot 7 tools — connect in under 2 minutes

Name: Ping++
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 7 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.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

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

Download Free Open SourceNo signup required

Classic Setup·json

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

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 Ping++ MCP Server

Empower your Agent to seamlessly manage Chinese payment ecosystems with Ping++, the ultimate multi-channel payment aggregator. Connect to WeChat Pay, Alipay, UnionPay, and multiple other networks through a single, elegant interface, replacing complex point-to-point integrations.

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

What you can do

Unified Charges — Create and manage transactions across any supported payment channel
Refund Management — Process and retrieve refunds across any network without learning specific gateway APIs
Customer Synchronization — Create and track customer profiles and saved payment methods across platforms

The Ping++ MCP Server exposes 7 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 Ping++ to VS Code Copilot via MCP

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

Create MCP config

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

Add the server config

Paste the JSON configuration above

Enable Agent mode

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

Start using Ping++

Ask Copilot: "Using Ping++, help me...". 7 tools available

Why Use VS Code Copilot with the Ping++ MCP Server

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

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

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

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

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

Ping++ + VS Code Copilot Use Cases

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

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

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

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

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

Ping++ MCP Tools for VS Code Copilot (7)

These 7 tools become available when you connect Ping++ to VS Code Copilot via MCP:

create_charge

Requires the order_no, amount, app ID, channel, currency, subject, and body. Create a new charge (payment request)

create_customer

Create a new Customer

create_refund

Create a refund for a specific charge

list_charges

List existing charges

list_customers

List existing Customers

retrieve_charge

Retrieve the details of an existing charge

retrieve_customer

Retrieve Customer details

Example Prompts for Ping++ in VS Code Copilot

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

"List the last 5 successful charges for my Ping++ app."

"Create a new refund of 100 CNY for charge ID ch_xyz789."

"Show me the details for customer ID cus_12345."

Troubleshooting Ping++ MCP Server with VS Code Copilot

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

MCP tools not available

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

Ping++ + VS Code Copilot FAQ

Common questions about integrating Ping++ MCP Server with VS Code Copilot.

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.

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.

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.

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.