mcp-server-sigma
Community MCP server that drives Sigma Computing workbooks, models and admin via API
- Pricing
- Open source
- Platforms
- CLI, self-hosted, API
- Runs
- Locally
- Version
- 2.3.2
- Listing updated
- today
Similar MCP servers
About mcp-server-sigma
mcp-server-sigma is an open-source MCP server for analytics and data. It runs locally on your machine and is started by your AI client.
The server wraps the Sigma API in 263 tools that span connections, workbooks, data models, members, teams, deployments, webhooks and multi-tenant operations. Its README is candid about a split in Sigma itself: data models can be built entirely from code, while workbook layouts are mostly designed in the Sigma UI. The recommended pattern is to build a layout once, save it as a template, then instantiate it and swap its warehouse sources through the API.
Two composite tools automate that pattern: one deploys a template into a customer folder, the other swaps the sources behind a workbook's elements. Partial failures come back with step-by-step detail.
Because the tools can change workbooks, users and teams, the README stresses safety. A read-only mode exposes only the 120 tools marked read-only, single deletes need an explicit confirm flag, and bulk destructive tools are refused unless an environment variable allows them. It is an independent project and is not affiliated with Sigma Computing.
Install
Run in a terminal
claude mcp add sigma --env SIGMA_CLIENT_ID='<SIGMA_CLIENT_ID>' --env SIGMA_CLIENT_SECRET='<SIGMA_CLIENT_SECRET>' --env SIGMA_API_BASE_URL='<SIGMA_API_BASE_URL>' -- uvx mcp-server-sigmaAdd to claude_desktop_config.json
{
"mcpServers": {
"sigma": {
"command": "uvx",
"args": [
"mcp-server-sigma"
],
"env": {
"SIGMA_CLIENT_ID": "<SIGMA_CLIENT_ID>",
"SIGMA_CLIENT_SECRET": "<SIGMA_CLIENT_SECRET>",
"SIGMA_API_BASE_URL": "<SIGMA_API_BASE_URL>"
}
}
}
}Add to ~/.cursor/mcp.json
{
"mcpServers": {
"sigma": {
"command": "uvx",
"args": [
"mcp-server-sigma"
],
"env": {
"SIGMA_CLIENT_ID": "<SIGMA_CLIENT_ID>",
"SIGMA_CLIENT_SECRET": "<SIGMA_CLIENT_SECRET>",
"SIGMA_API_BASE_URL": "<SIGMA_API_BASE_URL>"
}
}
}
}Add to .vscode/mcp.json
{
"servers": {
"sigma": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-server-sigma"
],
"env": {
"SIGMA_CLIENT_ID": "<SIGMA_CLIENT_ID>",
"SIGMA_CLIENT_SECRET": "<SIGMA_CLIENT_SECRET>",
"SIGMA_API_BASE_URL": "<SIGMA_API_BASE_URL>"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json
{
"mcpServers": {
"sigma": {
"command": "uvx",
"args": [
"mcp-server-sigma"
],
"env": {
"SIGMA_CLIENT_ID": "<SIGMA_CLIENT_ID>",
"SIGMA_CLIENT_SECRET": "<SIGMA_CLIENT_SECRET>",
"SIGMA_API_BASE_URL": "<SIGMA_API_BASE_URL>"
}
}
}
}Add to your client's MCP settings (most use this shape)
{
"mcpServers": {
"sigma": {
"command": "uvx",
"args": [
"mcp-server-sigma"
],
"env": {
"SIGMA_CLIENT_ID": "<SIGMA_CLIENT_ID>",
"SIGMA_CLIENT_SECRET": "<SIGMA_CLIENT_SECRET>",
"SIGMA_API_BASE_URL": "<SIGMA_API_BASE_URL>"
}
}
}
}Using several servers? Build one config file with the MCP config generator.
Configuration
SIGMA_CLIENT_IDYour Sigma API client IDRequiredSIGMA_CLIENT_SECRETYour Sigma API client secretRequiredSIGMA_API_BASE_URLRegion-specific Sigma API host URL (e.g. https://api.us-a.aws.sigmacomputing.com)Required
Tools this server provides (4)
Taken from the project documentation; the running server may differ.
- workbooks_deploy_template_to_folder
- Instantiates a saved template into a target customer folder.
- elements_swap_workbook_sources
- Swaps the warehouse sources behind workbook elements.
- admin_bulk_deactivate_members
- Bulk deactivation of members; refused unless bulk destructive mode is enabled.
- admin_bulk_remove_team_members
- Bulk removal of team members; refused unless bulk destructive mode is enabled.
What it does
- 263 Sigma API tools
- Covers connections, workbooks, data models, members, teams, deployments and webhooks.
- Template deployment recipe
- One call instantiates a saved template into a target customer folder.
- Source swapping
- Repoints the warehouse sources behind workbook elements through the API.
- Read-only profile
- Limits the server to the 120 tools annotated as read-only.
- Delete confirmation gates
- Single-delete tools change nothing until the caller passes confirm=true.
- Stdio and HTTP transports
- Runs over stdio, or Streamable HTTP with a bearer token for networked use.
Good for
- Deploy a dashboard template to each customer folder in a multi-tenant setup
- Swap warehouse sources on existing workbooks
- Audit members and teams in a Sigma organization
- Build or update data models from code via an AI assistant
- Run read-only inspections of a Sigma environment
Pricing
Open source
Apache-2.0 licensed per the README badge; a Sigma API account is separate
mcp-server-sigma FAQ
What credentials does it need?
A Sigma API client ID, a client secret and the region-specific API base URL for your organization.
How do I stop it making changes?
Set SIGMA_MCP_READONLY=1 or use the readonly profile, which exposes only read-only tools and refuses everything else.
Is it an official Sigma product?
No. The README says it is an independent community project not affiliated with or endorsed by Sigma Computing.
How is it installed?
With pip or uv from PyPI, or as a Docker image from GitHub Container Registry.
Is mcp-server-sigma free?
Yes. mcp-server-sigma is open source, so you can use and self-host it for free.
How do I add mcp-server-sigma to Claude Code?
Run this command in your terminal: claude mcp add sigma --env SIGMA_CLIENT_ID='<SIGMA_CLIENT_ID>' --env SIGMA_CLIENT_SECRET='<SIGMA_CLIENT_SECRET>' --env SIGMA_API_BASE_URL='<SIGMA_API_BASE_URL>' -- uvx mcp-server-sigma
What are the best alternatives to mcp-server-sigma?
The closest alternatives to mcp-server-sigma are Agent-Native Analytics, Google Ads + Meta Ads + SEO/GEO MCP, dashboard-icons, Tapetide - Indian Stock Market MCP and World Monitor.
Where this comes from
- Description: written from the project's README.
- Install steps: from the official MCP Registry entry.

