Bring Product Analytics
to Claude Desktop
Learn how to connect Pendo to Claude Desktop and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Pendo MCP Server?
Connect your Pendo account to any AI agent and take full control of your product orchestration and user engagement through natural conversation. Pendo provides a world-class platform for understanding how users interact with your software, and this integration allows you to retrieve usage metadata, manage in-app guides, and run complex aggregations directly from your chat interface.
What you can do
- Usage & Analytics Orchestration — Run powerful aggregations programmatically to understand feature adoption and user behavior via natural language.
- Metadata & Profile Control — Update custom visitor and account metadata directly from the AI interface to ensure your CRM and success data are always synchronized.
- Guide Lifecycle Management — List all managed guides and retrieve detailed metadata to maintain a clear overview of your in-app messaging strategy.
- Feature & Page Intelligence — Access and monitor tagged features and pages to track engagement and identify bottlenecks using simple AI commands.
- Operational Monitoring — Track system responses and manage regional data centers (US, EU, JPN, AU) to ensure your analytics pipeline is always optimized.
How it works
1. Subscribe to this server
2. Enter your Pendo Integration Key and regional Base URL from your settings
3. Start managing your product analytics from Claude, Cursor, or any MCP-compatible client
No more manual exporting of usage reports or context switching for user profiles. Your AI acts as a dedicated product analyst or customer success manager.
Who is this for?
- Product Managers — quickly retrieve feature adoption summaries and monitor guide performance without switching apps.
- Customer Success Teams — automate the update of account health metadata and track visitor activity via natural conversation.
- Growth Marketers — streamline the retrieval of user segments and monitor engagement trends directly within the chat.
Built-in capabilities (11)
Get details for a specific account
Get details for a specific guide
Get details for a specific visitor
List tagged features
List all in-app guides
List tagged pages
List all analytics reports
List all user segments
Perform complex analytics and grouping
Update custom account metadata
Update custom visitor metadata
Why Claude Desktop?
Claude Desktop is the definitive way to connect Pendo to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 11 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Pendo in Claude Desktop
Pendo and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Pendo to Claude Desktop 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 Claude Desktop
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 11 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Claude Desktop 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 Claude Desktop
Every tool call from Claude Desktop 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
Can my AI automatically run a data aggregation for unique visitors?
Yes! Use the run_aggregation tool. Provide the aggregation logic (following Pendo's JSON syntax), and your agent will respond with complete metadata and result sets in seconds.
Where do I find my Pendo Integration Key?
Log in as an Admin, navigate to Settings > Integrations, select the Integration Keys tab, and create a new key with the required permissions.
Does this work with EU or Japan instances?
Yes! During setup, you can specify your regional base URL (e.g., app.eu.pendo.io or app.jpn.pendo.io) to ensure the MCP server connects to the correct data center.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.