Bring Customer Success
to VS Code Copilot
Learn how to connect Zengain to VS Code Copilot and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Zengain MCP Server?
Connect your Zengain (Nalpeiron Growth Platform) account to any AI agent and simplify your customer success and usage analytics workflows through natural conversation.
What you can do
- Product Lifecycle — List all registered products and retrieve detailed configuration metadata
- User Engagement — Query product users, inspect their profiles, and calculate real-time health scores
- Usage Analytics — Get high-level analytics summaries and track custom events to monitor feature adoption
- KPM Tracking — Monitor Key Product Milestones to identify successful onboarding and churn risks
- System Monitoring — List configured webhooks to understand your integration data flow
How it works
1. Subscribe to this server
2. Enter your Zengain Tenant ID and API Key
3. Start managing your customer success resources from Claude, Cursor, or any MCP-compatible client
Built-in capabilities (10)
Get analytics summary
Get customer health score
Get details for a specific product
Get details for a specific user
List tracking events
List Key Product Milestones
List Zengain products
List product users
List configured webhooks
Track a custom event
Why VS Code Copilot?
GitHub Copilot Agent mode brings Zengain 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.
- —
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
Zengain in VS Code Copilot
Zengain and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Zengain to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Zengain in VS Code Copilot
The Zengain 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. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Zengain for VS Code Copilot
Every tool call from VS Code Copilot to the Zengain MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I calculate a customer's health score using my AI agent?
Yes! Use the get_health_score tool by providing the User ID. The agent will retrieve the real-time engagement score from Zengain.
How do I see high-level usage summary for a specific product?
Use the get_analytics_summary tool. You can optionally provide a Product ID to filter the metrics for that specific offering.
Is it possible to track a new custom event through this integration?
Yes, use the track_event action. Provide the User ID and the Event Name to record engagement data programmatically.
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.
MCP tools not available
Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.