Included as a product-experience intelligence surface whose hosted MCP can combine visitor and account metadata, Page and Feature usage, guide and poll performance, replay diagnostics, Listen feedback, Agent Analytics, and Orchestrate reporting, with administrator-opted Listen writes for creating feedback and ideas.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Subscriptions and applications; visitors and accounts with metadata; Pages, Features, Track Events, product areas and segments; guides, polls and NPS; replay links and development logs; feedback, insights, ideas and topics; AI agents, use cases and issues; Orchestrate journeys and emails.
Query account and visitor metadata, product activity, guide and poll metrics, NPS, Product Engagement Score, public segments, replay metadata and developer logs, Listen feedback and ideas, Agent Analytics, and Orchestrate journey or email configuration and aggregate performance, subject to product and tool limits.
When a subscription admin separately enables write tools, the current hosted server can create Listen feedback items and ideas. Read-only MCP must be enabled first, and the operation requires the relevant Pendo product and required identifiers or fields.
Interactive users authenticate through Pendo OAuth and inherit their Pendo roles and accessible subscriptions within one region. Service accounts use OAuth client credentials, are limited to one subscription and selected applications, require the API package and admin creation, and cannot cross regional boundaries.
A subscription admin separately controls read-only and write-tool toggles, with read required before write. Use the regional endpoint matching the subscription, preserve existing Pendo roles and application scope, keep visitor-facing agents away from shared service-account credentials, and require confirmation before creating feedback or ideas.
Pendo is regionally isolated and uses separate connections across US, US1, EU, Japan, and Australia. Official ChatGPT and Cursor connectors support only specified regions, while custom MCP can use other regional URLs. Product modules gate tools; service accounts require the API package; tool limits include 31-, 90-, 180-, or 367-day windows and result caps, and replay content itself is not exposed.
First-party access
Agent access
Support: Official MCP server
Read scope: Read enabled Pendo product areas through structured tools for metadata, aggregate activity, guides and polls, replay links and logs, feedback and ideas, agent performance, and Orchestrate configuration or metrics; respect each tool's product prerequisite, date range, aggregation level, and row cap.
Write scope: Admin-opted write tools currently create Listen feedback items and ideas. `createFeedbackItem` requires an App ID, title, description, and at least one Visitor ID or Account ID; product prerequisites and the live tool catalog still apply.
Authentication: Interactive OAuth through a Pendo login for users; OAuth client-credentials bearer tokens for service accounts. Connections and token endpoints are regional, and service-account access tokens last 60 minutes without refresh tokens.
Approval boundary: Keep Pendo's read and write toggles separate. Before creating a feedback item or idea, show the subscription, application, target visitor or account association, title, description, and product area, and require explicit confirmation; raw feedback, replay logs, and visitor metadata should remain read-only context.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Pendo ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
Official Pendo documentation confirms a remote MCP with administrator enablement and OAuth or service-account authentication.
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
All currently listed Pendo MCP tools are read-only across product usage, guides, replay, feedback, ideas and agent analytics.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
The external Pendo MCP server became generally available in April 2026.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
