# Basedash MCP vs Matomo (slim)

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

- Full: https://www.anchorterminal.com/compare/basedash-mcp-vs-matomo.md (~4,350 tokens) · this version ~2,280 tokens · JSON https://www.anchorterminal.com/compare/basedash-mcp-vs-matomo.json · canonical https://www.anchorterminal.com/compare/basedash-mcp-vs-matomo
- 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 Matomo's 59.7 (C), and leads in 2 of 7 scored categories. Matomo leads on schema & documentation and agent ergonomics. Both do analytics queries.

- Basedash MCP: C 61.1, rank #501 of 1266 · https://www.anchorterminal.com/tools/basedash-mcp.min.md
- Matomo: C 59.7, rank #582 of 1266 · https://www.anchorterminal.com/tools/matomo.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 38. Also A hosted endpoint, with nothing to install.
- Matomo, good for Teams that want web and product analytics with data kept in the EU or on their own servers, queried by report, segment, funnel or cohort. Ahead on Schema & documentation, 73 against 57; Agent ergonomics, 78 against 55. Also Open source.

| Category | Basedash MCP | Matomo |
| --- | --- | --- |
| Reliability (16%) | 70 | 38 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 57 | 73 |
| Agent ergonomics (13%) | 55 | 78 |
| Security & auth (14%) | 68 | 71 |
| Payments & pricing (10%) | 32 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 75 | 79 |
| Transparency & trust (7%) | 74 | 74 |

| Fact (where they differ) | Basedash MCP | Matomo |
| --- | --- | --- |
| Kind | MCP server | HTTP API |
| Vendor | BaseDash Inc. | InnoCraft Limited |
| Hosted endpoint | `https://charts.basedash.com/api/public/mcp` | no (local only) |
| Transports | Streamable HTTP | HTTP, Streamable 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 | Matomo core is GPL-3.0-or-later and the MCP server plugin is GPL v3 or later. Matomo Cloud is a hosted service under InnoCraft's terms. Paid On-Premise plugins fall under the InnoCraft EULA |
| Tools exposed | 10 | 19 |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| MCP registry | `com.basedash/mcp` | not listed |
| Last release | 2026-10-30 | 2026-10-04 |
| Terms last updated | 2026-10-14 | 2025-04-10 |
| Privacy policy last updated | 2026-06-01 | 2026-05-05 |
| Terms restrict automated access | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Reliability, Basedash MCP +32: 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.); Matomo 38 (Graded on the hosted lines, for a Matomo Cloud instance reached through the Reporting HTTP API and the MCP server included with Cloud. status.matomo.cloud is a public status page with six components (20). The page is drawn by script, its settings show two days of history, and its RSS feed lists only current component states, all Operational on 9 October 2026 with the last state change on 8 September 2026, so no 90-day incident record could be read (5). No API rate limit numbers were found. The terms reserve suspension for excessively frequent requests, and `API.getBulkRequest` is capped at 50 URLs for anonymous callers (3 of 15). No 429 or retry guidance and no idempotency keys were found (0). No SLA for Cloud was found, and the terms supply the service as is (0). The Reporting API and MCP plugin 5.1.1 are stable releases (10).)
- Agent ergonomics, Matomo +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.); Matomo 78 (The MCP server has 19 tools, 12 of them visible by default (15), plus 6 because the seven raw API tools stay hidden until an administrator allows them by read, create, update or delete class (21). `filter_limit`, `filter_offset`, sorting, pattern filters, `showColumns` and segments on the API, and cursors with a 250-row cap on the MCP report tool (20). Errors are HTTP codes with a message and an optional integer code, with no code catalogue. The MCP server separates schema failures (-32602) from tool result errors that name the arguments involved (14). Every MCP tool carries readOnlyHint, destructiveHint and idempotentHint. API writes have no idempotency keys and the OpenAPI descriptions declare delete methods as GET (13). Report calls need only `idSite`, `period` and `date`. The official clients for JavaScript, PHP and Java cover tracking, not the Reporting API (10).)
- Schema & documentation, Matomo +16: 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.); Matomo 73 (Each of the 72 module pages in the API reference embeds an OpenAPI 3.1 description, and every MCP tool has a typed JSON Schema input. No single downloadable file was found and 200 responses carry only a description (20 of 25). developer.matomo.org/llms.txt and matomo.org/llms.txt answer 404. The docs source is Markdown in a public repository (2). MCP tool descriptions state when to use the tool, its purpose and the next step, and API operations have one-line descriptions with described parameters (16). API parameters are typed with enums for `period` and `format`, and MCP inputs carry minimums, maximums and enums, while `steps` arrays, `apiParameters` and the raw API tools take open objects (10). Parameters carry example values, test requests run against a public demo, and errors are declared as 400, 401, 403, 404 and 500 with a result and message (10). Docs are versioned 4.x, 5.x and 6.x, with a developer changelog per release (15).)