Sigma Computing MCP server
Sigma Computing in any MCP client, through Memtro: Sigma Computing does not publish this server. Memtro's Sigma Computing connector reads Sigma Computing through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
Sigma Computing BI: workbooks with their owners, versions and tags, a workbook's elements, files and folders (workbooks, data models, reports), teams, warehouse connections, scheduled exports and materialization jobs, and member lookup by email; when you ask, can email a workbook as PDF, Excel or CSV to named people or teams, run a materialization, copy or version-tag a workbook, delete a scheduled export, add or deactivate a member, and change a team's members.
Reads
sigma_list_workbooksSigma workbooks the credentials' owner can see: name, folder path, link, latest version, owner id, tags, description, created and updated.sigma_list_workbook_elementsThe elements (tables, charts, pivots, controls) in a Sigma workbook: id, name, type, visualization and column names.sigma_list_filesSigma's file tree: workspaces, folders, workbooks, data models, reports and more, with type, path, the owner's permission, badge and dates.sigma_list_teamsSigma teams: id, name, description, visibility and whether archived.sigma_find_memberLooks up a Sigma member by an exact email address the user already has, returning the member id, account type, kind and whether deactivated…sigma_list_connectionsSigma's warehouse connections: id, name, type (Snowflake, BigQuery, Databricks…), sample or archived, write access, OAuth or not…sigma_list_workbook_schedulesA Sigma workbook's scheduled exports: id, cron expression and timezone, title, attachment count, whether suspended or disabled…sigma_materialization_statusThe state of a Sigma materialization job (from sigma_run_materialization): status, started, ready, expires and any error.
Acts, when you ask
These change something in Sigma Computing. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
sigma_send_workbookExports a Sigma workbook now and emails it as PDF, Excel or CSV to the email addresses and teams given (recipients may be outside the company)…sigma_run_materializationStarts a materialization job for a Sigma workbook element now (its schedule's sheetId), which runs queries on the warehouse and spends its compute.sigma_copy_workbookCopies a Sigma workbook into a folder under a new name, owned by the credentials' owner.sigma_tag_workbookApplies an existing version tag (e.g. Production) to a Sigma workbook's published version, which changes what people and tenants who use that tag see.sigma_delete_workbook_schedulePermanently deletes a scheduled export from a Sigma workbook; its recipients stop receiving it.sigma_create_memberAdds a person to the Sigma organisation, which gives them access; send_invite true has Sigma email them an invitation.sigma_deactivate_memberDeactivates a Sigma member, removing their access; their documents stay.sigma_update_team_membersAdds and removes members of a Sigma team by member id, which changes what they can see and are sent.
Connect it
First connect Sigma Computing on Dashboard → Connections, then add Memtro to your client once. The Sigma Computing tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Sigma Computing connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Which workbooks did finance update this month?
- › Which charts and tables are in the Revenue overview workbook?
- › What scheduled exports does the Board pack workbook have?
- › Which warehouse connections have not been active lately?
- › Email the Weekly sales workbook as a PDF to the leadership team.
Questions
- Is this an official Sigma Computing MCP server?
- No. It is Memtro's MCP server with Memtro's Sigma Computing connector behind it: the connector reads Sigma Computing through its API with the credentials you connect on Dashboard → Connections, and Sigma Computing publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in Sigma Computing?
- Only when you ask, and only what it has been granted: email a workbook as PDF, Excel or CSV to named people or teams; run a materialization for a workbook element (uses warehouse compute); copy a workbook into a folder; add a version tag to a workbook; delete a scheduled export (permanent); add a member, inviting them by email if you ask; deactivate a member; add or remove members of a team. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.