Bring Product Analytics
to Cursor
Learn how to connect Pendo to Cursor 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 Cursor?
Cursor's Agent mode turns Pendo into an in-editor superpower. Ask Cursor to generate code using live data from Pendo and it fetches, processes, and writes. all in a single agentic loop. 11 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Pendo in Cursor
Pendo and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Pendo to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.