Can AI agents automate Sigma?

Sigma is automatable today through its REST API. The API is documented as REST and OpenAPI. Base URLs depend on the cloud, such as https://api.sigmacomputing.com for GCP and https://aws-api.sigmacomputing.com for AWS US West. An administrator, or a member with Create API keys, creates a client ID and secret under Administration, Developer access, with the REST API scope. POST /v2/auth/token with grant_type client_credentials returns a bearer access token that expires after 1 hour. Documented uses include user onboarding, workbook permissions, and workbook export. Export downloads can be CSV, XLSX, PDF, PNG, or JSON. Token requests are limited to 1 per second. Workbook export is limited to 400 requests per minute. Sigma also documents an organization MCP server. The URL is copied from Profile, Integrations. Transport is HTTP and auth is OAuth. The account needs the Use Sigma MCP with OAuth permission. The page describes search, explore, query, and calling Sigma agents. Queries run against the published version of a document and are tagged kind mcp. The help-center server at https://help.sigmacomputing.com/_mcp/server is a documentation index, not this organization server. https://help.sigmacomputing.com/llms.txt is a first-party documentation index. Zapier, Make, Power Automate, and n8n were not assessed. A published language SDK and a CLI were not established. Computer-use viability is unassessed. API scores 8. MCP scores 7. API is the best path because a bearer token calls the REST API directly, without an organization-specific MCP URL or a browser OAuth consent.

Best path today: api · Overall automatability: 8/10