Retrieve all user accounts from Matomo Analytics to manage access permissions and user administration.
ISC
305,717 tools. Last updated 2026-07-16 16:39
"Matomo" matching MCP tools:
- Retrieve all sites from Matomo Analytics to manage and monitor website tracking configurations through the Matomo MCP Server.ISC
- Connect to a Matomo Analytics instance using base URL and authentication token to access analytics data and manage sites, users, and reports through the MCP interface.ISC
- Add a new site to Matomo Analytics for tracking and monitoring website performance data through the Matomo MCP Server.ISC
- Add a new user to Matomo Analytics by providing login credentials and email, enabling user management through the Matomo MCP Server.ISC
- Retrieve Matomo Analytics system information including version, configuration, and server details to monitor platform status and verify API connectivity.ISC
Matching MCP Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server that provides tools to interact with Matomo Analytics API, enabling management of sites, users, goals, segments, and access to analytics reports through a MCP interface.Last updated112ISC
- -license-quality-maintenanceEnables AI models to interact with Matomo analytics through a complete MCP server implementation. Provides tools for retrieving analytics data, managing sites, and generating reports with zero configuration setup.Last updated
- Retrieve a 30/60/90-day performance snapshot for a post, aggregating GSC, Matomo, GA4, Clarity, and AI citation data from configured sources. Returns available metrics only.MIT
- Retrieve detailed information about a specific Matomo Analytics site using its site ID to access configuration, settings, and metadata.ISC
- Retrieve goals list for a Matomo site to track and analyze conversion metrics using site ID.ISC
- Add a new goal to a Matomo Analytics site by specifying tracking criteria like URL patterns or event attributes to measure conversions and user actions.ISC
- Retrieve total visits, actions, and engagement metrics for a specific Matomo site during a defined period to analyze traffic patterns and performance.ISC
- Retrieve the most visited pages from Matomo Analytics for a specific site and date range to identify popular content and user behavior patterns.ISC
- Deploys an app to a VM and exposes it at a public https://<name>-<id>.redu.cloud URL (a random 8-char suffix is appended to <name> for uniqueness — a BARE custom `dname` like `myapp.redu.cloud` ALSO gets a suffix, so to PIN a known URL pass a dname that already includes an 8-char suffix like `myapp-7k2m9x4p.redu.cloud` and wire the app's own URL env to it; single-surface apps can instead just read the injected PUBLIC_URL/APP_URL). The container is built ON the VM — no local Docker/podman needed. PREREQS — run check_deploy_prerequisites first: it auto-selects your network_id + keypair_name (and returns a recipe to mint a keypair if you have none). Pass those two ids here. PORT: pass the port the app actually listens on (plan_deploy detects it / Dockerfile EXPOSE) — redu health-probes that exact port, so a wrong/omitted port (defaults to 3000) fails a non-3000 app (e.g. a static nginx app listens on 80 → pass 80). TWO source modes: (1) GIT — pass `repo` (public; private repos also need git_token). (2) UPLOAD — call prepare_upload first to tar + POST your LOCAL working dir, then pass the returned `source_token` (no git, no PAT; use this for uncommitted code, a fixed clone of a repo you don't own, or private code). The source needs a Containerfile/Dockerfile; redu auto-finds one in common subfolders (Docker/, scripts/, packaging/…) and builds with the repo root as context — for a repo with MULTIPLE Dockerfiles pass `dockerfile`+`context` to pick the right one. If it has NONE, pass dockerfile_content (the one plan_deploy generated) or include a Dockerfile in the uploaded tarball. To wire a DB, pass `database` (auto-injects the connection env + DATABASE_URL — zero setup): `database:'single_vm'` puts Postgres ON the app VM (cheapest; data dies if the VM is replaced); `database:'managed'` provisions a SEPARATE managed-DB VM on the same private network and wires it automatically (data PERSISTS across redeploys; reused on a same-name redeploy) — you do NOT call create_database/create_relational_database for this. Choose the engine with `db_engine` ('postgres' default → PG* env; 'mysql'/'mariadb' → MYSQL_* env + mysql:// URL, for WordPress/Matomo/LAMP apps; mysql/mariadb require database:'managed'). redu also injects APP_URL/PUBLIC_URL (= the app's public URL) into its env, so apps that need their own URL get it (map an app-specific var like BASE_URL to PUBLIC_URL if needed). Build+provision takes ~3-6 min (a bit longer for managed, which also brings up the DB VM); poll list_deployments or get_deployment until status='ready'. On 'build_failed'/'error', call get_deployment(id) to read build_log. ALWAYS run plan_deploy first and confirm the plan + cost with the user before deploying.Connector
- Provisions a managed MySQL (or MariaDB) database on a dedicated VM on your private network — the relational-database resource (use this instead of create_database when the app needs MySQL/MariaDB, e.g. WordPress, NextCloud, Matomo, many PHP/LAMP apps). Requires a recent plan_managed_datastore. For app deployments, prefer deploy_app database:'managed' with db_engine mysql/mariadb so plan_deploy includes and wires the DB automatically. It is PRIVATE — reachable only from another instance on the same private network, via the DB's internal/private IP (port 3306), not a public address. Get the ids from plan_managed_datastore/list_flavors/list_private_networks/list_keypairs. Provisioning takes ~5 min; poll list_relational_databases until status='ready', then the connection details (private_ip, port 3306, db_name, db_user) are populated. MySQL is created with mysql_native_password auth so older clients/apps connect cleanly. (ClickHouse is a separate resource — use create_clickhouse / list_clickhouse_databases.)Connector