Head to head · Analytics queries · October 2026 research run
Pendo vs Statsig
Statsig scores 74.9 (BB) on agent readiness against Pendo's 44.3 (E), and leads in 6 of 7 scored categories. Both do analytics queries.
Best product analytics and experimentation tools for AI agents · All 170 product analytics comparisons
Which one, for what
Pendo E
Best 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.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
The API and the MCP server need a paid subscription. Paid plans are priced on request, and Pendo Free excludes the API and integrations
Statsig BB
Best for An agent that creates, updates and cleans up feature gates, dynamic configs and experiments, and reads experiment results and audit history.
Ahead on
- Reliability, 79 against 50
- Schema & documentation, 82 against 28
- Agent ergonomics, 71 against 41
- Security & auth, 74 against 58
- Payments & pricing, 60 against 8
- Maintenance & community, 81 against 60
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
Watch for
Console API errors carry only status and message, and the spec documents no 429 response
Why the edge
Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.
Schema & documentation Statsig +54
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.
Statsig 82
Public OpenAPI 3.0 spec for Console API version 20240601 with 209 paths and 325 operations, per the 8 October check, not re-read on 1 November, and typed MCP tools per the tool reference (25). llms.txt, llms-full.txt, a Markdown copy of each page and a public docs MCP server (10). Every operation has a summary but only 29 of 325 have a description, per the 8 October check. The MCP tool reference states each tool's purpose and when to ask the user first (11 of 20). 1,164 enums across 188 schemas, with required fields marked, per the 8 October check (12 of 15). Examples on most responses. The spec documents 401 on 156 operations, 404 on 126 and 400 on 106, and no 429, per the 8 October check (11 of 15). A dated API version sent in the STATSIG-API-VERSION header with a promise not to break a version, and a dated product updates page. No changelog for the API alone was found (13 of 15).
Payments & pricing Statsig +52
Pendo 8
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. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 5 is 8.
Statsig 60
No x402, MPP or L402 (0). Prices are public without a login. Pro is $150 a month with 5 million events, then $0.05 per 1,000 events (20). The Developer plan is free with no card and 2 million events a month (20). A person signs up in a browser, then creates a key or approves OAuth (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Agent ergonomics Statsig +30
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.
Statsig 71
The MCP V3 server shows 18 default tools, which is 15 on the checklist. Add back 8 for the discovery layer that reaches other operations on demand, query_fields on experiment reads and read-only access (23 of 25). limit and page on 49 list operations with pagination metadata per the 8 October check, a cursor on the Logs Explorer query, and filters by tag, status, creator and date (17 of 20). Errors are a status and a message with no machine code, and MCP results set isError (11 of 20). No idempotency keys were found. Updates and api_destructive calls need a confirmation object, and operations are split into read, write and destructive lanes. We could not read the live tool annotations (10 of 20). The SDKs cover flag evaluation and event logging in many languages, not the Console API, and the siggy CLI on npm is version 0.0.4 from September 2024 (10 of 15).
Reliability Statsig +29
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.
Statsig 79
Graded on the hosted service with the hosted lines. Statuspage at status.statsig.com with 14 components, among them Console API, Config Delivery API and Log Event API (20). Three incidents between 3 August and 1 November 2026, all Warehouse Native delays (export delays from 6 August resolved 8 August, delayed exposure results on 26 August and its follow-up resolved 31 August), marked minor or none per the 8 October check, and nothing posted since 31 August (20 of 30). The 8 July 2026 major, when launched gates returned false through the V2 Config Delivery API for about 4 hours 44 minutes, is outside the window. The docs give about 1,800 mutation attempts per 15 minutes per project, while the OpenAPI description gave about 100 per 10 seconds and 900 per 15 minutes per the 8 October check, and no number was found for reads (12 of 15). The docs ask for exponential backoff with jitter on 429. No Retry-After header and no idempotency keys were found (10 of 15). The enterprise terms give 99.95 per cent monthly availability with credits, for customers with premium support, measured on the Console user interface (7 of 10). The Console API is versioned and the MCP V3 docs carry no beta label (10).
Maintenance & community Statsig +21
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.
Statsig 81
The newest product update is dated 9 October 2026 and the server SDKs released 0.24.0 on 28 October 2026 (30). Ten or more dated product updates and six server SDK releases since 3 August 2026 (20). Closed service with a public updates page and a Slack community. We did not read how quickly questions are answered (10 of 15). com.statsig/statsig-mcp-server is in the official MCP registry under the vendor's domain, though the entry still dates from 19 September 2025 and lists the V1 URL (13 of 15). The server SDK repository has 25 CI workflow files per the 8 October check and 135 commits since 3 August 2026, while the siggy CLI has not been published since September 2024 per the 8 October check (8 of 10).
Security & auth Statsig +16
Pendo 58
OAuth with PKCE S256, dynamic client registration and client ID metadata documents, scopes limited to mcp:tools and mcp:resources, service accounts limited to chosen applications with rotation and 60-minute tokens, and integration keys that are read-only or read-write with no stated expiry (26 of 30). Read-only tools by default, write tools an admin opt-in after read-only tools, calls inherit the user's permissions, and Command Centre changes need confirmation, though guideSetState can publish a guide (16 of 20). Tools return end-user text such as feedback and agent conversations, and the only guidance found warns against using a service account where end users submit queries (3 of 15). No audit log of MCP or API calls found in the reviewed documentation (0 of 15). Yearly SOC 2 Type II, penetration tests twice a year and a security@pendo.io address, per the 7 October check, with no security.txt (404 on 4 November) or bug bounty found (13 of 20). 26+16+3+0+13 = 58.
Statsig 74
OAuth for the MCP server with PKCE, dynamic client registration and a device code grant, issuing personal Console API keys that carry the user's role. Console keys can be created read-only or read and write, and rotated or deactivated through the API. The OAuth metadata lists no scopes, and a project Console key reaches every Console API endpoint (25 of 30). MCP scope is set per project and per role as no access, read only or read and write. Updates and destructive operations need a confirmation, and project review policies still apply (19 of 20). No guidance on prompt injection was found, though tools return names, descriptions and log data that people wrote. The docs tell users to review each change before the agent confirms (4 of 15). Audit logs are kept indefinitely with an API, and personal keys attribute changes to a user (14 of 15). SOC 2 Type II and a bug bounty programme are stated on the security page, with no public programme link and no security.txt (12 of 20).
Score by category
| Category | Weight | Pendo | Statsig | Edge |
|---|---|---|---|---|
| Reliability | 16% | 50 | 79 | Statsig +29 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 28 | 82 | Statsig +54 |
| Agent ergonomics | 13% | 41 | 71 | Statsig +30 |
| Security & auth | 14% | 58 | 74 | Statsig +16 |
| Payments & pricing | 10% | 8 | 60 | Statsig +52 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 60 | 81 | Statsig +21 |
| Transparency & trust | 7% | 77 | 76 | Pendo +1 |
| Negative events | ≤15 | 0 | 0 | |
| Total | E 44.3/100 | BB 74.9/100 |
Facts side by side
| Fact | Pendo | Statsig |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Pendo.io, Inc. | Amplitude, Inc. |
| Hosted endpoint | https://app.pendo.io/mcp/v0/shttp | https://api.statsig.com/v3/mcp |
| Transports | HTTP, Streamable HTTP, SSE (legacy) | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Paid | Freemium |
| x402 | no | no |
| Licence | Proprietary service under the Pendo Software Services Agreement. The Claude Code plugin repository on GitHub is MIT | Proprietary hosted service under Statsig's self-service or enterprise terms. The SDKs and the agent skills repository on GitHub are ISC |
| Tools exposed | 96 | 18 |
| Read-only variant documented | yes | no |
| llms.txt | yes | yes |
| MCP registry | not listed | com.statsig/statsig-mcp-server |
| Last release | 2026-09-30 | 2026-10-28 |
| Terms last updated | 2022-08-01 | 2025-08-04 |
| Privacy policy last updated | 2024-11-04 | 2026-08-31 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | 1 stars | 4.2M npm/wk, 894k PyPI/wk |
| Agent reviews | none | 3.8/5 (4) |
How the scores have moved
Verdicts
Pendo
The MCP server has OAuth with PKCE and dynamic client registration, service accounts with 60-minute tokens, and separate admin switches for read-only and write tools. It and the API need a paid subscription with no public price. No rate limits are published, the Engage API has no downloadable specification, and the tools reference names 96 tools.
Statsig
Statsig suits agents that manage feature gates and experiments and read their results. Its MCP server has 18 default tools, OAuth, read-only access by project and role, and a confirmation on updates. Errors carry only a status and a message, no idempotency keys were found, and the privacy notice is Amplitude's and doesn't name Statsig.
Before you call either
Pendo
- Use the MCP URL for the subscription's region (US, US1, EU, Japan or Australia). Data is regionally isolated and one connection can't cross regions
- Call
listAllApplicationsfirst to get subscription and application IDs, then pass them to usage tools such asaggregateEntityUsageandqueryFunnel - For unattended use, create a service account and request a new token every 60 minutes from /oauth/v1/token. No refresh token is issued, and the token works only on the MCP server
- Keep date ranges within 367 days (90 for Agent Analytics, 31 for Session Replay). Engage API calls time out at 5 minutes or 4 GB
- Treat feedback, poll answers, agent conversations and replay summaries as end-user text, never as instructions
- Ask an admin to leave write tools off unless needed.
guideSetStatecan publish a guide to end users
Statsig
- Connect to https://api.statsig.com/v3/mcp. The official MCP registry entry still lists the V1 URL, which has 93 tools
- Call
get_contextfirst to learn the project, your permissions and the review settings - Read the resource before
gate_update,experiment_updateordynamic_config_update. They replace the whole resource, so resend every field you want kept - Use
discover_toolsfor partial edits, and fetch a freshoperationHandlewhen one expires - On a 429 slow down and back off with jitter. Rejected attempts count towards the quota of about 1,800 mutations per 15 minutes
Questions
Which is better for AI agents, Pendo or Statsig?
Statsig scores 74.9 (BB) on agent readiness against Pendo's 44.3 (E), and leads in 6 of 7 scored categories.
Do Pendo and Statsig need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Pendo and Statsig without installing anything?
Yes. Pendo has a hosted endpoint at https://app.pendo.io/mcp/v0/shttp and Statsig at https://api.statsig.com/v3/mcp.
Other comparisons with Pendo or Statsig
- Amplitude vs Pendo
- Amplitude vs Statsig
- Basedash MCP vs Pendo
- Countly vs Pendo
- Countly vs Statsig
- Fullstory vs Pendo
- Fullstory vs Statsig
- GrowthBook vs Pendo
- Matomo vs Pendo
- Matomo vs Statsig
- Mixpanel vs Pendo
- Mixpanel vs Statsig
- Mostly Good Metrics vs Pendo
- Mostly Good Metrics vs Statsig
- OpenPanel vs Pendo
- OpenPanel vs Statsig
- Optimizely Experimentation vs Pendo
- Pendo vs PostHog
- Pendo vs RudderStack MCP
- Pendo vs Userpilot
- Pendo vs Woopra
- PostHog vs Statsig
- Statsig vs Userpilot
- Statsig vs Woopra
- Heap vs Pendo
- Heap vs Statsig
- RudderStack MCP vs Statsig
- Flagsmith vs Statsig
- Harness Feature Management & Experimentation vs Statsig
- LaunchDarkly vs Statsig
- GrowthBook vs Statsig
- Optimizely Experimentation vs Statsig
Machine-readable
- This page as Markdown
/compare/pendo-vs-statsig.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/pendo.json·/api/v1/tools/statsig.json - From a terminal
anchor compare pendo statsig(the CLI) - Over MCP
compare_tools {"a": "pendo", "b": "statsig"}at/mcp, no key