Sigma Agents GA: MCP, REST invoke, and admin Agents page

Sigma Agents are generally available as of Sigma’s blog 2026-09-29—“generally available for all customers,” “rolling out today”—with the same agent reusable from the Sigma MCP server, the REST API, and a new Administration → Agents management surface (blog). Sigma’s “all customers” wording still depends on premium entitlement as Sigma states.

What shipped

Sigma’s Sep 29 post takes workbook-governed agents on live warehouse data to GA: invoke from remote-MCP assistants, call from apps/scripts/pipelines, and administer usage/ownership from one Agents page (blog, About agents).

MCP + REST + Admin

Sigma MCP server — Invoke a Sigma Agent from assistants that support remote MCP (blog-named: Claude, ChatGPT, Codex, Claude Code, Cursor, Snowflake CoCo/Cowork). Same instructions, data sources, and tools as in-workbook. MCP URL from Profile → Integrations; OAuth; account permission Use Sigma MCP with OAuth. Agent-calling is the MCP-server path—not the Sigma plugin for ChatGPT/Codex (blog, MCP help).

REST path:

POST /v2/workbooks/{workbookId}/agents/{agentId}

Full host in docs: https://api.sigmacomputing.com/v2/workbooks/{workbookId}/agents/{agentId} with messages. Calls run with the calling user’s permissions and RLS; streaming or non-streaming; optional responseFormat JSON schema. API does not store chat history even if org chat history is on. Warehouse agents are not callable via this Sigma agent endpoint—use platform APIs instead (blog, API help).

Administration → Agents — Org-wide list (token usage, accessed data, ownership), per-agent profile + execution log, AI usage dashboard by agent/user/model. Workbook publish/tag after 2026-08-24 required for an agent to appear (blog, manage help).

Pricing and availability

• Premium paid feature — confirm access with Sigma; model tokens go to the customer-brought AI provider; credit-consuming activity metered like other Sigma consumption. Sigma has not published list prices for Agents as a separate SKU in the GA post.
• Vendor stats since public beta: 1,200+ organizations, close to 6,400 agents “running in production,” 580,000+ conversations — Sigma’s figures, not independently audited (blog).

Supporting product context (as Sigma states): Input Tables write-back; Snowflake Cortex / Databricks Genie as tools; inherit warehouse RLS + Sigma permissions; Slack/Jira/Salesforce via API/MCP; schedule / chat / webhook (blog).

Related products

This is Sigma Computing Agents—not MongoDB Atlas Agent Engine, not Amazon Bedrock Managed Agents, and not Kong Volcano.

Who should care

Analytics teams that want governed agents on warehouse data, callable from Cursor/Claude-style MCP clients or from POST /v2/workbooks/{workbookId}/agents/{agentId}, should start at the Sigma Agents GA post.