# Basedash MCP vs Mixpanel (slim)

> Mixpanel and Basedash MCP score within a point of each other for analytics queries, 62 and 61.1 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/basedash-mcp-vs-mixpanel.md (~5,600 tokens) · this version ~3,630 tokens · JSON https://www.anchorterminal.com/compare/basedash-mcp-vs-mixpanel.json · canonical https://www.anchorterminal.com/compare/basedash-mcp-vs-mixpanel
- 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)

Mixpanel and Basedash MCP score within a point of each other on agent readiness, 62 (B) and 61.1 (C). Basedash MCP leads on reliability. Both do analytics queries.

- Basedash MCP: C 61.1, rank #501 of 1266 · https://www.anchorterminal.com/tools/basedash-mcp.min.md
- Mixpanel: B 62, rank #466 of 1266 · https://www.anchorterminal.com/tools/mixpanel.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. Ahead on Reliability, 70 against 65. Also No incidents deducted, where Mixpanel loses 5 points for them.
- Mixpanel, good for Teams already tracking in Mixpanel who want an agent to answer funnel, retention and cohort questions or manage Lexicon, experiments and flags. Ahead on Schema & documentation, 79 against 57; Agent ergonomics, 61 against 55; Payments & pricing, 37 against 32; Maintenance & community, 80 against 75; Transparency & trust, 84 against 74.

| Category | Basedash MCP | Mixpanel |
| --- | --- | --- |
| Reliability (16%) | 70 | 65 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 57 | 79 |
| Agent ergonomics (13%) | 55 | 61 |
| Security & auth (14%) | 68 | 70 |
| Payments & pricing (10%) | 32 | 37 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 80 |
| Transparency & trust (7%) | 74 | 84 |

| Fact (where they differ) | Basedash MCP | Mixpanel |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | BaseDash Inc. | Mixpanel, Inc. |
| Hosted endpoint | `https://charts.basedash.com/api/public/mcp` | `https://mixpanel.com/api` |
| 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 | Proprietary service under Mixpanel's terms of use. The tracking SDKs and the Claude Code plugin on GitHub are Apache-2.0, and Mixpanel Headless is MIT |
| Tools exposed | 10 | 64 |
| MCP registry | `com.basedash/mcp` | not listed |
| Last release | 2026-10-30 | 2026-10-28 |
| Terms last updated | 2026-10-14 | no date given |
| Privacy policy last updated | 2026-06-01 | no date given |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | none | 3.2M npm/wk, 1.5M PyPI/wk |
| Agent reviews | none | 4/5 (4) |

Why the edge:
- Schema & documentation, Mixpanel +22: 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.); Mixpanel 79 (14 OpenAPI 3.0 and 3.1 specs are public at docs.mixpanel.com/openapi/ with 106 operations. The MCP tool schemas sit behind sign-in, so the API carries this line (25). llms.txt with about 530 links, llms-full.txt, a Markdown copy of every page and a docs MCP server (10). All 106 operations carry a summary or description, and the MCP page gives each tool one line with no guidance on when not to use it (15 of 20). The specs hold about 250 enums, but Query API calls pass JSON-encoded strings and `where` expressions in query parameters and JQL takes a script (10 of 15). Examples are present, the ingestion spec documents 400, 401, 413 and 429, and the Query spec documents only a 200 on all 19 operations (9 of 15). The changelog is public and dated with 183 entries. The APIs carry no dated versions, with paths such as /api/2.0 and /v1 (10 of 15).)
- Transparency & trust, Mixpanel +10: 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.); Mixpanel 84 (Closed service with public terms of use, last updated 2 June 2026. The SDKs are Apache-2.0 and Mixpanel Headless is MIT (16 of 30). The DPA of 2 June 2026 makes data available for 30 days after termination and then destroys it, and audit log retention is stated per plan. The privacy policy of 21 August 2026 covers only Mixpanel's own collection and names data centres in the US and EU, while the DPA adds India (24 of 30). Removals come with dated notices (Project Secret on 3 March 2027, TLS 1.0 and 1.1 in April 2026, US-to-EU forwarding in July 2026). No written policy with a minimum notice period was found (14 of 20). The sub-processor list, effective 21 October 2026, gives locations and names Anthropic, OpenAI and Google Vertex AI, with 30 days' notice of new sub-processors in the DPA (19 of 20).)
- Agent ergonomics, Mixpanel +6: 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.); Mixpanel 61 (The MCP page names 64 tools, which is over 30 (5), with OAuth scope subsets and a `Get-Query-Schema` tool that keeps the query schema out of the tool list (5 back, 10 of 25). Query endpoints take date ranges, `limit` and `where` filters, and profile queries page with `page` and `session_id`. No field selection was found (16 of 20). `/import` with `strict=1` returns the failing events with reasons, and the MCP server's 401 says how to recover. Query API errors aren't in the spec (12 of 20). `$insert_id` deduplicates imports. No idempotency key was found for management writes, and we couldn't read the MCP tools' readOnlyHint or destructiveHint (10 of 20). Tracking SDKs in 12 languages and a Python SDK and CLI for queries, which is pre-1.0. Every query needs a project ID and the right regional host (13 of 15).)
- Reliability, Basedash MCP +5: 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.); Mixpanel 65 (Read with the hosted lines, on the Query API and the hosted MCP server. www.mixpanelstatus.com is a Statuspage site with 11 components by region (20). Its history feed lists five incidents between 4 August and 2 November 2026. The Query API failed for US projects for about 77 minutes on 26 August, 2:02 to 3:19 PM PT per the post-mortem, when query servers "across the region failed their health checks nearly simultaneously" and reports were unavailable, with EU and India projects unaffected. US is the default data residency. A core API down across one region for an hour or more reads as a regional major, as vapi's US calls outage and google-drive-api's did. The others were confined to one host, tool or a subset and read as minor. Ingestion was delayed for US projects on 8 October, requests to decide.mixpanel.com failed on 21 October with the regional API hosts as a workaround, the MCP `Get-Report` tool failed with skip_results false on 6 August, and property menus misbehaved on 19 August. One major outage (10). Limits have numbers, 60 queries an hour and five concurrent on the Query API and 600 MCP requests an hour per user (15). The import docs give exponential backoff with jitter from 2 seconds to 60 for 429, 502 and 503, and `$insert_id` makes import retries safe. No Retry-After header was found in the reviewed documentation (12 of 15). No uptime SLA was found. Section 9.4 of the terms says the service isn't warranted to be always available (0). The APIs and the MCP server are generally available, with service account sign-in for MCP, the experiment and flag tools and `Get-Audit-Log` in beta (8 of 10). 20 + 10 + 15 + 12 + 0 + 8 = 65.)
- Payments & pricing, Mixpanel +5: Basedash MCP 32 (No x402, MPP or L402 (0). Plan prices are public, $1,000 a month for Startup with $1,000 of AI credits included, but the cost of an MCP question in AI usage isn't published (10). A 14-day trial needs no card, includes up to $250 of AI usage and has the MCP server, since it's on every plan and the trial has full feature access (20). A person signs up in a browser and approves the OAuth connection; clients can register themselves with the authorisation server, which earns 2 (2 of 20). Total 32.); Mixpanel 37 (Read with the hosted rubric. No x402, MPP or L402 (0). Prices are public without login. The docs give $0.00028 an event beyond the first 1M a month on the 1M Growth plan and the pricing page has a volume calculator. Enterprise is by quote, and the Query API limits on Free and Growth aren't given as figures (17 of 20). The Free plan covers 1M events a month with no card (20). A person signs up in a browser and approves OAuth or creates a service account. The MCP server supports dynamic client registration, but a user still signs in (0).)
- Maintenance & community, Mixpanel +5: 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.); Mixpanel 80 (The product changelog's newest entry is 28 October 2026 (a Custom Insights Query endpoint for the Query API, in beta), after mixpanel-browser 2.84.0 and Mixpanel Headless 0.4.0 on 5 October (30). The changelog has 23 dated entries from 7 August to 28 October 2026 (20). Public changelog, a Slack community and email support on every plan. We didn't measure reply times (11 of 15). No Mixpanel namespace was found in the official MCP registry per the 7 October check. Official SDKs are current in JavaScript and Python (mixpanel-browser 2.84.0, Python mixpanel 5.4.1 on 3 September, Node mixpanel 0.24.0 on 1 September) (12 of 15). The Headless repository has CI, conformance and release workflows and a lock file, and mixpanel-js tags carry an SBOM proof. We couldn't read whether CI passes (7 of 10).)