# Basedash MCP vs Woopra (slim)

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

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

Basedash MCP scores 61.1 (C) on agent readiness against Woopra's 44.4 (E), and leads in 6 of 7 scored categories. Woopra 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
- Woopra: E 44.4, rank #1085 of 1266 · https://www.anchorterminal.com/tools/woopra.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 Schema & documentation, 57 against 45; Agent ergonomics, 55 against 45; Security & auth, 68 against 22; Maintenance & community, 75 against 9; Transparency & trust, 74 against 62. Also Free to start without a card.
- Woopra, good for An agent that reads a company's existing Woopra reports, looks up or edits customer profiles, or exports raw sessions on a schedule. Ahead on Reliability, 80 against 70.

| Category | Basedash MCP | Woopra |
| --- | --- | --- |
| Reliability (16%) | 70 | 80 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 57 | 45 |
| Agent ergonomics (13%) | 55 | 45 |
| Security & auth (14%) | 68 | 22 |
| Payments & pricing (10%) | 32 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 9 |
| Transparency & trust (7%) | 74 | 62 |

| Fact (where they differ) | Basedash MCP | Woopra |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | BaseDash Inc. | Woopra, Inc. |
| Hosted endpoint | `https://charts.basedash.com/api/public/mcp` | `https://www.woopra.com/rest/3.10` |
| Transports | Streamable HTTP | HTTP |
| Auth | OAuth | OAuth or key |
| 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 Woopra's terms of service. The browser tracker and the SDKs on GitHub are MIT, and the Node package is ISC |
| Tools exposed | 10 | none |
| MCP registry | `com.basedash/mcp` | not listed |
| Last release | 2026-10-30 | 2026-03-16 |
| Terms last updated | 2026-10-14 | 2025-12-10 |
| Privacy policy last updated | 2026-06-01 | 2025-08-01 |
| Terms restrict automated access | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |
| Popularity | none | 415 npm/wk |
| Agent reviews | none | 2.3/5 (4) |

Why the edge:
- Maintenance & community, Basedash MCP +66: 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.); Woopra 9 (The newest dated change found is a commit to the browser tracker on 16 March 2026, and the REST intro page was last edited on 13 March 2026, both more than 180 days before the check (0). No releases or dated changelog entries in the last 90 days (0). No API changelog. Support is by email and in-app, and response times were not checked (3). The browser tracker's last tag is v5.3.0 from 2021, iOS and Android were last committed to in November 2024, and the Node, Python, Java and Rails SDKs in 2017 (4). The Node README carries a Travis CI badge and no current CI was found (2). Total 9.)
- Security & auth, Basedash MCP +46: 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.); Woopra 22 (REST calls use per-user access keys sent by HTTP Basic, with no scopes or rotation guidance found. Tracking calls need only the project name by default, with an optional Secure Tracking secret. Docs examples still show `http://` tracking URLs (15 of 30). The pricing page states group and individual permission controls, but no read-only key or confirmation on `/profile/delete` was found (5). The API returns event and profile text that any caller who knows the project name can write, and no guidance on untrusted content was found (0). No audit log found in the docs (0). No security page, bug bounty or certification was found on the pages read, and security.txt timed out. The privacy policy states Data Privacy Framework certification (2). Total 22.)
- Schema & documentation, Basedash MCP +12: 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.); Woopra 45 (Each REST reference page embeds an OpenAPI 3.1 fragment in its Markdown copy. No single spec file was found, most operations define no responses, and the tracking endpoints are documented as tables (12). llms.txt and a .md copy of each page, though llms.txt lists four of fourteen REST operations (10). Descriptions are one line. The `/profiles` page repeats the `/trends` text, three profile operations have none, and one page still holds template placeholder text (6). Query parameters carry types and required flags. There are no enums, and profile edits take a JSON string in `data` (6). One curl example for REST and several tracking examples. Tracking response codes are explained, while REST errors are a 400 with an empty object (6). The version sits in the path and 3.10 is the only one supported. No changelog found (5). Total 45.)
- Transparency & trust, Basedash MCP +12: 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.); Woopra 62 (Closed service with dated terms that cover the subscription, and MIT SDKs (15). The terms say the customer owns tracking data, and the pricing page states 24 months of retention. The privacy policy excludes end-user data, the DPA is sent only on request, and the GDPR page still cites Privacy Shield while the privacy policy cites the Data Privacy Framework (14). No deprecation policy or dated notices found (0). Nine sub-processors named in the terms with addresses and countries, eight in the USA and Hetzner in Germany. Where customer data is stored is not stated (16). Total 45.)
- Reliability, Woopra +10: 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.); Woopra 80 (Graded on the REST and HTTP tracking APIs with the hosted lines. Statuspage site at status.woopra.com with three components (20). Its history lists no incidents for August, September or October 2026, the three months shown (30). Limits published with numbers, 300 calls a minute, 600 an hour and 3,000 a day per project (15). A 429 status is documented and tracking calls answer 202 when queued, but no Retry-After, backoff guidance or idempotency key was found (5). No SLA found. The terms promise commercially reasonable efforts (0). The API is version 3.10 with no beta label (10). Total 80.)
- Agent ergonomics, Basedash MCP +10: 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.); Woopra 45 (Report responses can be capped with `limit`, but a report can only be run from a `report_id` saved in the web app, so an agent can't shape a query through the API (12). `limit`, `offset`, a `snapshot` ID for consistent paging and timeframe overrides on reports, and position headers on log export (14). Tracking codes 401, 402 and 403 each name a cause. REST error bodies are not documented (8). No idempotency key or dedupe field was found, and tracking is by GET. Imports return a batch ID to poll (3). Report calls need two parameters. Official SDKs exist in several languages, but the server ones date from 2017 (8). Total 45.)