Gumloop MCP connector
Connecting Gumloop to Elaichi lets Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent look up your Gumloop flows, agents, automation runs, files, and audit logs through one governed endpoint, with every action tied to the person who asked for it.
- Connects with an API key
- Free 14-day trial
- No credit card
List the Gumloop agents created this month.
Working in Gumloop with Elaichi
-
List all Gumloop agents
-
Get single Gumloop agent by ID
-
Get single Gumloop artifact by ID
How to connect Gumloop to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Gumloop 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.
Gumloop MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Gumloop 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. The plugin directory lives at chatgpt.com/plugins.
Gumloop 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.
Gumloop MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Gumloop 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.
What teams do with Gumloop through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Gumloop is logged.
-
Operations
Check overnight automation runs before standup
Ask which Gumloop automations ran last night, which finished cleanly, and which need a second look, then open the details of any single run without leaving the chat.
-
Marketing
Find the flow that already does this
Before anyone rebuilds a lead enrichment or content flow, list the Gumloop flows and workbooks the team already has and see what each one is for.
-
Revenue operations
Load a batch of files into Gumloop
Drop a stack of call transcripts or spreadsheets into Gumloop in one go so the next flow has everything it needs, then confirm each file landed.
-
Data
Request an export and collect it later
Kick off a Gumloop data export, then come back and fetch the finished export by its ID when the run has produced it.
-
Product
Adjust a Gumloop agent's instructions after review
List the Gumloop agents your team runs, read how one is set up, and update its instructions or model choice from a plain description of the change.
-
IT and admin
Review who changed what in Gumloop
Pull the Gumloop audit log for a date range, see which member did what, and move a person to a different permission group when a role changes.
Try asking
- “List the Gumloop agents created this month.”
- “Which Gumloop flows ran the most last week?”
- “Show artifacts produced by our onboarding Gumloop agent.”
What connecting Gumloop gets you
6 screens from Elaichi, each doing one job for your Gumloop account.
Ask Elaichi to work across your apps.
List the Gumloop agents created this month.
Which Gumloop flows ran the most last week?
Show artifacts produced by our onboarding Gumloop agent.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Gumloop agents, get real answers.
Plain language questions read live Gumloop flows, agents and artifacts as they stand now.
Copy the endpoint
AI apps
Claude, ChatGPT, Cursor and Microsoft Copilot reach Gumloop here.
One org MCP endpoint over OAuth, no SDK work and no shared API key.
Tool catalog
38 Gumloop tools arrive ready to call.
Agents, flows, workbooks, files and artifacts are covered with no custom code written.
Toolboxes
Every team gets its own Gumloop toolbox.
Curate one toolbox per team so Gumloop tools match the work that team does.
Shared connections
Teammates run Gumloop flows without a credential.
Each Gumloop connection shows who connected it and which teams and members use it.
Audit log
Every Gumloop call is written down.
When, who, what happened, type and resource for each agent, flow and file touched.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Gumloop digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch agents
Gumloop
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 Jake Morgan
Approve Deny -
Post the digest
Gumloop
Queued
Automations
A schedule fires and Gumloop work finishes.
Six steps fetch Gumloop flow runs, group them, draft a digest, await approval, post back.
Gumloop health
Refreshed 4 minutes ago · every 15 minutes · from the agents collection
Agents
1,284 ↓ 12%
Flows
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Agents created
Last 14 days
By team
Share of activity
Operations 34%
Marketing 27%
Sales EMEA 21%
Support 18%
Collections and dashboards
Gumloop health is counted, not requested.
Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Gumloop
All three can connect Gumloop 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 Gumloop tools | Allow or restrict single Gumloop 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 Gumloop 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 | Free for one person; $15 per user per month on Gold. | 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.
Gumloop tools for your AI agents
38 tools are ready to call through Elaichi's MCP endpoint the moment you connect Gumloop, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Gumloop to Claude?
First connect Gumloop in Elaichi by pasting a Gumloop API key when prompted, which takes a minute. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. There is no OAuth application to register in Gumloop and no client ID or secret to generate, so the whole setup is two steps.
Does Gumloop work with ChatGPT and Cursor as well as Claude?
Yes. Once Gumloop is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent. You connect Gumloop once and every client picks it up.
What can an AI agent actually do with my Gumloop data?
It can list your Gumloop flows, workbooks, agents, and models, check recent automation runs and open the details of one, fetch the files and artifacts a run produced, request a data export, read the audit log, and create or update Gumloop agents. Because Gumloop exposes a lot of actions, the agent searches for the right one as you ask, so short concrete requests like "show failed runs from yesterday" work better than long paragraphs.
Does connecting Gumloop give the AI everything in my workspace?
No. Access follows the person who signed in to Elaichi, so an AI client sees only the Gumloop flows, runs, files, and audit entries that person's Gumloop access already allows. Elaichi can narrow that further per team or per action, and it never widens what someone could already do in Gumloop.
Can I stop an agent from changing things in Gumloop?
Yes. Restrictions in Elaichi work per action, so you can allow reading Gumloop runs, flows, and files while restricting actions that create or update agents, upload files, or change permission groups. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.
What happens to a Gumloop connection when someone leaves?
Offboarding that person in Elaichi ends their access to Gumloop through every AI client at once. If they had shared a Gumloop connection with a team, it keeps working for everyone else. If you want the connection gone entirely, disconnecting Gumloop once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot, and every other client at the same time.
Does the Gumloop MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Gumloop 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, Microsoft Copilot, 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 Gumloop?
Yes. Both let Claude, ChatGPT or Cursor use Gumloop. 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 Gumloop call.
How is Elaichi different from Composio for Gumloop?
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 Gumloop: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Gumloop in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot