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.

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

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

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "pendo": {
      "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 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.

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.

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.

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

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

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

Why Use VS Code Copilot with the Pendo MCP Server

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

Pendo + VS Code Copilot Use Cases

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

Pendo MCP Tools for VS Code Copilot (10)

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

get_pendo_account

Get details for a specific account

get_pendo_guide

Get details for a specific guide

get_pendo_guide_metrics

Get performance metrics for a guide

get_pendo_visitor

Get details for a specific visitor

list_pendo_applications

List applications tracked in the Pendo subscription

list_pendo_features

List tagged features

list_pendo_guides

) defined in Pendo. List Pendo guides

list_pendo_metadata_schema

List metadata schema definitions

list_pendo_pages

List tagged pages

list_pendo_segments

List saved user segments

Example Prompts for Pendo in VS Code Copilot

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

"List all active guides in my Pendo account."

"Get metadata for visitor 'user@example.com'."

"Show me the performance metrics for the guide 'guide_98765'."

Troubleshooting Pendo MCP Server with VS Code Copilot

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

Pendo + VS Code Copilot FAQ

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