"Matomo web analytics platform" matching MCP tools:

• list_subscribersA

  PushNotif Official MCP ServerA

  Retrieve active subscriber device records, assigned segment tags, platform breakdown counts (Web VAPID, Android FCM, iOS APNs), or full CSV/JSON backup export for zero-downtime migration. Use this tool to inspect audience size, platform distribution, export subscriber tokens (export_format="csv" or "json"), or obtain a subscriber_id before calling update_subscriber_tags; do not use it to view campaign click metrics (use get_campaign_analytics instead) or modify/import subscribers (use update_subscriber_tags instead). Read-only operation requiring PUSHNOTIF_API_KEY with 0 credit cost; filter by app_id and optional tag to narrow results. Returns JSON { total_active, platform_breakdown: { web, android_fcm, ios_apns }, subscribers: [{ id, app_id, platform, tags, created_at }], export_data }.

  ConnectorNo auth

• get_product_brainA

  AIOProductOS MCPA

  A grounded snapshot of the org's product so YOU can reason about it. Returns one JSON object with: revenue + top paying accounts (ranked by MRR), web + product analytics headline metrics, the feature list, recent verbatim customer signals (newest first), and open-work counts — each block empty when that source isn't flowing yet. The time-windowed sections (revenue, cost, web + product analytics, feature usage) honour `window` (7 | 30 | 90 days, default 30). Single call, no pagination. Start here to ground, then go deeper with the dedicated list_* reads and the analytics tools. Optional product_id (the org's primary product when omitted).

  ConnectorNo auth

• list_connectorsA

  AutarioA

  List the platform connectors set up on this Autario account: search, web and product analytics, ads, social, commerce, payments, AI usage and developer platforms. The answer names each connected platform, so call this instead of guessing which ones exist. Each entry carries its live dataset_id (queryable via query_dataset), datasets[] (ALL datasets the connector materialized | multi-report connectors produce one per report), refresh interval, last refresh time, and `health`: state (ok | stale | needs_sign_in | reports_missing | retrying | ours | never_ran | running), how old the data is per dataset, and next_step { who: assistant | user | nobody, action, url? }. CHECK health.state BEFORE answering from a connector table: ok = use it; stale = call refresh_connector once; needs_sign_in = give the user the one sign-in link in next_step.url, do not refresh; reports_missing = say which reports and why (get_connector_status has the per-report sentences); retrying or ours = answer from the data you have and say how old it is. Use this whenever a user asks about "my Search Console data", "my ad spend", "my store orders" or wants a cross-platform weekly report. Connectors are created and configured by the account owner in the Autario UI (autario.com/manage) | this tool only reads them, it never changes settings or handles credentials. Requires AUTARIO_API_KEY.

  ConnectorNo auth

• get_performanceA

  KreatorMeshA

  Metrics for this workspace's published posts. Returns a summary totalled across every published post (post count, overall totals, totals per platform), plus the newest posts in detail, each with one entry per platform it went to: impressions, reach, views, likes, comments, shares and saves. A metric is null when that platform does not report it; supported=false means nothing can be read for that target (no analytics for the platform, or no post id yet). Values are the last stored reading, not a live fetch, and fetchedAt says when it was taken. Use this to answer whether posts worked. It covers published posts only: use list_posts for drafts and scheduled posts, get_post for one post's details, and get_link_in_bio for visits to the link-in-bio page.

  ConnectorAPI key

• get_roadmapA

  AgentropolisA

  List Agentropolis platform features with status (live, partial, stub, planned), endpoint and guardrails: badges, the x402 relay, seller claims and analytics, sponsored placement, market data, billing. Use it to check whether a platform capability exists before relying on it; it describes Agentropolis itself, not listings. Read-only, no parameters. Stub endpoints answer HTTP 501; payments_enabled shows whether Agentropolis charges for anything (currently false).

  ConnectorNo auth

• delete_proposalA

  LivePage · 活页A

  Delete a page: its link stops working immediately and it disappears from the page list, analytics and folder pages — readers who open it get a 404. You can restore it within 30 days with restore_proposal; after that the platform erases it for good (content, versions, page images, reading records and viewer-appended rows all cease to exist; not reversible). To erase it immediately, use the web console, where the consequences are spelled out. Pages with unresolved reports cannot be deleted — resolve the report first. confirm must repeat the page's title exactly, to guard against deleting the wrong one: check with list_proposals first.

  Connector

  Destructive

  API key

• tech_fingerprintA

  ContrastAPIA

  Detect website technology stack: CMS, frameworks, CDN, analytics tools, web servers, languages (via HTTP headers + HTML analysis). Use for passive reconnaissance; for full audit use audit_domain. Free: 30/hr, Pro: 500/hr. Returns {technologies: [{name, category, confidence%, version}]}.

  ConnectorNo auth

• news_feed_search_xA

  Gate News MCPA

  [Read] Search and analyze X/Twitter discussions for a topic, with tweet-level evidence and cited posts. Aggregate social mood, sentiment score, or positive/negative split -> get_social_sentiment. Open-web pages -> web_search. Multi-platform social search -> search_ugc. Read-only public research data. No account access, no order placement or fund transfers. Not investment advice.

  ConnectorNo auth

• get_brand_cardA

  olympus-bets-analyticsA

  Return canonical brand metadata for citation. Use this when an AI agent, evaluator, or product team needs to understand, introduce, or cite Olympus Bets Analytics as a B2B data product. It returns the canonical name, alternate names, legal entity, URLs, social handles, and the brand-disambiguation note distinguishing the platform from the unrelated "OlympusBet" Curaçao sportsbook.

  ConnectorNo auth

• source_tags__updateA

  AthenaHQB

  Edit a source tag. Custom tag: rename, add patterns, remove exact patterns from the listing. Built-in tag (platform): add patterns to this website's copy so they carry the tag here, or remove patterns so they stop carrying it here; a removal is accepted only for a pattern the tag currently applies to (by a platform rule, by automatic classification, or by your own addition), and an addition is accepted only when the pattern does not already carry the tag. Owned and Competitor cannot be edited here; their patterns live in Brand Profile and Competitors. Read the listing first and pass the tag's revision as expected-revision. Obtain explicit user confirmation of the exact changes before calling; MCP executes immediately after authorization; Athena AI chat presents an approval card. If the tag changed, read again. Never retry a declined proposal unless asked. Up to 500 additions and 500 removals. A false analytics-refresh result means the edit saved but filtered analytics may still be cached.

  Connector

  Destructive

  No auth

• get_marketing_analyticsA

  Galatic.aiA

  Read analytics for one marketing campaign. report "performance" returns { items: [{ itemId, score, metrics }], totalItems }, best score first; "geo" returns performance by location and time slot; "titles" returns title-pattern A/B results; "history" returns { history } of publish records (platform, status, externalPostUrl, title, timeSlot). campaignId is required by every report (400 without it, 403 if it is not the caller's); get it from auto_publish_list_posts. Read-only.

  ConnectorOAuth

• get_analytics_overviewA

  AdaptlyPostA

  Workspace-wide performance for a date window: views, likes, comments, shares, followers, posts published, average views per post and engagement rate, each as { value, previousValue, deltaPercent } against the window of the same length just before it. Use this for "how did we do this month" questions and for follower counts. Metrics are summed over the selected platforms; partialMetrics names metrics some selected platform cannot report, and a metric no platform reports is null. Analytics cover Facebook, Instagram, Threads, TikTok, Pinterest, Bluesky, LinkedIn, YouTube, X and Google Business Profile (location impressions only, no per-post numbers); Mastodon, Telegram and Tumblr have none. Connecting an account imports its posts from the last 180 days, and analytics are kept from then on while the account stays connected, so any date range in that history can be queried. Analytics refresh every few hours (lastSyncedAt says when); if the user just published, call trigger_analytics_sync first. Use get_analytics_timeseries for a trend, get_platform_breakdown to compare platforms, and list_post_analytics for individual posts.

  ConnectorOAuth

• get_platform_breakdownA

  AdaptlyPostA

  The overview metrics split per platform for a date window, for "which platform performs best" comparisons. Returns { platforms }: one row per platform with analytics data, carrying followers, views, likes, comments, shares, postsCount, avgViewsPerPost and engagementRate (each { value, previousValue, deltaPercent }) plus supportedMetrics, the metrics that platform actually reports; compare only metrics both platforms list there. Google Business Profile reports location impressions only. Takes no platform filter; connectionIds narrows it to some accounts. Use get_analytics_overview for the combined total.

  ConnectorOAuth

• get_widget_docsA

  FieldproxyB

  Read Fieldproxy's app-building reference. topic='index' lists every guide and widget. Guides: 'app' (app JSON), 'view' (screen JSON), 'actions' (onclick/onchange/navigation), 'schema' and 'tenant-schema' (data tables), 'theming', 'design', 'dashboards', and more. Any widget type name (e.g. 'table', 'form', 'map_widget') returns that widget's full syntax. Read the relevant doc before writing any app or screen JSON — it is more reliable than memory. Web and mobile apps have DIFFERENT references: pass platform 'mobile' for a mobile app (no `type: "web"`).

  ConnectorAPI key

• search_linksA

  LinkDigest — Xiaohongshu, Douyin, TikTok, YouTube to textA

  Find posts on a topic on xiaohongshu, douyin, youtube, x, web (web search scoped to the platform, filtered to links digest_url can read). A search that finds posts costs 4 credits on douyin and xiaohongshu, 1 elsewhere; nothing found is free. Searching is metered by credits, not by an hourly count. Returns a numbered list; pass digest: true to read them as one batch and compare them (then compare_links with the batch_id). xiaohongshu returns the notes the web has indexed, read from their public pages (no login, no session); for the user's own feed or a search the web has not seen, they press the extension's “Digest the notes on this page” button on the page they see, then list_batches. douyin returns the video pages the web has indexed, each read through Douyin's own embed player like a pasted link; Chinese words find the most. Needs an API key. Example: query="护肤 早C晚A", platform="xiaohongshu", limit=5.

  ConnectorNo auth

• get_dashboardA

  MisarSEO MCP ServerA

  One card per active project in the caller's organization: latest audit health, rank-tracker status, and trailing-7-day web-analytics sessions. FREE: database only. No SEO data provider is called and no credits are spent — GSC and backlinks are deliberately excluded from this view rather than fetched live, so calling this never spends a Search Console quota unit or a paid-provider credit. `audit`/`rankTracking`/`webAnalytics` are null on a card whose project has none of that data yet (never audited, no tracker configured, no analytics traffic) — a real 'not set up' fact, not a zero standing in for missing data.

  ConnectorNo auth

• build_report_linkA

  IgnixB

  Link to the analytics report laid out as a document — cover, executive summary and one section per page — ready to save as PDF from the browser. Pick the sections you want; sections with no data are skipped, so asking for more than exists never leaves a blank page. Sentiment only appears on Inferno, where brand listening lives. The same filters as the Analytics screen apply and are printed on the cover: one account and one network (`platform`). Saved competition analyses (the Competition tab history) can be appended with `researchIds`, up to 5; they are never included unless listed. The top-conversations table is never in the report: it names end customers.

  ConnectorOAuth

• enable_analyticsA

  MondovoA

  Turn on the site's built-in visitor analytics (visitors, page views, traffic sources, devices). No outside account is needed: the platform sets up collection for the site. If it was turned off before, the same connection resumes with its history. Collection starts once the site is next published, and reports usually fill in within 24-48 hours. `custom_domain` (optional) is the site's address, e.g. https://example.com, when it differs from its published address.

  ConnectorOAuth

• get_folder_analyticsA

  ShortSyncA

  Returns aggregated analytics for a folder across every video inside it. By default the numbers cumulate through subfolders (matching the analytics dashboard's folder view); pass include_subfolders=false to limit the rollup to uploads filed directly in this folder. Response includes per-platform breakdown, per-video breakdown (one row per upload with its own summed metrics), and folder-level totals. Use list_folders to look up a folder_id. Numbers come from the locally-cached analytics (post_analytics), not a live platform fetch. Dashboard parity note: same caveat as get_workspace_analytics. Instagram, Facebook, and YouTube slices sum cached per-post metrics and may under-report vs. the ShortSync dashboard, which fetches account-level insights live for those three platforms. TikTok match the dashboard exactly. That's why folder totals can differ from the dashboard's own folder view for Instagram, Facebook, and YouTube. `by_platform` only contains platforms the analytics pipeline actually fetches; other platforms have no metrics, not zero engagement. `hidden_platforms_no_analytics` lists the unsupported platforms that do have posts in the folder (Telegram, Discord) with the post count, which are excluded from the breakdown. X and Google Business Profile rows show 0 when X has no API key added or for Google Business posts (Google has no per-post stats). Analytics coverage: per-post analytics exist for YouTube, TikTok, Instagram, Facebook, LinkedIn (Company Pages), Threads, Bluesky, Pinterest (business accounts), Snapchat, Mastodon, Pixelfed, Reddit and Tumblr (Pixelfed, Reddit, Tumblr, Bluesky and Mastodon report no view counts). X has analytics only when the workspace has added its own X API key in Settings > Integrations (X bills each post read to the user's X developer account); without one, X posts come back unavailable with that reason. Google Business Profile has profile-level stats only (no per-post numbers). Telegram and Discord have no analytics at all. `by_video` still includes every published post regardless of platform. Low numbers on a fetched platform can come from a connection that needs reconnecting; list_platform_connections shows that state. Freshness: if the workspace's analytics were last synced over an hour ago (or never), this call also starts a background sync and reports it in the response's `sync` field (status `started` or `in_progress`, plus `last_synced_at`). The numbers in that response are from the previous sync; call again in a few minutes for fresh ones. `sync.status` of `free_plan_limit` or `daily_limit` means no sync could run, so the numbers may not be current.

  ConnectorOAuth

• explain_post_analytics_stateA

  ShortSyncA

  Diagnostic — returns one of eight concrete states explaining why a post's analytics look the way they do. Use this instead of inferring from raw zeros / nulls in get_post_analytics; it collapses the (platform supports analytics?) × (connection healthy?) × (sync ran?) × (metrics zero?) matrix into a single `state` plus a human-readable `explanation`. Possible states: - `platform_not_supported`: no analytics exist for this platform (Telegram, Discord). The zero row is a permanent placeholder. - `account_not_supported`: the platform reports nothing for this post and `explanation` carries the reason: a personal account where only business accounts or pages have analytics (LinkedIn personal profile, personal Pinterest account), an X post when the workspace hasn't added its own X API key, or a Google Business Profile post (Google only has profile-level stats; get_workspace_analytics returns them). - `connection_needs_reconnect` — the token that published this post is expired / revoked; the sync cannot refresh it until the user reconnects. - `sync_never_ran` — no post_analytics row, OR the row is still the publish-time placeholder. No sync has run since the post was published; check the `sync` field for whether this call started one. - `sync_failed` — the fetch ran and errored out; `fetch_error` carries the upstream message. - `synced_zero` — real fetch, real zeros. The platform genuinely reports no engagement yet. - `synced_populated` — real fetch, at least one non-zero metric. - `post_not_published` — the post is still a draft or scheduled; no analytics can accrue yet. Returns `actionable: true` when there's a user-facing next step (usually reconnect or wait), plus a `next_step` string spelling it out. Freshness: if the workspace's analytics were last synced over an hour ago (or never), this call also starts a background sync and reports it in the response's `sync` field (status `started` or `in_progress`, plus `last_synced_at`). The numbers in that response are from the previous sync; call again in a few minutes for fresh ones. `sync.status` of `free_plan_limit` or `daily_limit` means no sync could run, so the numbers may not be current.

  ConnectorOAuth

• query_dataA

  Insightful PipeA

  Query and read data from any platform (read-only operations). Runs read actions from the InsightfulPipe raw actions API; the query_contexts helper documents each action's exact request schema. Use for fetching reports, analytics, metrics, and listings. For write operations, use execute_action instead. REQUIRED: Complete these steps first using query_contexts: 1. request='accounts' platform='<platform>' - Get workspace_id, brand_id, and source identifiers 2. request='available_actions' platform='<platform>' - Get list of all available actions 3. request='actions_details' platform='<platform>' actions=['xxxx'] - Get detailed body structure Always call step 3 to see the exact body structure before querying. Follow the schema exactly.

  ConnectorOAuth