Skip to content

IPAAS

Gumloop MCP connector

Connecting Gumloop to Elaichi lets Claude, ChatGPT, Cursor, 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.

  • How it connects. Connects with an API key. 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 Gumloop to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Gumloop once

  1. Open Connections, choose Add connection, and pick Gumloop.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Gumloop API key. One person generates a token in Gumloop and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

gumloop
Gumloop
1Password
360learning
7shifts
Acquire
Ada
2

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.

Connect Gumloop to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Gumloop to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Gumloop to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 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 Gumloop to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 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 Gumloop through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • 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.”

See all 38 Gumloop tools below

AI tools

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.

See it in Elaichi

What connecting Gumloop gets you

6 screens from the product, each doing one job for your Gumloop account.

The agent

Ask about Gumloop agents, get real answers.

Plain language questions read live Gumloop flows, agents and artifacts as they stand now.

  • agents
  • flows
  • artifacts
  • files

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 or Cursor

MCP clients

Claude, ChatGPT and Cursor reach Gumloop here.

One org MCP endpoint over OAuth, no SDK work and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

38 Gumloop tools arrive ready to call.

Agents, flows, workbooks, files and artifacts are covered with no custom code written.

  • Create a Gumloop agent
  • List all Gumloop agents
  • Get single Gumloop agent by ID
  • Update a Gumloop agent by ID
ElaichiTools
Tool Action Description
Create a Gumloop agent Create Create a new agent in Gumloop. The authenticated caller must have permission to create agents on the target team. Returns: id, name, team_id.
List all Gumloop agents List List Gumloop agents the caller has access to, optionally filtered by team, name, tool, or trigger. Returns: id, name, team_id.
Get single Gumloop agent by ID Get Retrieve a single Gumloop agent by id. Returns: id, name, team_id. Required: id.
Update a Gumloop agent by ID Update Update an existing Gumloop agent by id; only fields included in the request body are changed — omitted fields remain untouched. Returns: id, name, team_id. Required: id.
Get single Gumloop artifact by ID Get Download a gumloop artifact by id. Returns a signed download URL for the artifact along with its filename, media_type, and size; follow download_url to fetch the file bytes. Required: id.

Toolboxes

Every team gets its own Gumloop toolbox.

Curate one toolbox per team so Gumloop tools match the work that team does.

  • Operations
  • Engineering
  • Marketing
  • Sales
ElaichiToolboxes
Name Source template Tools Created

Operations toolbox

Gumloop · flows and automations

Gumloop starter 18 Mar 4, 2026

Engineering toolbox

Gumloop · agents and chat completions

9 Mar 2, 2026

Marketing toolbox

Gumloop · content flows and artifacts

24 Feb 27, 2026

Sales toolbox

Gumloop · outreach flows and workbooks

Gumloop starter 6 Feb 19, 2026

Support toolbox

Gumloop · ticket triage flows

31 Jan 30, 2026

Finance toolbox

Gumloop · reporting workbooks and files

12 Jan 22, 2026

Shared connections

Teammates run Gumloop flows without a credential.

Each Gumloop connection shows who connected it and which teams and members use it.

  • Operations
  • Marketing
  • Sales EMEA
  • Support
ElaichiConnections
Connection Scope Status Access
GU

Gumloop (Operations)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
GU

Gumloop (Marketing)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
GU

Gumloop (Sales EMEA)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
GU

Gumloop (Support)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
GU

Gumloop (Engineering)

Connected by Clara Nowak

Personal • Active Not shared
GU

Gumloop (Finance)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Every Gumloop call is written down.

When, who, what happened, type and resource for each agent, flow and file touched.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Gumloop Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Gumloop Agents Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Gumloop Agents List Toolbox

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 and Gumloop work finishes.

Six steps fetch Gumloop flow runs, group them, draft a digest, await approval, post back.

Gumloop digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch agents

    Gumloop

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Gumloop

    Queued

Collections and dashboards

Gumloop health is counted, not requested.

Four metrics, 14 days of records created and a team breakdown, refreshed on schedule.

Gumloop health

Refreshed 4 minutes ago · every 15 minutes · from the agents collection

Live

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%

FAQ

Frequently asked questions

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, 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 my team share one Gumloop connection?

Yes. One person connects Gumloop with an API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who checked a run or updated an agent, not a shared account.

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 blocking actions that create or update agents, upload files, or change permission groups. A blocked action is never advertised to Claude, ChatGPT, Cursor, or any other client, so no prompt can reach it.

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, and every other client at the same time.

Put Gumloop in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.