How do I find my GrowingIO Project ID and Client ID?

Log in to your GrowingIO portal, go to [Project Configuration] -> [Project Info]. You will find your Project ID (ai) and Client ID (Public Key) there.

Where do I generate the API Token?

In your GrowingIO portal, navigate to [Project Configuration] -> [API Token Management] to generate a long-term API Token for this server.

Can I query quantitative metrics through the agent?

Yes. Use the `get_metrics` tool with a JSON query definition. This allows your agent to retrieve specific data points like DAU, retention rates, or custom conversion metrics.

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

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

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "growingio": {
      "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 GrowingIO MCP Server

Empower your AI agent to orchestrate your product analytics and user behavioral data with GrowingIO, the premier analytical platform in China. By connecting GrowingIO to your agent, you transform complex event tracking, user segmentation, and metric analysis into a natural conversation. Your agent can instantly list tracked events, retrieve detailed user segment metadata, monitor conversion funnels, and execute quantitative metric queries without you ever needing to navigate the comprehensive GrowingIO web interface. Whether you are conducting a product health audit or monitoring real-time campaign performance, your agent acts as a real-time data analyst assistant, keeping your product data accurate and your growth moving.

GitHub Copilot Agent mode brings GrowingIO 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

Event Orchestration — List and retrieve detailed metadata for all tracked behavioral events in your project.
User Segmentation — Browse and monitor user segments to identify high-value cohorts and behavioral patterns.
Metric Querying — Execute quantitative queries to retrieve specific performance metrics via natural language.
Funnel Auditing — Retrieve detailed configuration and data for conversion funnels to identify drop-off points.
Campaign Insights — Browse tracked advertising campaigns and identify successful growth drivers.

The GrowingIO 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 GrowingIO to VS Code Copilot via MCP

Follow these steps to integrate the GrowingIO 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 GrowingIO

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

Why Use VS Code Copilot with the GrowingIO MCP Server

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

GrowingIO + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the GrowingIO 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

GrowingIO MCP Tools for VS Code Copilot (10)

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

get_event

Get event details

get_funnel

Get conversion funnel details

get_metrics

Query project metrics

get_project_info

Get project metadata

get_segment_users

Get users in a segment

list_ads

List advertising campaigns

list_events

List project events

list_log_sources

). List data log sources

list_segments

List user segments

list_variables

List tracked variables

Example Prompts for GrowingIO in VS Code Copilot

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

"List all user segments in GrowingIO."

"Show me the conversion funnel for 'Checkout Flow'."

"Query the DAU for the last 7 days."

Troubleshooting GrowingIO MCP Server with VS Code Copilot

Common issues when connecting GrowingIO 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.

GrowingIO + VS Code Copilot FAQ

Common questions about integrating GrowingIO 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.