Bring Product Adoption
to VS Code Copilot
Learn how to connect Pendo 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.
GDPR Free for Subscribers
What is the Pendo MCP Server?
Connect your Pendo subscription to any AI agent and take full control of your product adoption and user engagement workflows through natural conversation.
What you can do
- Guide Management — List all in-app guides and retrieve detailed metadata and performance metrics.
- User & Account Insights — Look up detailed profiles for visitors and accounts to understand their journey.
- Product Tagging Auditing — List defined pages and features to verify your product instrumentation.
- Metadata Schema Discovery — Retrieve schemas for visitor and account metadata to understand available data points.
- Segment Overview — List saved user segments to maintain visibility over your audience targeting.
How it works
1. Subscribe to this server
2. Enter your Pendo Integration Key
3. Start optimizing your product experience from Claude, Cursor, or any MCP client
Who is this for?
- Product Managers — quickly check guide performance or verify if a feature is correctly tagged.
- Customer Success Managers — lookup visitor activity and account metadata during high-pressure support cases.
- Growth Engineers — audit segments and metadata schemas while implementing new tracking events.
Built-in capabilities (10)
Get details for a specific account
Get details for a specific guide
Get performance metrics for a guide
Get details for a specific visitor
List applications tracked in the Pendo subscription
List tagged features
) defined in Pendo. List Pendo guides
List metadata schema definitions
List tagged pages
List saved user segments
Why VS Code Copilot?
GitHub Copilot Agent mode brings Pendo 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
Pendo in VS Code Copilot
Pendo and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Pendo 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 Pendo in VS Code Copilot
The Pendo 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
Pendo for VS Code Copilot
Every tool call from VS Code Copilot to the Pendo MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my Pendo Integration Key?
In Pendo, navigate to Settings > Integrations. There you can find or generate your Integration Key for API access.
Can I see real-time statistics for my guides?
Yes! Use the get_pendo_guide_metrics tool with a Guide ID to retrieve live data on views, clicks, and completion rates.
Does this support looking up individual user metadata?
Absolutely. Use the get_pendo_visitor tool to retrieve all identified properties, account association, and activity history for a specific user ID.
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.