---
title: "Domo MCP server for AI agents - actionlake"
description: "Give Claude 87 Domo actions through one MCP server: datasets, stream executions, accounts. Your agent never holds the credential. 100,000 calls a month free."
canonical: https://actionlake.com/connectors/domo
updated: 2026-10-23
---

Connectors · Observability & analytics

# Domo MCP server for AI agents.

actionlake is an MCP gateway: one remote MCP server that connects Claude and other MCP clients to Domo and the rest of your systems. It gives your agent 87 Domo actions (36 reads, 37 writes and 14 that wait for a confirmation) and holds the Domo credential itself, so the agent never does. It paces Domo's limits and records every call.

[Connect Domo free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

100,000 free calls a month. No card, no email, no password: press Start a free sandbox on the next screen and keep the key it shows you.

`claude mcp add --transport http actionlake https://connect.actionlake.com/mcp`

the first call

```
do {
  action: "domo.users.list",
  intent: "check which Domo account is connected"
}
# List users · read · 1 upstream call
```

- 87 actions in one signed file
- 36 read look, never change
- 37 write create and update
- 14 wait for a yes destructive, confirmed first

Set up

## Connect Domo in three steps.

1. 01
   ### Add actionlake to Claude.
   Run the command once in Claude Code; its consent page can create a free sandbox: 100,000 calls a month, no card. In the Claude app, add a custom connector with the URL below and paste your key on the consent page. Creating a new sandbox from the Claude app is not yet tested by us.
   `https://connect.actionlake.com/mcp`
2. 02
   ### Connect Domo.
   OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in. actionlake stores what you paste write-only, sealed under your tenant's key.
   - `client_id` Domo client ID: developer.domo.com > My Account > New Client (sign in with your Domo instance)
   - `client_secret` Domo client secret, shown with the client ID when the client is created
   ```
   account { op: "connections.requirements", service: "domo" }
   # free: exactly what to paste, and what is found for you
   ```
3. 03
   ### Make the first call. Check before a write.
   Ask in plain words; Claude picks the action. Before anything changes, `check` validates the call and prices it, for free.
   ```
   do    { action: "domo.users.list" }
   # list users · read · 1 upstream call
   check { action: "domo.datasets.create", input: { … } }
   # free: inputs, permissions, cost and confirmations, nothing sent
   ```

Domo at a glance

**Sign-in**

OAuth 2.0, client credentials. Paste the app's client id and secret; actionlake fetches and renews the token, and nobody has to sign in.

**You provide**

`client_id` `client_secret`

**Limits we pace to**

600 calls a minute, per connection

**API covered**

Domo (BI platform: DataSets, Streams, cards, pages, users, groups, projects) API Domo Platform APIs (api.domo.com v1, OpenAPI from DomoApps/domo-documentation-hub)`api.domo.com`

**Built from**

Domo's documentation, read 23 October 2026[OpenAPI spec (GitHub)](https://github.com/DomoApps/domo-documentation-hub/blob/HEAD/openapi/platform/accounts.yaml) [OpenAPI spec (GitHub)](https://github.com/DomoApps/domo-documentation-hub/blob/HEAD/openapi/platform/activity.yaml) [OpenAPI spec (GitHub)](https://github.com/DomoApps/domo-documentation-hub/blob/HEAD/openapi/platform/cards.yaml)

**Service file**

Version 1.0.0, signed (Ed25519)

**Cached reads**

36 of 36 reads, for up to 5 minutes; a write clears what it affects

**Shared entities**

5, so ask can line Domo up with your other systems

**Data**

Processed and stored in Sydney, Australia. No US region yet

Capabilities

## What an AI agent can do in Domo.

87 actions in 27 areas. Every one carries its effect, so a key can allow the reads and hold the rest.

- **36** read look, never change
- **37** write create and update
- **14** destructive wait for a confirmation

1. ### Datasets
   7
   3 read · 3 write · 1 destructive
   List DataSets · Create a DataSet · Query a DataSet · Retrieve a DataSet
2. ### Stream executions
   7
   2 read · 3 write · 2 destructive
   Create a Stream execution · List Stream executions · Commit a Stream execution · Retrieve a Stream execution
3. ### Accounts
   6
   2 read · 3 write · 1 destructive
   Create an account · List accounts · Share an account · Retrieve an account
4. ### Streams
   6
   3 read · 2 write · 1 destructive
   List Streams · Create a Stream · Search Streams · Retrieve a Stream
5. ### Dataset policies
   5
   2 read · 2 write · 1 destructive
   Create a PDP policy · List PDP policies · Retrieve a PDP policy · Update a PDP policy
6. ### Groups
   5
   2 read · 2 write · 1 destructive
   List groups · Create a group · Retrieve a group · Update a group
7. ### Pages
   5
   2 read · 2 write · 1 destructive
   List pages · Create a page · Retrieve a page · Update a page
8. ### Project lists
   5
   2 read · 2 write · 1 destructive
   Create a project list · List project lists · Retrieve a project list · Update a project list

**19 more areas · 41 actions**

- Projects **5**
- Users **5**
- Page collections **4**
- Chart cards **3**
- Group users **3**
- Tasks **3**
- Account types **2**
- Cards **2**
- Json datasets **2**
- Project members **2**
- Task attachments **2**
- Audit entries **1**
- Card embed tokens **1**
- Chart card drillpath **1**
- Chart card drills **1**
- Dashboard embed tokens **1**
- Dataset exports S3 **1**
- List tasks **1**
- Project tasks **1**

Top actions

## The Domo API, shaped for agents.

The ids your agent types, what each does, and the one name it shares with other systems. 30 of Domo's 30 action names are shared with at least one other connector, so an agent learns them once.

| Action | What it does | Effect | Same name in |
| --- | --- | --- | --- |
| `domo.users.list` List users | List users. | read | `identity.user.list` 474 connectors |
| `domo.groups.list` List groups | List groups. | read | `identity.group.list` 262 connectors |
| `domo.pages.list` List pages | List pages. | read | `analytics.report.list` 37 connectors |
| `domo.datasets.list` List DataSets | List DataSets. | read | `analytics.dataset.list` 28 connectors |
| `domo.projects.list` List projects | List projects. | read | `work.project.list` 109 connectors |
| `domo.users.get` Retrieve a user | Retrieve a user. | read | `identity.user.get` 399 connectors |
| `domo.datasets.create` Create a DataSet | Create a DataSet. | write | `analytics.dataset.create` 21 connectors |
| `domo.groups.create` Create a group | Create a group. | write | `identity.group.create` 205 connectors |
| `domo.pages.create` Create a page | Create a page. | write | `analytics.report.create` 27 connectors |
| `domo.users.delete` Delete a user | Delete a user. | destructive | `identity.user.delete` 253 connectors |
| `domo.projects.create` Create a project | Create a project. | write | `work.project.create` 102 connectors |
| `domo.tasks.create` Create a task | Create a task. | write | `work.task.create` 127 connectors |

Try it

## Prompts to paste into Claude.

Each one names the Domo actions it will call, so you know what it reads and what it changes before you send it.

1. Read read
   Give me a one-line status for every active Domo project.
   calls `domo.projects.list`
2. Write write
   Create a DataSet in Domo. Show me exactly what you will send before you save it.
   calls `domo.datasets.create`

Governance for Domo

## Destructive actions wait for a yes.

14 Domo actions are destructive. These are all of them:

- Delete a user `domo.users.delete`
- Delete a group `domo.groups.delete`
- Delete a DataSet `domo.datasets.delete`
- Delete a page `domo.pages.delete`
- Delete a project `domo.projects.delete`
- Delete a Stream `domo.streams.delete`
- Delete an account `domo.accounts.delete`
- Remove a user from a group `domo.group_users.remove`
- Delete a project list `domo.project_lists.delete`
- Delete a PDP policy `domo.dataset_policies.delete`
- Delete a page collection `domo.page_collections.delete`
- Delete a task attachment `domo.task_attachments.delete`
- Abort a Stream execution `domo.stream_executions.abort`
- Abort the current Stream execution `domo.stream_executions.abort_current`

A destructive action runs only with `confirm: true`. Under the `human` policy the agent cannot confirm for itself: the run stops until a named person approves, in the console or from a signed link in an email. The cap on a key is refused before the call is sent, never after.

do domo.users.delete confirm_policy: **human**

Delete a user?

**intent:** the user asked me to delete a user

run suspended · waiting for a named person · key _domo-agent_ cannot confirm itself

In the console, or from an emailed signed link.

a key for this connector

```
account {
  op: "keys.create", name: "domo-agent",
  allowed_actions: ["domo.*"], cap_calls: 2000,
  confirm_policy: "human_for_writes",
  approval_rules: [
    { match: "domo.users.delete", approver: "lead@example.com" },
    { match: "domo.groups.delete", approver: "lead@example.com" },
    { match: "domo.datasets.delete", approver: "lead@example.com" }
  ]
}
```

Illustrative. Scoped to Domo only, capped at 2,000 upstream calls, every write confirmed, and the destructive ones approved by a named person.

Cost

## What Domo costs on actionlake.

Every Domo action is one upstream call, the only thing actionlake bills. Searching, `check`, `cost`, `account` and any call Domo refused with 401, 403, 429 or a 5xx are free. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

- 1 upstream call per action all 87 Domo actions
- 87 actions page each page of a long list is one call
- 36 reads can be cached a cache hit costs nothing
- 100,000 calls a month, free paid plans from US$49 a month for 250,000

[See pricing](https://actionlake.com/pricing)

Action index

## Every Domo action.

87 actions by area: the id your agent calls, what it does, and its effect.

**Datasets 7**

- `domo.datasets.create` Create a DataSet write
- `domo.datasets.delete` Delete a DataSet destructive
- `domo.datasets.get` Retrieve a DataSet read
- `domo.datasets.import_csv` Import data into a DataSet write
- `domo.datasets.list` List DataSets read
- `domo.datasets.query` Query a DataSet read
- `domo.datasets.update` Update a DataSet write

**Stream executions 7**

- `domo.stream_executions.abort` Abort a Stream execution destructive
- `domo.stream_executions.abort_current` Abort the current Stream execution destructive
- `domo.stream_executions.commit` Commit a Stream execution write
- `domo.stream_executions.create` Create a Stream execution write
- `domo.stream_executions.get` Retrieve a Stream execution read
- `domo.stream_executions.list` List Stream executions read
- `domo.stream_executions.upload_part` Upload a data part write

**Accounts 6**

- `domo.accounts.create` Create an account write
- `domo.accounts.delete` Delete an account destructive
- `domo.accounts.get` Retrieve an account read
- `domo.accounts.list` List accounts read
- `domo.accounts.share` Share an account write
- `domo.accounts.update` Update an account write

**Streams 6**

- `domo.streams.create` Create a Stream write
- `domo.streams.delete` Delete a Stream destructive
- `domo.streams.get` Retrieve a Stream read
- `domo.streams.list` List Streams read
- `domo.streams.search` Search Streams read
- `domo.streams.update` Update a Stream write

**Dataset policies 5**

- `domo.dataset_policies.create` Create a PDP policy write
- `domo.dataset_policies.delete` Delete a PDP policy destructive
- `domo.dataset_policies.get` Retrieve a PDP policy read
- `domo.dataset_policies.list` List PDP policies read
- `domo.dataset_policies.update` Update a PDP policy write

**Groups 5**

- `domo.groups.create` Create a group write
- `domo.groups.delete` Delete a group destructive
- `domo.groups.get` Retrieve a group read
- `domo.groups.list` List groups read
- `domo.groups.update` Update a group write

**Pages 5**

- `domo.pages.create` Create a page write
- `domo.pages.delete` Delete a page destructive
- `domo.pages.get` Retrieve a page read
- `domo.pages.list` List pages read
- `domo.pages.update` Update a page write

**Project lists 5**

- `domo.project_lists.create` Create a project list write
- `domo.project_lists.delete` Delete a project list destructive
- `domo.project_lists.get` Retrieve a project list read
- `domo.project_lists.list` List project lists read
- `domo.project_lists.update` Update a project list write

**Projects 5**

- `domo.projects.create` Create a project write
- `domo.projects.delete` Delete a project destructive
- `domo.projects.get` Retrieve a project read
- `domo.projects.list` List projects read
- `domo.projects.update` Update a project write

**Users 5**

- `domo.users.create` Create a user write
- `domo.users.delete` Delete a user destructive
- `domo.users.get` Retrieve a user read
- `domo.users.list` List users read
- `domo.users.update` Update a user write

**Page collections 4**

- `domo.page_collections.create` Create a page collection write
- `domo.page_collections.delete` Delete a page collection destructive
- `domo.page_collections.list` List page collections read
- `domo.page_collections.update` Update a page collection write

**Chart cards 3**

- `domo.chart_cards.create` Create a chart card write
- `domo.chart_cards.get` Retrieve a chart card definition read
- `domo.chart_cards.update` Update a chart card definition write

**Group users 3**

- `domo.group_users.add` Add a user to a group write
- `domo.group_users.list` List users in a group read
- `domo.group_users.remove` Remove a user from a group destructive

**Tasks 3**

- `domo.tasks.create` Create a task write
- `domo.tasks.get` Retrieve a task read
- `domo.tasks.update` Update a task write

**Account types 2**

- `domo.account_types.get` Retrieve an account type read
- `domo.account_types.list` List account types read

**Cards 2**

- `domo.cards.get` Retrieve a card read
- `domo.cards.list` List cards read

**Json datasets 2**

- `domo.json_datasets.create` Create a JSON DataSet write
- `domo.json_datasets.import` Import JSON rows into a DataSet write

**Project members 2**

- `domo.project_members.list` List project members read
- `domo.project_members.update` Update project members write

**Task attachments 2**

- `domo.task_attachments.delete` Delete a task attachment destructive
- `domo.task_attachments.list` List task attachments read

**Audit entries 1**

- `domo.audit_entries.list` List activity log entries read

**Card embed tokens 1**

- `domo.card_embed_tokens.create` Create a card embed token write

**Chart card drillpath 1**

- `domo.chart_card_drillpath.get` Retrieve drill properties read

**Chart card drills 1**

- `domo.chart_card_drills.create` Add a drill view write

**Dashboard embed tokens 1**

- `domo.dashboard_embed_tokens.create` Create a dashboard embed token write

**Dataset exports S3 1**

- `domo.dataset_exports_s3.create` Export a DataSet to S3 write

**List tasks 1**

- `domo.list_tasks.list` List tasks in a list read

**Project tasks 1**

- `domo.project_tasks.list` List project tasks read

Questions

## The Domo MCP server, answered.

**Is there a Domo MCP server for Claude?**

Yes. actionlake is an MCP gateway: a remote MCP server that gives Claude, or another MCP client, 87 Domo actions across datasets, stream executions, accounts and streams, through the same eight tools it uses for every other connector. actionlake is independent; it is not made or endorsed by Domo.

**What do I need to connect Domo?**

Domo client ID: developer.domo.com > My Account > New Client (sign in with your Domo instance) and Domo client secret, shown with the client ID when the client is created. The free call account { op: "connections.requirements", service: "domo" } lists exactly what to paste.

**Can an AI agent delete or change things in Domo?**

Only if its key allows it, and only with an explicit confirmation. 14 Domo actions are destructive, including delete a user, delete a group and delete a DataSet. Each runs only with confirm: true. Under the human confirm policy, or an approval rule on the key, the run waits until a named person approves it.

**Will an AI agent use up my Domo API limit?**

actionlake paces every call to the limits in the Domo service file: 600 calls a minute per connection. Repeated reads are answered from cache (36 Domo actions can be), which never reaches Domo.

**What does a Domo action cost?**

One upstream call, the only unit actionlake bills. A list that pages bills one call per page (87 Domo actions page). Cache hits, searches, dry runs and calls Domo refused with 401, 403, 429 or a 5xx are free. The Free plan includes 100,000 calls a month with no card. Paid plans start at US$49 a month for 250,000 calls, with overage from US$0.30 down to US$0.18 per 1,000.

**Which Domo API does it cover?**

The Domo (BI platform: DataSets, Streams, cards, pages, users, groups, projects) API Domo Platform APIs (api.domo.com v1, OpenAPI from DomoApps/domo-documentation-hub) at api.domo.com. It is built from Domo's documentation as read on 23 October 2026. 87 actions in 27 areas, each one in the signed service file (version 1.0.0).

**Does actionlake keep my Domo data, and where?**

actionlake processes and stores data in Sydney, Australia; there is no US region yet. Reads may be cached for up to 5 minutes, and a write clears the reads it affects. Each run's request and response is kept, sealed, for your plan's trace window: 1 day on Free, 3 days on Starter, 7 days on Pro, 14 days on Team, 30 days on Business and 30 days on Enterprise. Your Domo credential is sealed under your tenant's key, never logged and never returned. Your traffic is not used to train models.

**Which AI clients can use it?**

Claude Code, tested by us end to end, and the Claude app as a custom connector, tested by us with an existing key. Other MCP clients that support remote servers over Streamable HTTP (MCP revisions 2025-06-18 and 2025-11-25) and OAuth dynamic client registration, or a bearer header, should connect the same way; we have not tested them. Or plain REST, under the same action names.

## More connectors like Domo

Shares the most action names with

- [Tableau 18](https://actionlake.com/connectors/tableau)
- [Sigma Computing 16](https://actionlake.com/connectors/sigma-computing)
- [Sentry 16](https://actionlake.com/connectors/sentry)
- [Lightdash 13](https://actionlake.com/connectors/lightdash)
- [Qlik Cloud 12](https://actionlake.com/connectors/qlik-cloud)
- [Databricks 10](https://actionlake.com/connectors/databricks)

Joins with, on shared entities

- [Braintrust 4](https://actionlake.com/connectors/braintrust)
- [HaloPSA 3](https://actionlake.com/connectors/halopsa)
- [Odoo 3](https://actionlake.com/connectors/odoo)
- [Azure DevOps Services 3](https://actionlake.com/connectors/azure-devops-services)
- [Octopus Deploy 3](https://actionlake.com/connectors/octopus-deploy)
- [Jira 3](https://actionlake.com/connectors/jira)

Browse

- [All Observability & analytics connectors](https://actionlake.com/connectors/category/observability-and-analytics)
- [All connectors](https://actionlake.com/connectors)
- [How actionlake compares](https://actionlake.com/compare)

actionlake is independent. It is not made or endorsed by Domo; the name is the vendor's own. Counts are from the Domo service file, version 1.0.0.

## Give your agent Domo today.

[Connect Domo free](https://actionlake.com/console?start=sandbox) [See pricing](https://actionlake.com/pricing)

Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.

---

Source: https://actionlake.com/connectors/domo
More: https://actionlake.com/llms.txt