How do I find my ZEGO AppID and ServerSecret?

Log in to the [ZEGO Admin Console](https://console.zego.im/), create or select a project, and you will find your AppID and ServerSecret in the project configuration or basic information section.

What is the SignatureNonce used for?

The SignatureNonce is a random string used to prevent replay attacks. This server automatically generates a fresh nonce for every request to ensure high security for your RTC management.

Can I kick a user from a specific room?

Yes! Use the `kick_room_user` tool with the target RoomId and UserId. You can also provide a custom message that the user will see when they are disconnected.

ZEGO / 即构科技 MCP Server for VS Code Copilot 8 tools — connect in under 2 minutes

Name: ZEGO / 即构科技
Availability: InStock
Author: Vinkius

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

Built by Vinkius GDPR 8 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 ZEGO / 即构科技 and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "zego": {
      "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 ZEGO / 即构科技 MCP Server

Empower your AI agent to orchestrate your real-time communication infrastructure with ZEGO (即构科技), the premier provider of global video and audio RTC services. By connecting ZEGO to your agent, you transform complex room management, stream control, and user status tracking into a natural conversation. Your agent can instantly retrieve active room lists, monitor user counts, force-stop media streams, and audit service usage statistics without you ever needing to navigate multiple technical dashboards. Whether you are building an automated moderation system for live rooms or monitoring cross-regional connectivity, your agent acts as a real-time RTC operations assistant, providing accurate and reliable results from a single, authorized source.

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

What you can do

Room Orchestration — List active rooms, retrieve detailed metadata, and monitor real-time user activity.
User Management — Track user status (online/offline), list members in specific rooms, and manage access (kick users).
Stream Control — Monitor active media streams and force-terminate unauthorized or problematic broadcasts.
Usage Auditing — Retrieve comprehensive audio and video duration statistics for specific time ranges.
Operational Insights — Monitor total online user counts and API connectivity status to ensure system-wide health.

The ZEGO / 即构科技 MCP Server exposes 8 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 ZEGO / 即构科技 to VS Code Copilot via MCP

Follow these steps to integrate the ZEGO / 即构科技 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 ZEGO / 即构科技

Ask Copilot: "Using ZEGO / 即构科技, help me...". 8 tools available

Why Use VS Code Copilot with the ZEGO / 即构科技 MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with ZEGO / 即构科技 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

ZEGO / 即构科技 + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the ZEGO / 即构科技 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

ZEGO / 即构科技 MCP Tools for VS Code Copilot (8)

These 8 tools become available when you connect ZEGO / 即构科技 to VS Code Copilot via MCP:

check_user_status

Check status of multiple users

get_online_count

Get total online user count

get_room_streams

List active streams in a room

get_room_users

List users in a room

get_usage_stats

Get service usage statistics

kick_room_user

Kick user from room

list_rooms

List active rooms

stop_media_stream

Force stop a stream

Example Prompts for ZEGO / 即构科技 in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with ZEGO / 即构科技 immediately.

"List all active rooms in our ZEGO project."

"Check the status for these users: 'user_01,user_02'."

"What is our video usage duration for the last 7 days?"

Troubleshooting ZEGO / 即构科技 MCP Server with VS Code Copilot

Common issues when connecting ZEGO / 即构科技 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.

ZEGO / 即构科技 + VS Code Copilot FAQ

Common questions about integrating ZEGO / 即构科技 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.