How do I find my Tingyun API Key and Secret?

Log in to your Tingyun console, go to [Account Management] → [API], and you will find your unique API Key and Secret Key there. Ensure you have the necessary permissions enabled.

Can I query specific metric data through this server?

Yes. Use the `get_metrics` tool with the application ID and a comma-separated list of metric names. Your agent will retrieve the data points for the specified metrics.

Is it possible to monitor frontend performance?

Yes! Use the `list_browser_apps` tool to access performance data from Tingyun RUM (Real User Monitoring) for your web and browser applications.

Tingyun / 听云 MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Tingyun / 听云
Availability: InStock
Author: Vinkius

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

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.

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

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "tingyun": {
      "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 Tingyun / 听云 MCP Server

Empower your AI agent to orchestrate your entire digital performance stack with Tingyun (听云), the premier APM and observability platform. By connecting Tingyun to your agent, you transform complex application monitoring, incident response, and performance auditing into a natural conversation. Your agent can instantly list monitored applications, retrieve real-time performance summaries, browse active alerts, and query specific metric data without you ever needing to navigate the Tingyun console. Whether you are troubleshooting a production bottleneck or auditing system health across a distributed architecture, your agent acts as a real-time site reliability assistant, keeping your performance data accurate and your systems responsive.

GitHub Copilot Agent mode brings Tingyun / 听云 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

Application Orchestration — List all APM applications and retrieve detailed health and performance summaries.
Incident Control — Monitor active alerts and browse alert policies to identify and respond to performance issues.
Infrastructure Auditing — List application instances, external service calls, and database dependencies.
Metric Querying — Retrieve specific metric data points for applications to analyze trends and anomalies.
User Experience Insights — Browse Real User Monitoring (RUM) browser applications to audit frontend performance.

The Tingyun / 听云 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 Tingyun / 听云 to VS Code Copilot via MCP

Follow these steps to integrate the Tingyun / 听云 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 Tingyun / 听云

Ask Copilot: "Using Tingyun / 听云, help me...". 10 tools available

Why Use VS Code Copilot with the Tingyun / 听云 MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Tingyun / 听云 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

Tingyun / 听云 + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Tingyun / 听云 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

Tingyun / 听云 MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Tingyun / 听云 to VS Code Copilot via MCP:

get_account_info

Get account metadata

get_app_summary

Get application summary

get_metrics

Query metric data

list_alert_policies

List alert policies

list_alerts

List active alerts

list_app_instances

List application instances

list_applications

List APM applications

list_browser_apps

List RUM browser applications

list_databases

List monitored databases

list_external_services

List external service calls

Example Prompts for Tingyun / 听云 in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Tingyun / 听云 immediately.

"List all applications monitored by Tingyun."

"Show me the performance summary for application ID 12345."

"Check for any critical alerts in Tingyun from today."

Troubleshooting Tingyun / 听云 MCP Server with VS Code Copilot

Common issues when connecting Tingyun / 听云 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.

Tingyun / 听云 + VS Code Copilot FAQ

Common questions about integrating Tingyun / 听云 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.