Pendo MCP honesty matrix — Listen/Ideas/Guides/Orchestrate writes inside Pendo vs no create_github_issue / create_pr / file:line
Pendo's MCP product page (pendo.io/product/mcp/) markets "Connect Product Analytics to Any AI Tool" — turn any AI tool into a product expert with usage data, visitor behavior, and customer context wherever you work.
The Help Center article "Pendo MCP tools for AI agents" (last updated September 28, 2026) is explicit that most tools are read-only, but some write data back to Pendo — Listen (createFeedbackItem, createIdeaItem, updateIdeaItem, updateFeedbackItem, linkIdeaAndFeedback, unlinkIdeaFeedback), Segments (createSegment, updateSegment, deleteSegment), Guides (guideSetState, guideSetSegment), Orchestrate (createOrchestrateJourneyFromTemplate, createOrchestrateJourneyFromJson, setOrchestrateJourneySchedule, updateOrchestrateEmailContent), and Command Center (updateCommandCenterApp). That surface stays inside Pendo. There is no create_github_issue / create_tracker_issue / create_pr / open_pr / codebase / git write / React file:line tool on the published list. Feedback DevTools is honest about a different surface: create_github_issue / create_tracker_issue / mark_feedback_resolved plus source-mapped local-agent context with file:line. We do not claim server-side auto-opened or auto-merged PRs. Zero Pendo product integration ships in FDT today.
Feedback DevTools is our product. Pendo MCP marketing from https://www.pendo.io/product/mcp/; published tools from https://support.pendo.io/hc/en-us/articles/42476316360731 (Pendo MCP tools for AI agents — last updated September 28, 2026) — lastChecked September 29, 2026 ~2:30pm Asia/Jerusalem. Please verify before purchase.
Feedback DevTools vs Pendo MCP
| Feedback DevTools | Pendo MCP | |
|---|---|---|
| Positioning | Capture + create_github_issue / create_tracker_issue / mark_feedback_resolved + local-agent file:line | Product-analytics / Listen / Guides / Orchestrate MCP — markets "Connect Product Analytics to Any AI Tool"; writes stay inside Pendo |
| Published MCP write tools (Sep 28, 2026) | create_github_issue · create_tracker_issue · mark_feedback_resolved + local-agent file:line | Listen: createFeedbackItem · createIdeaItem · updateIdeaItem · updateFeedbackItem · linkIdeaAndFeedback · unlinkIdeaFeedback; Segments: createSegment · updateSegment · deleteSegment; Guides: guideSetState · guideSetSegment; Orchestrate: createOrchestrateJourneyFromTemplate · createOrchestrateJourneyFromJson · setOrchestrateJourneySchedule · updateOrchestrateEmailContent; Command Center: updateCommandCenterApp |
| Marketing claim | N/A — FDT does not market analytics-MCP as a GitHub ship path; create_* tickets + local-agent | "Connect Product Analytics to Any AI Tool" (pendo.io/product/mcp/) |
| create_github_issue / create_pr / file:line | Yes create_github_issue / create_tracker_issue + capture-time file:line; no server-side create_pr | No dedicated create_github_issue / create_pr / open_pr / React file:line / git write tool on the Sep 28, 2026 Help Center list |
| Server-side auto-open / auto-merge PRs | No — we do not claim server-side auto PRs | No — published write tools mutate Pendo Listen / Segments / Guides / Orchestrate / Command Center, not GitHub PRs |
| Source maps / file:line | Yes — capture-time React component + file:line | Product usage, Listen feedback/ideas, guides, Orchestrate metrics — Pendo objects, not React component file:line |
| Pendo in FDT today | Zero — no Pendo product integration ships in Feedback DevTools today | First-party MCP into Pendo data + in-Pendo writes |
| Pricing shape | Unlimited free collection; Pro $9/mo per project | Paid Pendo subscription (admin enables MCP); not a separate $9 MCP SKU |
Pendo MCP marketing quote verified on pendo.io/product/mcp/; tool list + write tools verified on support.pendo.io/hc/en-us/articles/42476316360731 (last updated September 28, 2026) — lastChecked September 29, 2026 ~2:30pm Asia/Jerusalem
Where Pendo MCP is genuinely strong
Credit where due — Pendo MCP is a real product-analytics + Listen unlock if:
- You already run Pendo and want AI agents in Claude / Cursor / ChatGPT / Copilot to query visitors, accounts, pages/features, guides, sentiment, Session Replay metadata, Listen feedback/ideas, and Orchestrate journeys without dashboard hopping.
- Writing feedback items, ideas, segments, guide state, or Orchestrate journey drafts back into Pendo from the agent is the workflow — not opening a GitHub issue from MCP.
- Natural-language product questions ("Which features dropped usage last month?", "Cluster Listen feedback about onboarding", "Publish this guide") are the primary surface.
Where Feedback DevTools is more honest about create_* / ship
- Marketing vs published tools. pendo.io/product/mcp/ markets "Connect Product Analytics to Any AI Tool"; the Sep 28, 2026 Help Center tool list publishes real writes inside Pendo (Listen / Segments / Guides / Orchestrate / Command Center) and no create_github_issue / create_pr / React file:line (lastChecked September 29, 2026 ~2:30pm Asia/Jerusalem). We quote both so buyers are not surprised.
- Tickets with file:line. create_github_issue and create_tracker_issue open GitHub/Linear tickets whose bodies carry component + file:line from capture. Pendo's published write tools create/update Listen feedback and ideas, segments, guide state, and Orchestrate journeys — they do not open GitHub issues or PRs with React file:line.
- Local-agent path. The same context is handed to your coding agent; a PR, if any, is that agent's git workflow — not a Pendo MCP PR tool. FDT does not claim server-side auto-open or auto-merge.
- Capture-time source maps. Every item pins the React component and file path:line so the agent starts from a known path instead of rediscovering from a Pendo Page/Feature ID or Listen idea alone.
- Zero Pendo in FDT today. This foil is honesty about surfaces — Feedback DevTools does not ship a Pendo connector; it ships create_github_issue / create_tracker_issue + local-agent file:line.
Pricing shape (not the foil) (as of September 29, 2026)
- Pendo: paid Pendo subscription with admin-enabled MCP (sources: pendo.io/product/mcp/; support.pendo.io/hc/en-us/articles/42476316360731)
- Feedback DevTools: Free (unlimited collection) · Pro $9/mo per project (source: feedback-devtools.com/pricing)
MCP honesty is about capability claims, not sticker shock — FDT Pro is $9/mo per project vs Pendo as a full product-analytics / Listen / Guides suite with MCP as a connector that can write back into Pendo.
Who should pick which?
- Choose Pendo MCP if your evidence archive is Pendo product analytics, Listen, Guides, and Orchestrate and you want AI agents to query — and write feedback/ideas/segments/guide state/journeys back into — Pendo.
- Choose Feedback DevTools if you want visual feedback with file:line on capture, MCP tools that create GitHub/Linear tickets (create_github_issue / create_tracker_issue), and a local-agent fix path — without reading "Connect Product Analytics to Any AI Tool" or in-Pendo Listen/Ideas writes as a published create_github_issue / create_pr / file:line tool.
Frequently asked questions
What does Pendo MCP marketing claim?
Per https://www.pendo.io/product/mcp/ (lastChecked September 29, 2026 ~2:30pm Asia/Jerusalem): the page is titled "Connect Product Analytics to Any AI Tool" and positions Pendo MCP as turning any AI tool into a product expert with usage data, visitor behavior, and customer context in Claude, ChatGPT, Cursor, and more.
What can Pendo MCP write (Sep 28, 2026 tool list)?
Per https://support.pendo.io/hc/en-us/articles/42476316360731 (last updated September 28, 2026): while most tools are read-only, write tools include Listen createFeedbackItem / createIdeaItem / updateIdeaItem / updateFeedbackItem / linkIdeaAndFeedback / unlinkIdeaFeedback; Segments createSegment / updateSegment / deleteSegment; Guides guideSetState / guideSetSegment; Orchestrate createOrchestrateJourneyFromTemplate / createOrchestrateJourneyFromJson / setOrchestrateJourneySchedule / updateOrchestrateEmailContent; and Command Center updateCommandCenterApp. Those writes stay inside Pendo.
Can Pendo MCP create GitHub issues, pull requests, or React file:line tickets?
No create_github_issue / create_tracker_issue / create_pr / open_pr / codebase / git write / React file:line tool is on the published Sep 28, 2026 Help Center list (support.pendo.io/hc/en-us/articles/42476316360731; lastChecked September 29, 2026 ~2:30pm Asia/Jerusalem). A GitHub ticket or PR, if any, is the coding agent using Pendo context — not those MCP tools. Feedback DevTools foils with create_github_issue / create_tracker_issue + local-agent path and does not claim server-side auto-open or auto-merge. Distinct from Contentsquare#79 / Dovetail#78 / FullStory#77.
Try Feedback DevTools free — create_github_issue / create_tracker_issue with file:line, no server-side auto-PR or "Connect Product Analytics to Any AI Tool" GitHub-ship claims.