Connect Pendo MCP to your AI agents, securely.
One secured endpoint for every Pendo call your AI agents make, scoped per user, inspected, and logged.Try Pendo MCP now
What your agents can ask once Pendo MCP is connected.
Select the tools your AI agents can call
97 tools from the Pendo MCP schema.
Showing 97 tools
What Pendo MCP exposes
Pendo MCP groups its 97 tools into 8 categories, each with a suggested starting policy.
All 97 tools as JSON, ready to paste.
| Category | Covers | Access | Suggested policy |
|---|---|---|---|
| Discovery & Segments | Listing subscriptions and applications, searching Pages, Features, Track Events, accounts and clips, reading entity configurations and custom business objects, and reading, creating, updating and deleting saved segments | Read / Write | Discovery is read-only and the starting point for almost every other call. Segment changes are shared state: read-only users cannot create shared segments, editing someone else's needs the edit-shared-segment permission, and deleteSegment is permanent, so it warrants approval |
| Visitors & Sessions | Account and visitor metadata schemas, listing accounts and visitors by segment, building inline segments, per-visitor activity timelines, session replay links and summaries, and raw developer logs with HTTP request and response details | Read | This is where personal data concentrates. visitorActivity and devlogEvents return console and network logs, which can include whatever the instrumented app sent over the wire, so scope these to agents that genuinely need per-visitor detail and log which visitors were looked up |
| Product Analytics | Page, Feature and Track Event usage, app-level usage, product areas, Product Engagement Score, funnels, acquisition trends, retention curves and business object analytics | Read | Read-only aggregate analytics and the safest group to allow broadly. Results follow the user's existing Pendo permissions, so an agent sees what its user could already see in the dashboard |
| Agent Analytics | Key metrics, detected issues, clustered use cases, tracked issues and use cases, and detailed analysis of conversations for AI agents instrumented with Pendo Agent Analytics | Read | Read-only, but several tools return visitor prompt content from your own AI agent's conversations, which can carry whatever end users typed. Treat it as user content rather than metrics when deciding which agents get it |
| Guides & Surveys | Listing and inspecting in-app guides, poll responses, guide effectiveness and usage, categories, ordering and A/B experiments, changing a guide's state or audience segment, and NPS, CSAT, PMF and UMUX survey scores and responses | Read / Write | Mostly read-only. guideSetState can publish a draft guide to live users and guideSetSegment changes who sees it, so both change the product your customers see and should require approval |
| Feedback | Retrieving Listen feedback items, extracted insights, AI-clustered topics and ideas, creating and updating feedback items and ideas, and linking or unlinking ideas and feedback | Read / Write | Write tools here are opt-in and additive: they create, update and associate records rather than delete them. Log which items an agent creates so automated feedback stays distinguishable from customer-submitted feedback |
| Orchestrate | Reading Orchestrate journeys, steps, metrics, templates, emails and per-visitor journey and email state, and building draft journeys and emails: steps, conditions, audience, schedule, goal, name, description and HTML content | Read / Write | The largest group. The documented create tools produce drafts, and updateOrchestrateEmailContent refuses emails that are already sending, but setOrchestrateJourneySchedule and setOrchestrateJourneySegment decide when and to whom outbound email goes, so review any journey an agent builds before it is activated |
| Command Center | The Command Center SaaS and AI app portfolio with costs, licenses, renewals and usage, and updating an app's license count, annual cost, renewal date or notes | Read / Write | Off by default and enabled only through Pendo Support. Each update requires confirmation before it is applied; keep it with agents that manage software spend |
Connect Pendo MCP to your AI agent
Four steps, under ten minutes.
- 01
Sign in to NeuralTrust
Open the NeuralTrust platform, sign in and go to Getting started, then Connect your tools.
- 02
Choose your agent
When asked which agent you use, pick Claude Code, Codex, Cursor, Windsurf, Copilot or your own code.
- 03
Connect Pendo
Find Pendo in the tool list and connect it.
- 04
Connect your agent
Follow the steps on screen to add the config to your agent, then send the test prompt.
Permissions down to the single tool
You do not allow Pendo MCP or block it. You allow the exact tools each agent can call, one by one.
| Pendo MCP | 97 TOOLS AVAILABLE |
|---|---|
| Code review agent | 4 tools, read only |
| Issue triage bot | 9 tools |
| Platform team assistant | all 97 tools |
- Tool by toolConnecting the server is not the unit of access. Each tool is granted on its own.
- Default denyA tool you have not enabled is never exposed to the agent.
- Approval on writesTools that change or delete things can require a human to confirm.
Is Pendo MCP secure?
One endpoint instead of raw credentials. Every call is checked against policy and logged.
| AI agentsConnect through your MCP client configuration. | NeuralTrustApply controls based on your configuration. | Pendo MCP97 documented tools on the remote server, with a separate endpoint per region (US, US1, EU, Japan, Australia) over streamable HTTP. Users sign in with OAuth and the server inherits their Pendo permissions; non-interactive agents use a service account scoped to one subscription. Read-only and write tools are separate admin toggles under AI access. |
|---|---|---|
| Coding assistants | Connection & credentialsper user | Orchestrate25 tools |
| Internal copilots | Tool access policiesdeny by default | Product Analytics18 tools |
| Workflow automations | Request & response inspectioninline | Guides & Surveys13 tools |
| Compatible MCP clients | Activity monitoringalerts and logs | All other tools41 tools |
Use Pendo MCP with any AI agent framework
Setup guides for the tools your team already uses.
Claude CodeAdd Pendo MCP to Claude Code from the terminal
CursorUse Pendo MCP tools inside Cursor's agent
CodexConnect Pendo MCP to the OpenAI Codex CLI
WindsurfGive Windsurf's Cascade access to Pendo MCP
Gemini CLICall Pendo MCP from Gemini CLI prompts
Google AntigravityLet Antigravity agents work with Pendo MCP
GitHub CopilotUse Pendo MCP in Copilot agent mode
Claude EnterpriseRoll out Pendo MCP across your Claude workspace
Microsoft Copilot StudioAdd Pendo MCP as a tool for Copilot Studio agents
Open WebUIBring Pendo MCP tools into Open WebUI chats
LangChainLoad Pendo MCP tools into LangChain agents
HaystackPlug Pendo MCP into Haystack agent pipelines
Strands AgentsGive Strands agents Pendo MCP tools
Vercel AI SDKCall Pendo MCP from Vercel AI SDK apps
n8nUse Pendo MCP in n8n AI agent workflows
Common questions about running Pendo MCP through TrustGate.
Other MCP servers
More servers from the catalog.
)
Amplitude
Securely connect your AI agents to Amplitude through TrustGate: charts, dashboards, notebooks, cohorts, experiments, taxonomy and ad-hoc analytics queries, scoped per agent and logged.
45 toolsViewMixpanel
Securely connect your AI agents to Mixpanel through TrustGate: insights, funnels, flows, retention, cohorts, Lexicon and dashboards, scoped per agent and logged.
63 toolsViewPostHog
Securely connect your AI agents to PostHog through TrustGate: insights, SQL, dashboards, feature flags, experiments, error tracking and documentation, scoped per agent and logged.
1135 toolsViewStatsig
Securely connect your AI agents to Statsig through TrustGate: feature gates, experiments, dynamic configs, metrics, logs, layers, segments and parameter stores, scoped per agent and logged.
27 toolsView
Connect Pendo MCP instantly
Pick the tools, point your agent at TrustGate, and Pendo MCP is live: scoped, inspected, logged.