# Pendo vs RudderStack MCP (slim)

> RudderStack MCP scores 54.7 (C) to Pendo's 44 (E) for analytics queries. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/pendo-vs-rudderstack-mcp.md (~4,750 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/pendo-vs-rudderstack-mcp.json · canonical https://www.anchorterminal.com/compare/pendo-vs-rudderstack-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

RudderStack MCP scores 54.7 (C) on agent readiness against Pendo's 44 (E), and leads in 5 of 7 scored categories. Pendo leads on reliability and transparency & trust. Both do analytics queries.

- Pendo: E 44, rank #1237 of 1510 · https://www.anchorterminal.com/tools/pendo.min.md
- RudderStack MCP: C 54.7, rank #901 of 1510 · https://www.anchorterminal.com/tools/rudderstack-mcp.min.md
- Pendo, good for Teams already paying for Pendo who want an agent to answer questions on usage, funnels, retention, guides and feedback, or to draft segments and journeys. Ahead on Reliability, 50 against 45; Transparency & trust, 77 against 51.
- RudderStack MCP, good for Data teams on RudderStack who want an agent to find why events, syncs or transformations failed and fix the configuration. Ahead on Schema & documentation, 66 against 28; Agent ergonomics, 52 against 41; Payments & pricing, 30 against 5; Maintenance & community, 85 against 60.

| Category | Pendo | RudderStack MCP |
| --- | --- | --- |
| Reliability (16%) | 50 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 28 | 66 |
| Agent ergonomics (13%) | 41 | 52 |
| Security & auth (14%) | 58 | 62 |
| Payments & pricing (10%) | 5 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 60 | 85 |
| Transparency & trust (7%) | 77 | 51 |

| Fact (where they differ) | Pendo | RudderStack MCP |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | Pendo.io, Inc. | RudderStack, Inc. |
| Hosted endpoint | `https://app.pendo.io/mcp/v0/shttp` | `https://mcp.rudderstack.com/mcp` |
| Transports | HTTP, Streamable HTTP, SSE (legacy) | Streamable HTTP |
| Auth | OAuth or key | OAuth |
| Pricing | Paid | Freemium |
| Licence | Proprietary service under the Pendo Software Services Agreement. The Claude Code plugin repository on GitHub is MIT | Proprietary service. The repository's MIT licence covers docs and metadata only |
| Tools exposed | 96 | 62 |
| MCP registry | not listed | `io.github.rudderlabs/rudderstack-mcp` |
| Last release | 2026-09-30 | none |
| Terms last updated | 2022-08-01 | not read yet |
| Privacy policy last updated | 2024-11-04 | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 1 stars | none |

