Skip to content

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.

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
  • 87actionsin one signed file
  • 36readlook, never change
  • 37writecreate and update
  • 14wait for a yesdestructive, 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_idDomo client ID: developer.domo.com > My Account > New Client (sign in with your Domo instance)
    • client_secretDomo 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 callcheck { 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_idclient_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 2026OpenAPI spec (GitHub)OpenAPI spec (GitHub)OpenAPI spec (GitHub)
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.

  • 36readlook, never change
  • 37writecreate and update
  • 14destructivewait 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.

ActionWhat it doesEffectSame name in
domo.users.listList usersList users.readidentity.user.list474 connectors
domo.groups.listList groupsList groups.readidentity.group.list262 connectors
domo.pages.listList pagesList pages.readanalytics.report.list37 connectors
domo.datasets.listList DataSetsList DataSets.readanalytics.dataset.list28 connectors
domo.projects.listList projectsList projects.readwork.project.list109 connectors
domo.users.getRetrieve a userRetrieve a user.readidentity.user.get399 connectors
domo.datasets.createCreate a DataSetCreate a DataSet.writeanalytics.dataset.create21 connectors
domo.groups.createCreate a groupCreate a group.writeidentity.group.create205 connectors
domo.pages.createCreate a pageCreate a page.writeanalytics.report.create27 connectors
domo.users.deleteDelete a userDelete a user.destructiveidentity.user.delete253 connectors
domo.projects.createCreate a projectCreate a project.writework.project.create102 connectors
domo.tasks.createCreate a taskCreate a task.writework.task.create127 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. Readread

    Give me a one-line status for every active Domo project.

    callsdomo.projects.list

  2. Writewrite

    Create a DataSet in Domo. Show me exactly what you will send before you save it.

    callsdomo.datasets.create

Governance for Domo

Destructive actions wait for a yes.

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

  • Delete a userdomo.users.delete
  • Delete a groupdomo.groups.delete
  • Delete a DataSetdomo.datasets.delete
  • Delete a pagedomo.pages.delete
  • Delete a projectdomo.projects.delete
  • Delete a Streamdomo.streams.delete
  • Delete an accountdomo.accounts.delete
  • Remove a user from a groupdomo.group_users.remove
  • Delete a project listdomo.project_lists.delete
  • Delete a PDP policydomo.dataset_policies.delete
  • Delete a page collectiondomo.page_collections.delete
  • Delete a task attachmentdomo.task_attachments.delete
  • Abort a Stream executiondomo.stream_executions.abort
  • Abort the current Stream executiondomo.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.

dodomo.users.deleteconfirm_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: "[email protected]" },    { match: "domo.groups.delete", approver: "[email protected]" },    { match: "domo.datasets.delete", approver: "[email protected]" }  ]}
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.

  • 1upstream call per actionall 87 Domo actions
  • 87actions pageeach page of a long list is one call
  • 36reads can be cacheda cache hit costs nothing
  • 100,000calls a month, freepaid plans from US$49 a month for 250,000

See pricing

Action index

Every Domo action.

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

Datasets7
  • domo.datasets.createCreate a DataSetwrite
  • domo.datasets.deleteDelete a DataSetdestructive
  • domo.datasets.getRetrieve a DataSetread
  • domo.datasets.import_csvImport data into a DataSetwrite
  • domo.datasets.listList DataSetsread
  • domo.datasets.queryQuery a DataSetread
  • domo.datasets.updateUpdate a DataSetwrite
Stream executions7
  • domo.stream_executions.abortAbort a Stream executiondestructive
  • domo.stream_executions.abort_currentAbort the current Stream executiondestructive
  • domo.stream_executions.commitCommit a Stream executionwrite
  • domo.stream_executions.createCreate a Stream executionwrite
  • domo.stream_executions.getRetrieve a Stream executionread
  • domo.stream_executions.listList Stream executionsread
  • domo.stream_executions.upload_partUpload a data partwrite
Accounts6
  • domo.accounts.createCreate an accountwrite
  • domo.accounts.deleteDelete an accountdestructive
  • domo.accounts.getRetrieve an accountread
  • domo.accounts.listList accountsread
  • domo.accounts.shareShare an accountwrite
  • domo.accounts.updateUpdate an accountwrite
