Sigma Computing MCP connector
The Sigma Computing connector brings Sigma members, teams, workspaces, access grants, and data connections into Claude, ChatGPT, Cursor, and the Elaichi Agent, so people can manage who sees what in Sigma Computing by asking in plain language.
-
How it connects. App credentials. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
How to connect
How to connect Sigma Computing to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Sigma Computing once
-
Open Connections, choose Add connection, and pick Sigma Computing.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste your Sigma Computing app credentials. Sigma Computing authenticates the app rather than a person. One person supplies the credentials once, and everyone else works through Share with.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
Sigma Computing
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Sigma Computing MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Sigma Computing MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Sigma Computing MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
Connect Sigma Computing to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
Use cases
What teams do with Sigma Computing through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
Analytics
Set up a new analyst on day one
Create the person as a Sigma Computing member, add them to the right team, and grant them access to the workspaces their group uses, all from one request.
-
IT
Audit who can open which workspace
Pull the list of Sigma Computing workspaces and their grants, then see which members and teams hold access before a security review.
-
Data platform
Check which data connections are live
List the connections Sigma Computing is using and confirm the warehouse sources each team relies on are still in place.
-
Operations
Stand up a workspace for a new project
Create a Sigma Computing workspace, then grant the project team and its sponsors access without waiting on an admin ticket.
-
People
Move someone between teams cleanly
When an analyst changes department, update their Sigma Computing team membership and adjust workspace grants so their access matches their new role.
-
Security
Remove a leaver's access the same day
Delete a departing member's workspace grants and remove them from Sigma Computing teams so nothing is left open after offboarding.
Try asking
- “Which Sigma Computing teams have no members right now?”
- “List workspaces added in Sigma Computing this month.”
- “Show members whose team changed in the last week.”
Compare
Elaichi vs Zapier MCP vs Composio for Sigma Computing
All three can connect Sigma Computing to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Sigma Computing tools | Allow or restrict single Sigma Computing tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Sigma Computing call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | $15 per user per month. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
AI tools
Sigma Computing tools for your AI agents
136 tools are ready to call through Elaichi's MCP endpoint the moment you connect Sigma Computing, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
See it in Elaichi
What connecting Sigma Computing gets you
6 screens from the product, each doing one job for your Sigma Computing account.
The agent
Ask about members and teams in plain language.
Three starter prompts return answers from live Sigma Computing members, teams and workspaces.
- members
- teams
- workspaces
- workbooks
Ask Elaichi to work across your apps.
Which Sigma Computing teams have no members right now?
List workspaces added in Sigma Computing this month.
Show members whose team changed in the last week.
Also runs in Claude, ChatGPT or Cursor
MCP clients
Claude, ChatGPT and Cursor reach Sigma Computing.
One org-wide MCP endpoint over OAuth, no SDK and no shared API key.
Copy the endpoint
Tool catalog
136 Sigma Computing tools are ready to call.
Members, teams, team members, workspaces and user attributes, with no custom code written.
- List all Sigma Computing members
- Get single Sigma Computing member by ID
- Create a Sigma Computing member
- Update a Sigma Computing member by ID
Toolboxes
Each team gets its own Sigma Computing toolbox.
Curate one toolbox for analytics, another for support, and scope each to its team.
- Analytics
- Data platform
- Revenue operations
- IT operations
Shared connections
Teammates query Sigma Computing without a credential.
The connections table shows who connected each account and how widely it is shared.
- Analytics core
- Data platform
- Revenue operations
- Finance EMEA
Audit log
Every Sigma Computing call is on the record.
When, who, what happened, type and resource, appended and never edited.
- When
- Who
- What happened
- Type
Launching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, a digest posts back.
Six steps fetch and group Sigma Computing members, draft a digest, then wait for approval.
Sigma Computing digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch members
Sigma Computing
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Sigma Computing
Queued
Collections and dashboards
Sigma Computing health arrives already counted.
Four metrics, 14 days of workbooks created and a team breakdown, refreshed on schedule.
Sigma Computing health
Refreshed 4 minutes ago · every 15 minutes · from the members collection
Members
1,284 ↓ 12%
Teams
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Members created
Last 14 days
By team
Share of activity
Analytics core 34%
Data platform 27%
Revenue operations 21%
Finance EMEA 18%
Related connectors
More from the catalog
FAQ
Frequently asked questions
How do I connect Sigma Computing to Claude?
Connect Sigma Computing in Elaichi first: choose the connector and enter the app credentials from your Sigma Computing admin settings. There is no OAuth application to register and no client ID or secret to generate in Elaichi. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in with your Elaichi account and Sigma Computing is available in Claude.
Does Sigma Computing work with ChatGPT and Cursor as well as Claude?
Yes. Once Sigma Computing is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Sigma Computing once and every client picks it up.
What can an AI agent actually do with my Sigma Computing data?
Through this connector an agent can look up Sigma Computing members and teams, create or update them, create and organize workspaces, grant or remove workspace access, and list the data connections your Sigma Computing organization uses. It works best with short, concrete asks such as "list who has access to the Finance workspace" rather than a long paragraph. Because Sigma Computing has many available actions, the agent searches for the right one based on what you ask.
Does connecting Sigma Computing give the AI access to every workspace?
No. Every request runs as the person who signed in, so the AI can only see the Sigma Computing members, teams, and workspaces that person's own Sigma Computing role already allows. Elaichi can narrow that further with restrictions, but it can never widen it beyond what Sigma Computing itself grants the person.
Can I stop an agent from deleting members or workspaces in Sigma Computing?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Sigma Computing members and workspaces while blocking deletion of members, teams, workspaces, or grants. A blocked action is never advertised to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.
What happens to a Sigma Computing connection when someone leaves?
Offboarding a person in Elaichi ends their access to Sigma Computing through every client at once. If they connected a shared Sigma Computing account, the connection keeps working for everyone else it was shared with. If you disconnect Sigma Computing in Elaichi, it disappears from Claude, ChatGPT, Cursor, and the Elaichi Agent in one step.
Does the Sigma Computing MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Sigma Computing is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Sigma Computing?
Yes. Both let Claude, ChatGPT or Cursor use Sigma Computing. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Sigma Computing call.
How is Elaichi different from Composio for Sigma Computing?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Sigma Computing: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Sigma Computing in front of your team
14 days on Gold, no credit card. Connect it once and pick what each team can call.
- Works with
-
and any other MCP client, or the Elaichi Agent.
- When the trial ends
- Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.