Funnels, retention and feedback themes, worked out from your Pendo data.

Product teams can work through usage, funnels, retention, guide results and feedback themes in one conversation, and with write tools on, act on what they find by building segments or logging feedback.

What it is

A remote MCP server Pendo runs, with a separate address for each data region: US, US1, EU, Japan and Australia. It works with Claude, Claude Code, ChatGPT, Cursor, Gemini CLI, Windsurf and other AI tools, and sees only the Pendo data your own account can see.

What you get

Visitors and accounts listed by segment, with their metadata, and one visitor's activity timeline
Page, Feature and Track Event usage: rankings, trends, funnels, retention curves and Product Engagement Score
Guide views, completions and poll responses, and guides published, staged, switched off or retargeted
NPS, CSAT, PMF and UMUX survey scores and individual responses
Session replay links and developer logs for a visitor or session
Customer feedback, ideas and AI-clustered feedback themes from Listen
Orchestrate journeys and emails with their performance metrics
Metrics on your own AI agents' conversations, use cases and detected issues
With write tools on: segments created, updated or deleted, feedback and ideas logged or updated, and draft Orchestrate journeys built

Requirements

A Pendo user login; you sign in with your Pendo credentials.
A subscription admin first turns on the Pendo MCP server under Settings > Subscription settings > AI access.
Write tools, which make changes in Pendo, are a separate switch the admin turns on.
Use the address for your data region, the same host you sign in to Pendo with.
Tools for Listen, Orchestrate, Agent Analytics and other Pendo products work only if your subscription has them.
In claude.ai and Claude Desktop, an admin adds Pendo as a connector for the organization before anyone else can connect.
Your sign-in lasts only as long as the shortest session limit across your Pendo subscriptions; reauthorize when it stops answering.

Setup effort

Admin enables it, then paste and authorize — add the endpoint to your client, then approve the OAuth consent screen