# Basedash MCP vs PostHog (slim)

> PostHog scores 67.4 (B) to Basedash MCP's 61.1 (C) for analytics queries. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/basedash-mcp-vs-posthog.md (~5,750 tokens) · this version ~3,780 tokens · JSON https://www.anchorterminal.com/compare/basedash-mcp-vs-posthog.json · canonical https://www.anchorterminal.com/compare/basedash-mcp-vs-posthog
- 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-02
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

PostHog scores 67.4 (B) on agent readiness against Basedash MCP's 61.1 (C), and leads in every scored category. Both do analytics queries.

- Basedash MCP: C 61.1, rank #501 of 1266 · https://www.anchorterminal.com/tools/basedash-mcp.min.md
- PostHog: B 67.4, rank #283 of 1266 · https://www.anchorterminal.com/tools/posthog.min.md
- Basedash MCP, good for Teams already on Basedash, or choosing a BI tool, that want an agent to answer questions from governed metrics and build dashboards under each person's access. Also No incidents deducted, where PostHog loses 10 points for them.
- PostHog, good for An agent that answers product questions in SQL or with funnel, retention and trends queries, and that manages feature flags, experiments and error tracking in the same project. Ahead on Reliability, 84 against 70; Schema & documentation, 81 against 57; Agent ergonomics, 78 against 55; Security & auth, 84 against 68; Payments & pricing, 40 against 32; Maintenance & community, 89 against 75; Transparency & trust, 83 against 74. Also Open source.

| Category | Basedash MCP | PostHog |
| --- | --- | --- |
| Reliability (16%) | 70 | 84 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 57 | 81 |
| Agent ergonomics (13%) | 55 | 78 |
| Security & auth (14%) | 68 | 84 |
| Payments & pricing (10%) | 32 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 89 |
| Transparency & trust (7%) | 74 | 83 |