Streams6
  • domo.streams.createCreate a Streamwrite
  • domo.streams.deleteDelete a Streamdestructive
  • domo.streams.getRetrieve a Streamread
  • domo.streams.listList Streamsread
  • domo.streams.searchSearch Streamsread
  • domo.streams.updateUpdate a Streamwrite
Dataset policies5
  • domo.dataset_policies.createCreate a PDP policywrite
  • domo.dataset_policies.deleteDelete a PDP policydestructive
  • domo.dataset_policies.getRetrieve a PDP policyread
  • domo.dataset_policies.listList PDP policiesread
  • domo.dataset_policies.updateUpdate a PDP policywrite
Groups5
  • domo.groups.createCreate a groupwrite
  • domo.groups.deleteDelete a groupdestructive
  • domo.groups.getRetrieve a groupread
  • domo.groups.listList groupsread
  • domo.groups.updateUpdate a groupwrite
Pages5
  • domo.pages.createCreate a pagewrite
  • domo.pages.deleteDelete a pagedestructive
  • domo.pages.getRetrieve a pageread
  • domo.pages.listList pagesread
  • domo.pages.updateUpdate a pagewrite
Project lists5
  • domo.project_lists.createCreate a project listwrite
  • domo.project_lists.deleteDelete a project listdestructive
  • domo.project_lists.getRetrieve a project listread
  • domo.project_lists.listList project listsread
  • domo.project_lists.updateUpdate a project listwrite
Projects5
  • domo.projects.createCreate a projectwrite
  • domo.projects.deleteDelete a projectdestructive
  • domo.projects.getRetrieve a projectread
  • domo.projects.listList projectsread
  • domo.projects.updateUpdate a projectwrite
Users5
  • domo.users.createCreate a userwrite
  • domo.users.deleteDelete a userdestructive
  • domo.users.getRetrieve a userread
  • domo.users.listList usersread
  • domo.users.updateUpdate a userwrite
Page collections4
  • domo.page_collections.createCreate a page collectionwrite
  • domo.page_collections.deleteDelete a page collectiondestructive
  • domo.page_collections.listList page collectionsread
  • domo.page_collections.updateUpdate a page collectionwrite
Chart cards3
  • domo.chart_cards.createCreate a chart cardwrite
  • domo.chart_cards.getRetrieve a chart card definitionread
  • domo.chart_cards.updateUpdate a chart card definitionwrite
Group users3
  • domo.group_users.addAdd a user to a groupwrite
  • domo.group_users.listList users in a groupread
  • domo.group_users.removeRemove a user from a groupdestructive
Tasks3
  • domo.tasks.createCreate a taskwrite
  • domo.tasks.getRetrieve a taskread
  • domo.tasks.updateUpdate a taskwrite
Account types2
  • domo.account_types.getRetrieve an account typeread
  • domo.account_types.listList account typesread
Cards2
  • domo.cards.getRetrieve a cardread
  • domo.cards.listList cardsread
Json datasets2
  • domo.json_datasets.createCreate a JSON DataSetwrite
  • domo.json_datasets.importImport JSON rows into a DataSetwrite
Project members2
  • domo.project_members.listList project membersread
  • domo.project_members.updateUpdate project memberswrite
Task attachments2
  • domo.task_attachments.deleteDelete a task attachmentdestructive
  • domo.task_attachments.listList task attachmentsread
Audit entries1
  • domo.audit_entries.listList activity log entriesread
Card embed tokens1
  • domo.card_embed_tokens.createCreate a card embed tokenwrite
Chart card drillpath1
  • domo.chart_card_drillpath.getRetrieve drill propertiesread
Chart card drills1
  • domo.chart_card_drills.createAdd a drill viewwrite
Dashboard embed tokens1
  • domo.dashboard_embed_tokens.createCreate a dashboard embed tokenwrite
Dataset exports S31
  • domo.dataset_exports_s3.createExport a DataSet to S3write
List tasks1
  • domo.list_tasks.listList tasks in a listread
Project tasks1
  • domo.project_tasks.listList project tasksread

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.

Give your agent Domo today.

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