Connect
Optimize
Secure
Domo MCP Server
for AI Agents
Production-ready Domo MCP server with 21 extensible actions — plus built-in authentication, security, and optimized execution.
Domo MCP Server
Built by 
StackOne
StackOne 
Coverage
21 Agent Actions
Create, read, update, and delete across Domo — and extend your agent's capabilities with custom actions.
Authentication
Agent Tool Authentication
Per-user OAuth in one call. Your Domo MCP server gets session-scoped tokens with zero credentials stored on your infra.
Agent Auth →
Security
Agent Protection
Every Domo tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.
Prompt Injection Defense →
Performance
Max Agent Context. Min Cost.
Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Domo call.
Tools Discovery →What is the Domo MCP Server?
A Domo MCP server lets AI agents read and write Domo data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's Domo MCP server ships with 21 pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, and optimized agent context. Connect it from MCP clients like Claude Desktop, Claude Code, Cursor, Goose, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.
All Domo MCP Tools and Actions
Every action from Domo's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.
Activity Logs
- List Activity Logs
Retrieve activity log entries filtered by time range via GET /v1/audit. Requires the 'start' timestamp parameter.
Groups
- Create Group
Create a new group in your Domo instance via POST /v1/groups
- List Groups
Retrieve a paginated list of all groups in your Domo instance via GET /v1/groups
- Get Group
Retrieve full details of a single group by its numeric ID via GET /v1/groups/{id}
- Update Group
Update an existing group's attributes via PUT /v1/groups/{id}. All fields (name, active, default) are required.
- Delete Group
Permanently delete a group via DELETE /v1/groups/{id}. The group must have no users before deletion.
Group Users
- List Group Users
List the user IDs belonging to a group via GET /v1/groups/{id}/users. Returns only user IDs, not full user objects.
User To Groups
- Add User To Group
Add a user to a group via PUT /v1/groups/{groupId}/users/{userId}. Returns 204 No Content on success.
User From Groups
- Remove User From Group
Remove a user from a group via DELETE /v1/groups/{groupId}/users/{userId}. Returns 204 No Content on success.
Current IAM Credentials
- Get Current IAM Credentials
Return the authenticated identity, granted OAuth scopes, and auth type for the current Domo connection, mapped to the IAM unified credentials schema.
IAM Groups
- List IAM Groups
List all groups in the Domo instance mapped to the IAM unified group schema, paginated 100 per page. Each entry surfaces the group's stable id, name, and active status.
- Get IAM Group
Retrieve a single Domo group by numeric ID, mapped to the IAM unified group schema. Optionally pass expand=["users"] to inline the first page of member user IDs.
IAM Roles
- List IAM Roles
Return the five stable workspace-level IAM roles synthesized from Domo system role strings (Admin, Privileged, Editor, Participant, Social). The role set is static and matches the role IDs embedded in IamUser.roles[] on this connector.
- Get IAM Role
Retrieve a single synthesized Domo IAM role by its stable key. Only "admin", "privileged", "editor", "participant", and "social" are valid — the role namespace is closed to Domo system roles only.
IAM Users
- List IAM Users
List all users in the Domo instance mapped to the IAM unified user schema, paginated 100 per page. Each user includes their role synthesized as a workspace-scoped IAM role.
- Get IAM User
Retrieve a single Domo user by numeric ID, mapped to the IAM unified user schema. Optionally pass expand=["groups"] to inline the groups the user belongs to.
Users
- Create User
Create a new user in your Domo instance via POST /v1/users with the sendInvite query parameter
- List Users
Retrieve a paginated list of all users in your Domo instance via GET /v1/users
- Get User
Retrieve full details of a single user by their numeric ID via GET /v1/users/{id}
- Update User
Update an existing user's attributes via PUT /v1/users/{id}. Known Domo limitation requires all user fields to be provided.
- Delete User
Permanently delete a user via DELETE /v1/users/{id}. This action is irreversible.
Set Up Your Domo MCP Server in Minutes
One endpoint. Any framework. Your agent is talking to Domo in under 10 lines of code.
MCP Clients
Agent Frameworks
JSON{
"mcpServers": {
"stackone": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://api.stackone.com/mcp?x-account-id=<account_id>",
"--header",
"Authorization: Basic <YOUR_BASE64_TOKEN>"
]
}
}
}More Data & Analytics MCP Servers
Tableau
122+ actions
SurveyMonkey
104+ actions
Microsoft Excel
101+ actions
Qlik
100+ actions
Snowflake
80+ actions
Smartsheet
78+ actions
PostHog
63+ actions
Domo MCP Server Resources
MCP Code Mode: Keeping Tool Responses Out of Agent Context
Anthropic's code_execution processes data already in context. Custom MCP code mode keeps raw tool responses in a sandbox. 14K tokens vs 500.
11 min
Comparing BM25, TF-IDF, and Hybrid Search for MCP Tool Discovery
Benchmarking BM25, TF-IDF, and hybrid search for MCP tool discovery across 916 tools. The 80/20 TF-IDF/BM25 hybrid hits 21% Top-1 accuracy in under 1ms.
10 min
Indirect Prompt Injection Defense for MCP Tools: A Technical Guide
MCP tools that read emails, CRM records, and tickets are indirect prompt injection vectors. Here's how we built a two-tier defense that scans tool results in ~11ms.
12 min
Domo MCP Server FAQ
Domo MCP server vs direct API integration — what's the difference?
A Domo MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling Domo. A Domo MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling Domo at runtime. StackOne provides both.
How does Domo authentication work for AI agents?
Domo authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Domo account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via
origin_owner_id.Are Domo MCP tools vulnerable to prompt injection?
Yes — Domo MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a Domo agent and how do I avoid it?
Context bloat happens when Domo tool schemas and API responses eat your Domo agent's memory, preventing it from reasoning effectively. A single Domo query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my Domo agent can access?
Yes — you can limit which actions your Domo agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Domo MCP server?
Yes — you can create custom agent actions for your Domo MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Domo's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Domo MCP server?
Skip a Domo MCP server if your integration is purely software-to-software — direct Domo API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Domo actions at runtime.
What AI frameworks and AI clients does the StackOne Domo MCP server support?
The StackOne Domo MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.
Put your AI agents to work
All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.