| Fact (where they differ) | Basedash MCP | PostHog |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | BaseDash Inc. | PostHog Inc. |
| Hosted endpoint | `https://charts.basedash.com/api/public/mcp` | `https://us.posthog.com` |
| Transports | Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth | OAuth or key |
| Pricing | Paid | Freemium |
| Licence | Proprietary hosted service under Basedash's Terms of Service (updated 14 October 2026), governed by Delaware law. The Basedash/mcp repository holds only a README and server.json, with no licence file and no server code | MIT for the repository outside the `ee` directory, which has its own licence. PostHog Cloud is a hosted service under PostHog's terms |
| Tools exposed | 10 | 1183 |
| Read-only variant documented | no | yes |
| MCP registry | `com.basedash/mcp` | `io.github.PostHog/mcp` |
| Terms last updated | 2026-10-14 | 2026-06-29 |
| Privacy policy last updated | 2026-06-01 | 2026-06-29 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict benchmarking | not found in the text | yes |
| Popularity | none | 40k stars, 15.2M npm/wk |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Schema & documentation, PostHog +24: Basedash MCP 57 (The served tool definitions can be read only in a signed-in MCP session, which this run doesn't open. The docs and feature page list all ten tools with their inputs, which are required or optional, their scopes, what each returns and which one is annotated destructive, and the REST API counterpart has a public OpenAPI 3.1.0 file (50 paths, 91 operations). Judgement call, 10 of 25 for documented inputs without published JSON Schemas. llms.txt and Markdown copies of every docs page are served (10). Each tool's purpose is stated, with when to use MCP over the REST API and `get_data_sources` described as the call to make before asking; when not to call a build tool isn't stated (12 of 20). Inputs are a free-text `question` or `instructions` plus ids, with no enums or constraints documented (5 of 15). Example questions on the feature page and the launch posts, and troubleshooting for Forbidden or not-a-member, usage blocked and not-found errors, but no error payload shapes (10 of 15). A public dated changelog with MCP entries on 5 June, 14 August, 4 and 25 September and 7 and 9 October 2026, and a server.json version (1.1.0), but the registry entry is still 1.0.0 and the llms.txt of 7 October 2026 still describes two tools (10 of 15). Total 57.); PostHog 81 (OpenAPI 3.1 served without a login, 1,742 paths and 2,347 operations, and typed JSON Schema inputs on the MCP tools (25). llms.txt, and every docs page has a Markdown copy at the same address with .md (10). 1,487 of 2,347 operations (63 per cent) have a description. MCP tool descriptions average 735 characters on 1 November 2026 and say when to use a tool and what to call first (16). 1,243 enums across 4,792 schemas and a required scope on most operations (13). 706 examples in the spec. It documents 400 on 224 operations and 429 on 55, and the docs show the error shape with examples (9). Dated public changelog with RSS, but the spec version is fixed at 1.0.0 and the API has no versions (8).)
- Agent ergonomics, PostHog +23: Basedash MCP 55 (Ten tools, grouped by the vendor into ask, build and look up. Their definitions' size couldn't be measured without a session, so 20 of 25 rather than 25. No paging, filters or size controls are documented for `list_dashboards` or `list_charts`; `ask_question` returns tables as CSV files rather than inline rows, and the client can page through the tool list, per the changelog of 14 August 2026 (5 of 20). The troubleshooting section names Forbidden or not-a-member, usage blocked and not-found or archived artifacts with what to do, and `ask_question` and `get_data_sources` return typed structured payloads since 5 June 2026 (10 of 20). `edit_dashboard` is annotated destructive and a failed dashboard or chart build is cleaned up, but no readOnlyHint on the look-up tools or idempotency on the create tools is documented (10 of 20). One or two required inputs per tool and nothing to install; the only official SDK is the React embedding SDK, which isn't for MCP (10 of 15). Total 55.); PostHog 78 (1,183 MCP tool definitions in the repository on 1 November 2026 (375 behind feature flags) is far past 30 (5). Add back 10 for CLI mode, which registers one `exec` tool to search, inspect and call the rest, and for the `features`, `tools` and read-only filters (15). Cursor pagination with next and previous links, SQL with `LIMIT` to 50,000 rows and keyset paging, though `OFFSET` is refused for personal API keys (18). Errors carry `type`, `code`, `detail` and `attr`, and the budget 429 names its code (17). Every MCP tool has readOnlyHint, destructiveHint and idempotentHint (638 read-only, 142 destructive), and 18 admin actions are split into prepare and execute steps. No idempotency keys on REST writes (15). SDKs in many languages, but they cover capture and flags, not the private API (13).)
- Security & auth, PostHog +16: Basedash MCP 68 (OAuth on Basedash's own authorisation server, with the authorisation code grant and PKCE S256 only, refresh tokens, public clients, dynamic client registration, client ID metadata documents and a revocation endpoint. Three scopes separate asking, reading dashboards and writing them, and the token goes in the header only (30). Building needs `mcp:dashboards:write` on top of `mcp:chat:ask`, `edit_dashboard` is annotated destructive, no tool deletes, and Basedash's AI can change database rows only from the web app with an approval card, per the accuracy page. No server-side confirmation is documented for dashboard edits, and the consent screen on the feature page shows all three scopes together (15 of 20). Answers are drawn from connected company data, which can include text written by outsiders (tickets, CRM records synced by Fivetran), and no prompt-injection guidance was found. Hidden columns and row-level security narrow what reaches the model (5 of 15). The MCP server is a named audit log source, but AI tool calls and queries are recorded on Enterprise only; AI usage per person and feature is shown on every plan (10 of 15). No security.txt on www or charts, and no bug bounty or disclosure policy found. Basedash says it holds SOC 2 Type II, with the report under NDA, and runs third-party penetration tests (8 of 20). Total 68.); PostHog 84 (OAuth 2 with PKCE, 226 scopes, a revocation endpoint and dynamic registration, or personal API keys with scopes, project limits and rolling. A key can still be created with full access, and keys found in public GitHub repositories are rolled automatically (28). Read-only mode, filters by product area or tool, project pinning, and a typed confirmation for 18 admin actions (18). The MCP docs warn about prompt injection and tell users to review tool calls, and the CLI escapes informational responses. No further mitigation is documented for event and replay data that end users wrote (9). Activity logs with an API, MCP calls recorded with the caller's IP, and an admin view of every key with last use. Longer retention needs a platform package (12). security.txt valid to 30 August 2027, Bugcrowd disclosure programme paid in merchandise, public SOC 2 Type 2 report, annual penetration test and a public advisories page (17).)
- Reliability, PostHog +14: Basedash MCP 70 (Graded with the hosted lines, on the remote server at charts.basedash.com. Instatus status page at status.basedash.com with one component, App, and notices back to April 2021; the MCP server isn't a separate component (20). No notices since 14 March 2026 and 100.0 per cent shown for September, October and November 2026, so the last 90 days are clean (30). No rate limit is published for the MCP server. The public API allows 60 requests a minute by default, per the changelog of 7 August 2026, which we count in part since the MCP surface may differ (5 of 15). The OpenAPI file documents a 429 with `RateLimitExceeded` and `retryAfterMs` on all 91 operations and an `Idempotency-Key` on starting a chat, but nothing is documented for 429s or retries over MCP (5 of 15). No uptime SLA; the about page names priority support SLAs on Enterprise only (0). The server isn't labelled beta or preview and is on both paid plans (10). Total 70.); PostHog 84 (Graded on PostHog Cloud with the hosted lines. Status page on incident.io at posthogstatus.com with per-region components, among them MCP Server and REST API Query endpoints (20). Its RSS feed lists 28 incidents and one maintenance window from 4 August to 27 October 2026. Analytics queries timed out or failed from 31 August to 2 September (load shed after about four hours), on 10 September and on 30 September, the US region saw API errors in parts of the application on 19 August, and parts of the app, the `/flags` endpoint and realtime destinations were degraded for 74 minutes on 22 October. Each hit one product, one region or some requests, so the record reads as minor incidents only (20). Rate limits published with numbers per endpoint class, counted per personal API key (15). The query read budget answers 429 with `Retry-After` and budget headers, but there is no backoff guidance for the general limits and no idempotency keys for writes were found (9). 99.95 per cent uptime SLA in the terms for the Enterprise package (10). The REST API is generally available and the MCP docs carry no beta label (10).)
- Maintenance & community, PostHog +14: Basedash MCP 75 (Read as a closed hosted service. The changelog's latest entry is 30 October 2026, and the latest MCP-specific entries are 7 and 9 October 2026 (chart placement on a dashboard tab, restyled MCP sign-in pages), all within 30 days (30). Weekly dated changelog entries, with MCP changes on 14 August, 4 and 25 September and 7 and 9 October 2026 (20). Support by email and by Slack on paid plans, with response times not tested (10 of 15). Active in the official MCP registry as com.basedash/mcp under the reverse-DNS namespace for basedash.com, though its description still names two tools (15). No package to judge; the registry entry lags the repository's server.json (0 of 10). Total 75.); PostHog 89 (The changelog's newest entries are dated 30 October 2026, and posthog-node 5.61.1 and the Python SDK's posthog-v7.81.1 came out the same day (30). 204 dated changelog entries since 3 August 2026 (20). Public changelog, community questions and in-app support. Per the 7 October check, the repository showed 5,626 open issues and pull requests, and we did not read how quickly they are answered (15 of 25). `io.github.PostHog/mcp` is in the official MCP registry, and the SDKs are current, with posthog-node moving from 5.55.0 to 5.61.1 between 7 and 30 October 2026 (15). 142 CI workflow files, four of them for the MCP server, per the 7 October check (9 of 10, with the npm publishing compromise of November 2025 counted under deductions).)
- Transparency & trust, PostHog +9: Basedash MCP 74 (The editorial half. A closed service under dated terms (14 October 2026) naming Basedash Inc. and Delaware law, with 30 days' notice of material adverse changes to the agreement (15). The privacy policy (1 June 2026), the data processing addendum (6 October 2026) and the security docs agree that customer data isn't used for training by Basedash or its AI providers, and the security docs say table and column names and query results go to AI providers. Retention periods differ by document. The privacy policy says a reasonable period, the terms 60 days after a deletion request, the security docs complete removal on request, and audit events are kept 90 days. Locations differ in wording (San Francisco servers in the security docs, DigitalOcean in the United States in the privacy policy) (18 of 30). No deprecation policy for the MCP server; the REST API is unversioned and breaking changes are communicated in advance when possible, and the dashboard scopes were granted to existing connections without re-authorising (8 of 20). The DPA names ten subprocessors (OpenAI, Sentry, Stripe, DigitalOcean, Anthropic, Amazon Web Services, Microsoft Azure, Fivetran, MotherDuck, Betterstack) in the United States and the Czech Republic (16 of 20). Total 57.); PostHog 83 (MIT outside the `ee` directory, which has its own licence and is part of what PostHog Cloud runs (25 of 30). Privacy policy, a self-serve DPA and the terms agree. The terms let PostHog use de-identified customer content to train its own models unless the customer opts out, and bar third parties from training on it. The privacy policy gives no retention periods, while the pricing page gives 1 year on the free plan and 7 on paid (22). No deprecation policy was found, and the query docs reserve the right to restrict export-like queries without notice. 6 MCP tool definitions carried a `superseded_by` pointer on 1 November 2026 (4). Sub-processor list updated 12 June 2026 with locations, 14 days' notice of changes, and data in Virginia or Germany (20).)