Why the edge:
- Schema & documentation, RudderStack MCP +38: Pendo 28 (No machine-readable contract can be read. The Engage API's Postman collection is fetched by the documentation page's script with only a Run in Postman button, so it isn't a published contract under this run's reading, and the MCP input schemas need a paid subscription (0 of 25). www.pendo.io/llms.txt exists but is marketing copy with a section telling AI assistants when to recommend Pendo, and no Markdown docs were found (3 of 10). The MCP tools reference (updated 3 November 2026) gives each of 96 tools a purpose, example prompts and limits, and some entries say when to use another tool. Per-request API descriptions are no longer counted (12 of 20). No typed input schema or attribute table can be read. The tools reference states required IDs and some valid values in prose only (0 of 15). Example prompts for every tool and help articles for the 400 and timeout errors, with the collection's saved responses and status table no longer counted (5 of 15). The API path is v1 and the MCP path v0, with monthly release notes but no API changelog (8 of 15). 0+3+12+0+5+8 = 28.); RudderStack MCP 66 (The public repository's docs/tools.md lists 62 tools with an access class for each; JSON Schemas not read without a session (15 of 25). llms.txt (10). Every tool has a one-line purpose and a Read, Sensitive execution or Write class (15 of 20). Inputs not verifiable (5 of 15). Example prompts and a documented 'workspace_id is required' error (6 of 15). Versioned in the registry (0.43.1, 6 November) and dated release notes (15). 15 + 10 + 15 + 5 + 6 + 15 = 66.)
- Transparency & trust, Pendo +26: Pendo 77 (Closed service with a published Software Services Agreement, dated August 2022 on the page, which points to the contract centre for current terms (15 of 30). Privacy policy effective 4 November 2024, a DPA updated 24 February 2025, raw event retention of 7 years adjustable from 1 to 84 months, and an AI article stating that providers keep data for essentially zero days. These agree with each other, per the 7 October check (22 of 30). The October 2026 release notes announce `listCountables` renamed to `listPagesFeaturesAndEvents`, with the old name kept as a deprecated alias. A dated notice with no stated period takes 15, as settled in this run (15 of 20). Five data regions and the AI providers are named (Azure OpenAI, OpenAI, Amazon Bedrock, Google Gemini), but the sub-processor list sits on a Trust Centre page that we couldn't read (12 of 20). 15+22+15+12 = 64.); RudderStack MCP 51 (The server's source is closed; the repository's MIT licence covers only its docs and metadata. Terms in a master service agreement naming RudderStack, Inc. (15). Privacy policy read, retention given by purpose, not as periods (12 of 30). No deprecation policy for the MCP server (5 of 20). Subprocessors not found in the pages read (5 of 20). The MCP docs say live events, schemas, profile artifacts, transformation code and audit data stay within the workspace view. 15 + 12 + 5 + 5 = 37.)
- Payments & pricing, RudderStack MCP +25: Pendo 5 (No x402, MPP or L402 (0). Paid plans are priced on request, and the only published plan is Free (0). Pendo Free needs no card but excludes the API and integrations, and the MCP server is for paid customers, so the free plan doesn't reach the graded surface. The 30-day trial goes through sales (5 of 20). An admin must sign in and enable access in a browser (0). Total 5.); RudderStack MCP 30 (No machine payment protocol (0). Public plan prices with event allowances, nothing per call (10). Free plan with 250,000 events a month (20). A person signs up in a browser and approves OAuth (0). 0 + 10 + 20 + 0 = 30.)
- Maintenance & community, RudderStack MCP +25: Pendo 60 (The AI release notes (updated 3 November 2026) carry October 2026 entries for the MCP server, among them `promoteDiscoveryApp`, labels and assignees on Listen tools, `resolveObjectInstance`, and the rename of `listCountables` to `listPagesFeaturesAndEvents`. Entries are dated by month, counted from their month as settled in this run (30). Several MCP entries in September and October 2026 (20). Dated release notes, a community site and technical support, with no public issue tracker (10 of 25). Not checked in the official MCP registry, and no API client libraries, though the Claude Code plugin repository had its last commit on 30 October 2026 (6 of 15). The plugin repository is active, with 28 commits since 6 August, no tags and no CI workflow (4 of 10). 20+20+10+6+4 = 60.); RudderStack MCP 85 (Release notes dated 4 November 2026 and a registry version on 6 November (30). Many dated releases in 90 days (20). Public issue templates on the MCP repository, issues not read, plus release notes (10 of 25). Official registry entry io.github.rudderlabs/rudderstack-mcp and current official SDKs (15). A repository workflow publishes to the registry (10). 30 + 20 + 10 + 15 + 10 = 85. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.)
- Agent ergonomics, RudderStack MCP +11: Pendo 41 (96 tools named in the reference earns 5, plus 5 back for the separate read-only and write switches and Command Centre tools being off by default (10 of 25). Documented date range and row limits, saved segments as filters, and offset paging with a `hasMore` flag on usage tools (10 rows by default, up to 200, offset up to 10,000) (14 of 20). Help articles explain the 400 "missing jzb" and timeout errors. The collection's status table is no longer counted (8 of 20). No idempotency keys, and tool annotations couldn't be read without a subscription. Orchestrate journeys are created as drafts (3 of 20). No official API client libraries found. The SDKs Pendo publishes are for data capture (6 of 15). 10+14+8+3+6 = 41.); RudderStack MCP 52 (62 tools (5), plus a separately controlled read-only web surface (5). Filters on some list tools, not documented generally (8 of 20). One documented error (5 of 20). Read, Sensitive execution and Write classes, with Write tools to be confirmed by the client; annotations not read (14 of 20). One URL with OAuth and RudderStack SDKs in many languages (15). 10 + 8 + 5 + 14 + 15 = 52.)
- Reliability, Pendo +5: Pendo 50 (Graded as a hosted service on the MCP server and the Engage API. Statuspage site with API and MCP components in each of five regional environments, read from the page on 4 November (20). The incident feed lists six incidents from 6 August to 4 November 2026, each scoped to a subset of users, one region or one function. They are intermittent sign-outs for some US users (2 September), latency in the US region affecting login, guide delivery and event processing (14 September), guide targeting for a subset of US visitors (21 September), mobile pairing (1 October), authentication errors on new MCP connections for some customers from 16:49 on 1 October to 05:19 on 2 October, with existing connections unaffected, and Account and Visitor reports failing to load (4 November). All partial, so minor only (20). No request rate limits found for the API or the MCP server (0). The earlier 429 reading came from the Engage API's Postman collection, which the documentation page loads by script and this run doesn't read, and no 429 or retry guidance was found on the readable pages (0). No SLA found on the public legal pages, and the contract centre wasn't read (0). The MCP server has been generally available since April 2026 (10). 20+20+0+0+0+10 = 50.); RudderStack MCP 45 (Statuspage at status.rudderstack.com with regional components and none for MCP (15). Since August the history shows an EU ingestion issue, increased US latency, a Python transformations issue, free-tier processing delays and scheduled maintenance (20, minor incidents). No MCP rate limits found (0). No retry guidance for the MCP server found (0). No SLA found in the pages read (0). Not labelled beta (10). 15 + 20 + 0 + 0 + 0 + 10 = 45.)