Holistics MCP server

What the model can do

Holistics BI: dashboards with their widgets and filters, data schedules and data alerts (destination type and how many recipients), users by id, initials and group, datasets with their models and fields, semantic-layer queries on a dataset (run on the company's warehouse), and job status; can run a schedule or alert now, pause or resume a schedule, delete schedules, alerts and dashboards, preload a dashboard's cache, invite, re-invite, change the role of, deactivate or restore users, add or remove users from groups, and add or remove tags on dashboards and datasets.

Reads

• holistics_list_dashboardsHolistics dashboards: id, title, owner id, category (folder) id, version, URL, tags and how many widgets.
• holistics_get_dashboardOne Holistics dashboard: title, URL, tags, its filters (id and name, needed to filter a preload) and its widgets (id, title, source type and id).
• holistics_list_schedulesHolistics data schedules (scheduled report deliveries): id, title, the dashboard or report it sends, its repeat rule, whether paused…
• holistics_list_alertsHolistics data alerts: id, title, the widget it watches, how often it checks, whether paused, how many conditions…
• holistics_list_usersHolistics users by id, initials, status and group names: use it to find the id of a user to act on.
• holistics_get_datasetA Holistics dataset's models and fields: for each model its name and label, and each field's name, label, type and aggregation.
• holistics_query_datasetRuns a semantic-layer query on a Holistics dataset: dimensions to group by (model.field, optionally truncated to a date part), metrics to aggregate…
• holistics_get_jobA Holistics job's status (created, queued, running, success, failure, cancelled), when it started and ended, and its error if it failed.

Acts, when you ask

These change something in Holistics. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• holistics_run_scheduleRuns a Holistics data schedule now: Holistics runs its queries on the warehouse and delivers the report to the schedule's destination…
• holistics_run_alertRuns a Holistics data alert now: Holistics checks its conditions on the warehouse, and if they match it sends to the alert's destination…
• holistics_pause_schedulePauses or resumes a Holistics data schedule.
• holistics_delete_schedulePermanently deletes a Holistics data schedule; its recipients stop receiving the report.
• holistics_delete_alertPermanently deletes a Holistics data alert; it stops checking and sending.
• holistics_delete_dashboardDeletes a Holistics dashboard for everyone who uses it, along with its widgets.
• holistics_preload_dashboardPreloads a Holistics dashboard: runs every widget's query on the company's warehouse…
• holistics_invite_usersInvites people to Holistics by email with a role, optionally into groups.
• holistics_resend_inviteResends a pending Holistics user's invitation email.
• holistics_set_user_roleChanges a Holistics user's role (user, explorer, analyst, admin, growth_admin, it_admin)…
• holistics_deactivate_userDeactivates a Holistics user (a soft delete): they can no longer sign in or use Holistics, and their API key stops working.
• holistics_restore_userRestores a deactivated Holistics user, giving them back access with their previous role.
• holistics_add_user_to_groupAdds a Holistics user to a group, giving them whatever the group can see.
• holistics_remove_user_from_groupRemoves a Holistics user from a group, taking away what they could see only through it.
• holistics_tag_objectAdds or removes tags on a Holistics dashboard or dataset, named by its uname (the AML object name).

Connect it

First connect Holistics on Dashboard → Connections, then add Memtro to your client once. The Holistics tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Holistics connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › What was GMV by country last month?
• › Which schedules email the board, and how often?
• › Which data alerts are paused?
• › What fields does the orders dataset have?
• › Pause the weekly sales schedule until further notice.

Questions

Is this an official Holistics MCP server?

No. It is Memtro's MCP server with Memtro's Holistics connector behind it: the connector reads Holistics through its API with the credentials you connect on Dashboard → Connections, and Holistics publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Holistics?

Only when you ask, and only what it has been granted: run a data schedule now (delivers to its recipients); run a data alert now (sends to its destination if its condition matches); pause or resume a data schedule; delete a data schedule (permanent); delete a data alert (permanent); delete a dashboard (permanent); preload a dashboard's cache (runs its queries); invite users by email with a role; resend a user's invitation email; change a user's role; deactivate a user (soft delete); restore a deactivated user; add a user to a group; remove a user from a group; add or remove tags on a dashboard or dataset. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Analytics

• Google Analytics 4 MCP server
• Plausible Analytics MCP server
• Umami MCP server
• Google Search Console MCP server
• Segment MCP server
• App Store Connect MCP server