Gumloop MCP Server & CLI
A free, open source Gumloop MCP server and CLI that lets Claude Code, Codex, Cursor and other AI agents run your flows, work with your agents and search your Company Brain.
0.0(0 ratings)- 1
Add it with a single command in a terminal.
Put your own API key and user ID in place of the examples.
claude mcp add gumloop \
-e GUMLOOP_API_KEY=YOUR_API_KEY \
-e GUMLOOP_USER_ID=YOUR_USER_ID \
-- npx -y @thenavidm/gumloop-mcp-cli@latest - 2
In Claude Code, type /mcp. Gumloop should show as connected.
/mcp
- 1
Add it with a single command in a terminal.
Put your own API key and user ID in place of the examples.
claude mcp add gumloop -e GUMLOOP_API_KEY="YOUR_API_KEY" -e GUMLOOP_USER_ID="YOUR_USER_ID" -- npx -y @thenavidm/gumloop-mcp-cli@latest - 2
In Claude Code, type /mcp. Gumloop should show as connected.
/mcp
- 1
Add it with a single command in a terminal.
Put your own API key and user ID in place of the examples.
claude mcp add gumloop \
-e GUMLOOP_API_KEY=YOUR_API_KEY \
-e GUMLOOP_USER_ID=YOUR_USER_ID \
-- npx -y @thenavidm/gumloop-mcp-cli@latest - 2
In Claude Code, type /mcp. Gumloop should show as connected.
/mcp
- 1Download the extension
Download the Claude Desktop extension.
- 2
Double-click it, and Claude Desktop installs it.
- 1
Add it with a single command in a terminal.
Put your own API key and user ID in place of the examples.
codex mcp add gumloop \
--env GUMLOOP_API_KEY=YOUR_API_KEY \
--env GUMLOOP_USER_ID=YOUR_USER_ID \
-- npx -y @thenavidm/gumloop-mcp-cli@latest - 2
Check that Codex lists it.
codex mcp list
- 1
Add it with a single command in a terminal.
Put your own API key and user ID in place of the examples.
codex mcp add gumloop --env GUMLOOP_API_KEY="YOUR_API_KEY" --env GUMLOOP_USER_ID="YOUR_USER_ID" -- npx -y @thenavidm/gumloop-mcp-cli@latest - 2
Check that Codex lists it.
codex mcp list
- 1
Add it with a single command in a terminal.
Put your own API key and user ID in place of the examples.
codex mcp add gumloop \
--env GUMLOOP_API_KEY=YOUR_API_KEY \
--env GUMLOOP_USER_ID=YOUR_USER_ID \
-- npx -y @thenavidm/gumloop-mcp-cli@latest - 2
Check that Codex lists it.
codex mcp list
- 1
Open Cursor's settings, go to the MCP tab, and click Add new global MCP server.
- 2
Add the server.
Put your own API key and user ID in place of the examples.
{
"mcpServers": {
"gumloop": {
"command": "npx",
"args": ["-y", "@thenavidm/gumloop-mcp-cli@latest"],
"env": {
"GUMLOOP_API_KEY": "YOUR_API_KEY",
"GUMLOOP_USER_ID": "YOUR_USER_ID"
}
}
}
} - 3
Open the MCP tab again. It should show 92 tools.
- 1
Open the Command Palette and run MCP: Open User Configuration.
- 2
Add the server to that mcp.json.
If the file already has servers, add only this one inside servers. Put your own API key and user ID in place of the examples.
{
"servers": {
"gumloop": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@thenavidm/gumloop-mcp-cli@latest"],
"env": {
"GUMLOOP_API_KEY": "YOUR_API_KEY",
"GUMLOOP_USER_ID": "YOUR_USER_ID"
}
}
}
}
- 1
Add it with a single command in a terminal.
Put your own API key and user ID in place of the examples.
copilot mcp add gumloop \
--env GUMLOOP_API_KEY=YOUR_API_KEY \
--env GUMLOOP_USER_ID=YOUR_USER_ID \
-- npx -y @thenavidm/gumloop-mcp-cli@latest - 2
Check that Copilot CLI has it.
copilot mcp get gumloop
- 1
Add it with a single command in a terminal.
Put your own API key and user ID in place of the examples.
copilot mcp add gumloop --env GUMLOOP_API_KEY="YOUR_API_KEY" --env GUMLOOP_USER_ID="YOUR_USER_ID" -- npx -y @thenavidm/gumloop-mcp-cli@latest - 2
Check that Copilot CLI has it.
copilot mcp get gumloop
- 1
Add it with a single command in a terminal.
Put your own API key and user ID in place of the examples.
copilot mcp add gumloop \
--env GUMLOOP_API_KEY=YOUR_API_KEY \
--env GUMLOOP_USER_ID=YOUR_USER_ID \
-- npx -y @thenavidm/gumloop-mcp-cli@latest - 2
Check that Copilot CLI has it.
copilot mcp get gumloop
- 1
Open your Gemini CLI settings.
~/.gemini/settings.json - 2
Add the server to settings.json.
If the file already has servers, add only this one inside mcpServers. Put your own API key and user ID in place of the examples.
{
"mcpServers": {
"gumloop": {
"command": "npx",
"args": ["-y", "@thenavidm/gumloop-mcp-cli@latest"],
"env": {
"GUMLOOP_API_KEY": "YOUR_API_KEY",
"GUMLOOP_USER_ID": "YOUR_USER_ID"
}
}
}
} - 3
Restart Gemini CLI and type /mcp to check it.
/mcp
- 1
Open your Gemini CLI settings.
%USERPROFILE%\.gemini\settings.json - 2
Add the server to settings.json.
If the file already has servers, add only this one inside mcpServers. Put your own API key and user ID in place of the examples.
{
"mcpServers": {
"gumloop": {
"command": "npx",
"args": ["-y", "@thenavidm/gumloop-mcp-cli@latest"],
"env": {
"GUMLOOP_API_KEY": "YOUR_API_KEY",
"GUMLOOP_USER_ID": "YOUR_USER_ID"
}
}
}
} - 3
Restart Gemini CLI and type /mcp to check it.
/mcp
- 1
Open your Gemini CLI settings.
~/.gemini/settings.json - 2
Add the server to settings.json.
If the file already has servers, add only this one inside mcpServers. Put your own API key and user ID in place of the examples.
{
"mcpServers": {
"gumloop": {
"command": "npx",
"args": ["-y", "@thenavidm/gumloop-mcp-cli@latest"],
"env": {
"GUMLOOP_API_KEY": "YOUR_API_KEY",
"GUMLOOP_USER_ID": "YOUR_USER_ID"
}
}
}
} - 3
Restart Gemini CLI and type /mcp to check it.
/mcp
- 1
Open your OpenCode config.
~/.config/opencode/opencode.json - 2
Add the server under mcp.
If the file already has servers, add only this one inside mcp. Put your own API key and user ID in place of the examples.
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gumloop": {
"type": "local",
"command": ["npx", "-y", "@thenavidm/gumloop-mcp-cli@latest"],
"enabled": true,
"environment": {
"GUMLOOP_API_KEY": "YOUR_API_KEY",
"GUMLOOP_USER_ID": "YOUR_USER_ID"
}
}
}
} - 3
Restart OpenCode.
- 1
Open your OpenCode config.
%USERPROFILE%\.config\opencode\opencode.json - 2
Add the server under mcp.
If the file already has servers, add only this one inside mcp. Put your own API key and user ID in place of the examples.
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gumloop": {
"type": "local",
"command": ["npx", "-y", "@thenavidm/gumloop-mcp-cli@latest"],
"enabled": true,
"environment": {
"GUMLOOP_API_KEY": "YOUR_API_KEY",
"GUMLOOP_USER_ID": "YOUR_USER_ID"
}
}
}
} - 3
Restart OpenCode.
- 1
Open your OpenCode config.
~/.config/opencode/opencode.json - 2
Add the server under mcp.
If the file already has servers, add only this one inside mcp. Put your own API key and user ID in place of the examples.
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"gumloop": {
"type": "local",
"command": ["npx", "-y", "@thenavidm/gumloop-mcp-cli@latest"],
"enabled": true,
"environment": {
"GUMLOOP_API_KEY": "YOUR_API_KEY",
"GUMLOOP_USER_ID": "YOUR_USER_ID"
}
}
}
} - 3
Restart OpenCode.
- 1
Add it with a single command in a terminal.
Put your own API key and user ID in place of the examples.
openclaw mcp add gumloop \
--command npx \
--arg -y \
--arg @thenavidm/gumloop-mcp-cli@latest \
--env GUMLOOP_API_KEY=YOUR_API_KEY \
--env GUMLOOP_USER_ID=YOUR_USER_ID - 2
Check that it starts and lists its tools.
openclaw mcp doctor gumloop --probe
- 1
Add it with a single command in a terminal.
Put your own API key and user ID in place of the examples.
openclaw mcp add gumloop --command npx --arg -y --arg @thenavidm/gumloop-mcp-cli@latest --env GUMLOOP_API_KEY="YOUR_API_KEY" --env GUMLOOP_USER_ID="YOUR_USER_ID" - 2
Check that it starts and lists its tools.
openclaw mcp doctor gumloop --probe
- 1
Add it with a single command in a terminal.
Put your own API key and user ID in place of the examples.
openclaw mcp add gumloop \
--command npx \
--arg -y \
--arg @thenavidm/gumloop-mcp-cli@latest \
--env GUMLOOP_API_KEY=YOUR_API_KEY \
--env GUMLOOP_USER_ID=YOUR_USER_ID - 2
Check that it starts and lists its tools.
openclaw mcp doctor gumloop --probe
- 1
In the agent panel, click the … menu, then MCP Servers, Manage MCP Servers and View raw config.
- 2
Add the server to mcp_config.json.
If the file already has servers, add only this one inside mcpServers. Put your own API key and user ID in place of the examples.
{
"mcpServers": {
"gumloop": {
"command": "npx",
"args": ["-y", "@thenavidm/gumloop-mcp-cli@latest"],
"env": {
"GUMLOOP_API_KEY": "YOUR_API_KEY",
"GUMLOOP_USER_ID": "YOUR_USER_ID"
}
}
}
}
- 1
Open your Hermes config.
~/.hermes/config.yaml - 2
Add the server under mcp_servers.
If the file already has mcp_servers, add only this one under it. Put your own API key and user ID in place of the examples.
mcp_servers:
gumloop:
command: "npx"
args: ["-y", "@thenavidm/gumloop-mcp-cli@latest"]
env:
GUMLOOP_API_KEY: "YOUR_API_KEY"
GUMLOOP_USER_ID: "YOUR_USER_ID"
- 1
Open your Hermes config.
%USERPROFILE%\.hermes\config.yaml - 2
Add the server under mcp_servers.
If the file already has mcp_servers, add only this one under it. Put your own API key and user ID in place of the examples.
mcp_servers:
gumloop:
command: "npx"
args: ["-y", "@thenavidm/gumloop-mcp-cli@latest"]
env:
GUMLOOP_API_KEY: "YOUR_API_KEY"
GUMLOOP_USER_ID: "YOUR_USER_ID"
- 1
Open your Hermes config.
~/.hermes/config.yaml - 2
Add the server under mcp_servers.
If the file already has mcp_servers, add only this one under it. Put your own API key and user ID in place of the examples.
mcp_servers:
gumloop:
command: "npx"
args: ["-y", "@thenavidm/gumloop-mcp-cli@latest"]
env:
GUMLOOP_API_KEY: "YOUR_API_KEY"
GUMLOOP_USER_ID: "YOUR_USER_ID"
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Give Claude Code the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells Claude Code what each command does and which ones ask first.
mkdir -p ~/.claude/skills/gumloop
cp "$(npm root -g)/@thenavidm/gumloop-mcp-cli/SKILL.md" ~/.claude/skills/gumloop/ - 3
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.zshrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.zshrc - 4
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 5
Ask Claude Code to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Claude Code finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Give Claude Code the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells Claude Code what each command does and which ones ask first.
New-Item -ItemType Directory -Force "$HOME\.claude\skills\gumloop" | Out-Null
Copy-Item "$(npm root -g)\@thenavidm\gumloop-mcp-cli\SKILL.md" "$HOME\.claude\skills\gumloop\" - 3
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
setx GUMLOOP_API_KEY "YOUR_API_KEY"
setx GUMLOOP_USER_ID "YOUR_USER_ID" - 4
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 5
Ask Claude Code to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Claude Code finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Give Claude Code the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells Claude Code what each command does and which ones ask first.
mkdir -p ~/.claude/skills/gumloop
cp "$(npm root -g)/@thenavidm/gumloop-mcp-cli/SKILL.md" ~/.claude/skills/gumloop/ - 3
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.bashrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.bashrc - 4
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 5
Ask Claude Code to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Claude Code finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Give Codex the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells Codex what each command does and which ones ask first.
mkdir -p ~/.agents/skills/gumloop
cp "$(npm root -g)/@thenavidm/gumloop-mcp-cli/SKILL.md" ~/.agents/skills/gumloop/ - 3
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.zshrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.zshrc - 4
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 5
Ask Codex to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Codex finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Give Codex the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells Codex what each command does and which ones ask first.
New-Item -ItemType Directory -Force "$HOME\.agents\skills\gumloop" | Out-Null
Copy-Item "$(npm root -g)\@thenavidm\gumloop-mcp-cli\SKILL.md" "$HOME\.agents\skills\gumloop\" - 3
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
setx GUMLOOP_API_KEY "YOUR_API_KEY"
setx GUMLOOP_USER_ID "YOUR_USER_ID" - 4
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 5
Ask Codex to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Codex finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Give Codex the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells Codex what each command does and which ones ask first.
mkdir -p ~/.agents/skills/gumloop
cp "$(npm root -g)/@thenavidm/gumloop-mcp-cli/SKILL.md" ~/.agents/skills/gumloop/ - 3
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.bashrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.bashrc - 4
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 5
Ask Codex to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Codex finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.zshrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.zshrc - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
Ask Cursor to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Cursor finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
setx GUMLOOP_API_KEY "YOUR_API_KEY"
setx GUMLOOP_USER_ID "YOUR_USER_ID" - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
Ask Cursor to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Cursor finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.bashrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.bashrc - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
Ask Cursor to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Cursor finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.zshrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.zshrc - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
Ask VS Code to use gumloop-cli.
Running gumloop-cli on its own lists every command, so VS Code finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
setx GUMLOOP_API_KEY "YOUR_API_KEY"
setx GUMLOOP_USER_ID "YOUR_USER_ID" - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
Ask VS Code to use gumloop-cli.
Running gumloop-cli on its own lists every command, so VS Code finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.bashrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.bashrc - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
Ask VS Code to use gumloop-cli.
Running gumloop-cli on its own lists every command, so VS Code finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Give Copilot CLI the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells Copilot CLI what each command does and which ones ask first.
mkdir -p ~/.copilot/skills/gumloop
cp "$(npm root -g)/@thenavidm/gumloop-mcp-cli/SKILL.md" ~/.copilot/skills/gumloop/ - 3
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.zshrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.zshrc - 4
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 5
Ask Copilot CLI to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Copilot CLI finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Give Copilot CLI the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells Copilot CLI what each command does and which ones ask first.
New-Item -ItemType Directory -Force "$HOME\.copilot\skills\gumloop" | Out-Null
Copy-Item "$(npm root -g)\@thenavidm\gumloop-mcp-cli\SKILL.md" "$HOME\.copilot\skills\gumloop\" - 3
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
setx GUMLOOP_API_KEY "YOUR_API_KEY"
setx GUMLOOP_USER_ID "YOUR_USER_ID" - 4
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 5
Ask Copilot CLI to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Copilot CLI finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Give Copilot CLI the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells Copilot CLI what each command does and which ones ask first.
mkdir -p ~/.copilot/skills/gumloop
cp "$(npm root -g)/@thenavidm/gumloop-mcp-cli/SKILL.md" ~/.copilot/skills/gumloop/ - 3
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.bashrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.bashrc - 4
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 5
Ask Copilot CLI to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Copilot CLI finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.zshrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.zshrc - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
Ask Gemini CLI to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Gemini CLI finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
setx GUMLOOP_API_KEY "YOUR_API_KEY"
setx GUMLOOP_USER_ID "YOUR_USER_ID" - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
Ask Gemini CLI to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Gemini CLI finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.bashrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.bashrc - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
Ask Gemini CLI to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Gemini CLI finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Give OpenCode the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells OpenCode what each command does and which ones ask first.
mkdir -p ~/.config/opencode/skills/gumloop
cp "$(npm root -g)/@thenavidm/gumloop-mcp-cli/SKILL.md" ~/.config/opencode/skills/gumloop/ - 3
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.zshrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.zshrc - 4
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 5
Ask OpenCode to use gumloop-cli.
Running gumloop-cli on its own lists every command, so OpenCode finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Give OpenCode the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells OpenCode what each command does and which ones ask first.
New-Item -ItemType Directory -Force "$HOME\.config\opencode\skills\gumloop" | Out-Null
Copy-Item "$(npm root -g)\@thenavidm\gumloop-mcp-cli\SKILL.md" "$HOME\.config\opencode\skills\gumloop\" - 3
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
setx GUMLOOP_API_KEY "YOUR_API_KEY"
setx GUMLOOP_USER_ID "YOUR_USER_ID" - 4
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 5
Ask OpenCode to use gumloop-cli.
Running gumloop-cli on its own lists every command, so OpenCode finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Give OpenCode the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells OpenCode what each command does and which ones ask first.
mkdir -p ~/.config/opencode/skills/gumloop
cp "$(npm root -g)/@thenavidm/gumloop-mcp-cli/SKILL.md" ~/.config/opencode/skills/gumloop/ - 3
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.bashrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.bashrc - 4
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 5
Ask OpenCode to use gumloop-cli.
Running gumloop-cli on its own lists every command, so OpenCode finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Give OpenClaw the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells OpenClaw what each command does and which ones ask first.
mkdir -p ~/.openclaw/skills/gumloop
cp "$(npm root -g)/@thenavidm/gumloop-mcp-cli/SKILL.md" ~/.openclaw/skills/gumloop/ - 3
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.zshrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.zshrc - 4
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 5
Ask OpenClaw to use gumloop-cli.
Running gumloop-cli on its own lists every command, so OpenClaw finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Give OpenClaw the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells OpenClaw what each command does and which ones ask first.
New-Item -ItemType Directory -Force "$HOME\.openclaw\skills\gumloop" | Out-Null
Copy-Item "$(npm root -g)\@thenavidm\gumloop-mcp-cli\SKILL.md" "$HOME\.openclaw\skills\gumloop\" - 3
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
setx GUMLOOP_API_KEY "YOUR_API_KEY"
setx GUMLOOP_USER_ID "YOUR_USER_ID" - 4
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 5
Ask OpenClaw to use gumloop-cli.
Running gumloop-cli on its own lists every command, so OpenClaw finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Give OpenClaw the skill, so it knows every command.
The skill is the SKILL.md in the package. It tells OpenClaw what each command does and which ones ask first.
mkdir -p ~/.openclaw/skills/gumloop
cp "$(npm root -g)/@thenavidm/gumloop-mcp-cli/SKILL.md" ~/.openclaw/skills/gumloop/ - 3
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.bashrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.bashrc - 4
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 5
Ask OpenClaw to use gumloop-cli.
Running gumloop-cli on its own lists every command, so OpenClaw finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.zshrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.zshrc - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
Ask Antigravity to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Antigravity finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
setx GUMLOOP_API_KEY "YOUR_API_KEY"
setx GUMLOOP_USER_ID "YOUR_USER_ID" - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
Ask Antigravity to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Antigravity finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.bashrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.bashrc - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
Ask Antigravity to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Antigravity finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.zshrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.zshrc - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
Ask Hermes to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Hermes finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
setx GUMLOOP_API_KEY "YOUR_API_KEY"
setx GUMLOOP_USER_ID "YOUR_USER_ID" - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
Ask Hermes to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Hermes finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.bashrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.bashrc - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
Ask Hermes to use gumloop-cli.
Running gumloop-cli on its own lists every command, so Hermes finds the one it needs.
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.zshrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.zshrc - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
List every command, then try one.
gumloop-cli
gumloop-cli list-agents
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
setx GUMLOOP_API_KEY "YOUR_API_KEY"
setx GUMLOOP_USER_ID "YOUR_USER_ID" - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
List every command, then try one.
gumloop-cli
gumloop-cli list-agents
- 1
Install the CLI. It needs Node 22 or newer.
npm install -g @thenavidm/gumloop-mcp-cli@latest - 2
Save your Gumloop details, so every new session has them.
Put your own API key and user ID in place of the examples.
echo 'export GUMLOOP_API_KEY=YOUR_API_KEY' >> ~/.bashrc
echo 'export GUMLOOP_USER_ID=YOUR_USER_ID' >> ~/.bashrc - 3
Check your setup.
It names anything that's wrong and the fix.
gumloop-cli doctor - 4
List every command, then try one.
gumloop-cli
gumloop-cli list-agents
Needs Node 22 or newer and a Gumloop API key, on the Pro plan or above. Get it in two minutes.
It's free and open source. If it saves you time, star it on GitHub, so more people find it.
This free Gumloop MCP server and CLI gives your AI real access to your Gumloop account: flows, agents, sessions, your Company Brain, skills and connected MCP servers. It runs your saved flows, talks to your agents and answers their approvals, searches your Company Brain, manages skills and evaluations, and handles team admin.
It's one install with two ways in. Claude, Codex, Cursor or any other MCP app calls its 92 tools for you, and the same tools work as a CLI that agents like Claude Code, Codex and OpenCode run, or that you type yourself.
In this guide, I'll show you:
- What the Gumloop MCP server & CLI is, and what you can ask it
- How to install it and check that it works
- When to use the MCP server, and when the CLI
- Every tool, and how to keep your account safe
Every tool on this page comes from the server itself, and every cost was measured in Claude Code.
Key takeaways
What is the Gumloop MCP server & CLI?
The Gumloop MCP server & CLI is a free, open source program that lets AI agents run flows and agents in your Gumloop account for you, in two ways. The MCP server is what an AI app like Claude, Codex or Cursor connects to, through MCP (Model Context Protocol), the open standard AI apps use to call outside tools.
You ask in plain language. Your AI picks the right tool, and the server makes the call to Gumloop's own API.
The CLI is the same program as commands. gumloop-cli list-agents runs the same code your AI runs when you ask which agents you have, whether an agent like Claude Code runs it or you do.
In an AI OS, the layer that connects your AI to your context, your data and your tools, a server like this is how your AI reaches Gumloop. I explain how the parts fit together in how to build an AI operating system, and here's how I use AI myself.
What can you ask it?
Once it's set up, you ask the way you'd ask an assistant. These are real prompts it handles:
Try askingWhich flows do I have, and what inputs does my lead-scraper flow need?
Run my weekly report flow for last week.
Ask my research agent to find five competitors, and show me what it needs approved.
Search our Company Brain for the refund policy.
How did my support agent do this month, by grade?
Which MCP servers does my sales agent use?
The third one shows why this is useful. Your AI starts the agent's session and comes back with exactly what the agent wants to do, so you approve each step yourself.
It works well next to my Google Workspace MCP server and Kit MCP server, so your AI can work in Google Sheets and draft emails to your list in the same chat. Every server I've made is on my MCP servers page.
For your prompts and agents, my free AI agent readiness checker and skill generator help too.
How to install the Gumloop MCP server
Pick your app in the box at the top of this page. Each one is a single command or a pasted block, and they all run through npx, so there's nothing to install first.
Windsurf, Zed and Cline take the same server, though they don't have a tab in the box yet. Follow the box's Cursor tab, and put its block here instead:
| App | Where the block goes |
|---|---|
| Windsurf | In the Cascade panel, open the Actions menu (…) and choose Open MCP config file, then paste the block. |
| Cline | Click the MCP Servers icon in the Cline panel, open the Configure tab, click Configure MCP Servers, and paste the block. |
| Zed | Go to Settings, then AI, then MCP Servers, and choose Add Server, then Add Local Server. Enter the block's command, arguments and variables, and Zed saves them under context_servers. |
Watch out: Gumloop has personal keys and team keys. A personal key acts as you, and a team key can act as any team member, so pick the one your work needs.
Set up your Gumloop account
It takes two minutes.
GUMLOOP_API_KEY in the command for your app, in place of the example.GUMLOOP_USER_ID, since flows need it.For team flows, also set GUMLOOP_TEAM_ID to your team's ID. Gumloop's older flow tools call it the project ID.
To keep the key out of your app's config, save it alone in a file only you can read, and point GUMLOOP_TOKEN_FILE at that file's full path instead.
Check that it works
Run the doctor with --network. It checks your settings, then reads the agents you can use, to prove the key works. It never starts a run.
npx -y @thenavidm/gumloop-mcp-cli doctor --networkWhen every line has a check mark, restart your app and ask it which flows you have. A 401 or 403 usually means the account isn't on Pro, or the key was deleted.
In Claude Code, /mcp also shows whether the Gumloop server is connected. It's one of the Claude Code commands worth knowing.
Use the Gumloop CLI
The CLI is the same 92 tools as commands. AI agents that run commands, like Claude Code, Codex and OpenCode, use it on their own, and you can type the same commands in a terminal or a script.
Every tool name becomes a command with dashes, so list_flows runs as gumloop-cli list-flows.
npm install -g @thenavidm/gumloop-mcp-cli
gumloop-cli
gumloop-cli list-flows
gumloop-cli get-input-schema --saved-item-id YOUR_FLOW_ID
gumloop-cli start-flow --payload-file ~/gumloop/weekly-report.json --confirm
gumloop-cli get-run-details --run-id YOUR_RUN_IDThe bare gumloop-cli lists every command, gumloop-cli which <words> finds the command for a task, and gumloop-cli <command> --help shows what a command takes. Every run, message, upload and change needs --confirm, the terminal's version of your approval.
gumloop-cli install <app> adds the server to Claude Code, Codex, Claude Desktop, Cursor, VS Code or Gemini CLI, in each app's own format.
These are the flags you'll use most:
| Flag | What it does |
|---|---|
--json | Prints JSON |
--compact | Prints the JSON on one line |
--select a,b.c | Keeps only those fields, and a dotted path goes deeper |
--agent | Machine mode: compact JSON, no prompts, and it never confirms anything |
--confirm | Lets a write that asks first go ahead |
--dry-run | Shows what a write would do, without doing it |
A script can branch on the exit code:
| Exit code | What it means |
|---|---|
| 0 | It worked |
| 1 | Something unexpected went wrong |
| 2 | The command was typed wrong, or a write needed --confirm |
| 3 | It wasn't found |
| 4 | Gumloop rejected the credentials |
| 5 | Gumloop failed or couldn't be reached |
| 7 | You hit a rate limit, so wait and try again |
| 10 | Nothing is set up yet |
MCP server or CLI: which one?
Both are the same program with the same 92 tools. The difference is when your AI pays for them, in the tokens it reads.
- MCP server
- 56,700 tokens
- CLI
- Nothing
- MCP server
- 1,500 tokens
- CLI
- Nothing
- MCP server
- Nothing more, or in Claude Code the tools it picks
- CLI
- 3,200 tokens, once
- MCP server
- 1,134,000 tokens
- CLI
- 3,200 tokens
- MCP server
- Yes
- CLI
- No, there's no terminal there
- MCP server
- No
- CLI
- Yes
An app that loads every tool up front sends the full list with every message, whether you mention Gumloop or not. Claude Code doesn't by default: its tool search sends only the tool names and the server's instructions, and loads a tool's full definition when your AI reaches for it.
The CLI costs nothing until Gumloop comes up. Then your agent reads its skill file once and runs the commands it needs. With the skill added, Claude Code also lists its one-line description with every message, about 60 tokens.
When the whole conversation is about Gumloop, the gap closes. Then the MCP server is the better experience, because you ask in plain language and your AI never has to look up a command.
How to spend less
In Claude Code, leave tool search on, which it is unless you've set ENABLE_TOOL_SEARCH=false.
Turn the server off when you aren't working with Gumloop. In Claude Code that's the /mcp panel, and every AI app has its own switch. GUMLOOP_READ_ONLY=1 cuts it to the 50 reading tools.
Or install the CLI and connect the server later, on the days it earns its place. Every tool stays in reach, and the standing cost drops to nothing.
Every number here was measured on October 5, 2026 in Claude Code 2.1.286 with Claude Opus 5.5. It's the same one-line prompt with and without the server connected, once with tool search off so every tool loads, and once with Claude Code's default. The skill was measured the same way, and other apps and models count tokens a little differently.
Flows, agents and approvals
A flow run starts with start_flow, using the inputs get_input_schema lists, and comes back with a run ID. Your AI checks that ID with get_run_details instead of starting the flow again. Only a flow's output steps show up as its final outputs.
An agent works in sessions. create_session can start the agent working right away, and when it needs your OK for a tool, the session pauses until resolve_session_approvals answers. Your AI shows you what the agent wants first. A busy agent takes new messages through its queue.
Runs, chats and Brain searches spend credits, and agents can act in the apps you've connected to Gumloop. That's why each of those asks first, even when the step sounds small.
Team admin tools, like adding people to a workspace or setting a role's credit limit, need the right role in your organization. Full data exports are for Enterprise.
Watch out: Gumloop limits how many agents run at once across your organization: 25 on Pro and 100 on Enterprise. On Pro, extra work is refused rather than queued.
Every Gumloop tool
The tables below list all 92 tools, grouped by what they're for. Of these, 50 only read, and 42 spend credits or change something in your Gumloop account or on your computer.
Flows, runs and files
start_flow- What it does
- Runs a saved flow, which can spend credits.
- Kind
- Asks first
kill_flow- What it does
- Stops a flow run and its subflows.
- Kind
- Asks first
get_run_details- What it does
- Reads a run's status and its final outputs.
- Kind
- Reads
list_workbooks- What it does
- Lists your workbooks and their saved flows.
- Kind
- Reads
list_flows- What it does
- Lists your saved flows.
- Kind
- Reads
get_input_schema- What it does
- Shows the inputs a saved flow takes.
- Kind
- Reads
get_run_history- What it does
- Lists a flow's 10 most recent runs.
- Kind
- Reads
download_file- What it does
- Saves a file from a run to a new private file.
- Kind
- Reads
download_files- What it does
- Saves several files from runs to a new private file.
- Kind
- Reads
upload_file- What it does
- Uploads a file, up to 3 MB, for your flows to use.
- Kind
- Asks first
upload_files- What it does
- Uploads several files for your flows to use.
- Kind
- Asks first
Agents
list_agents- What it does
- Lists the agents you can use.
- Kind
- Reads
create_agent- What it does
- Creates an agent.
- Kind
- Asks first
retrieve_agent- What it does
- Reads one agent.
- Kind
- Reads
update_agent- What it does
- Changes an agent's settings.
- Kind
- Asks first
list_agent_versions- What it does
- Lists an agent's saved versions, newest first.
- Kind
- Reads
retrieve_agent_version- What it does
- Reads one version of an agent, with what changed.
- Kind
- Reads
update_agent_skills- What it does
- Adds or removes skills on an agent.
- Kind
- Asks first
list_agent_mcp_servers- What it does
- Lists the MCP servers attached to an agent.
- Kind
- Reads
attach_agent_mcp_server- What it does
- Attaches an MCP server to an agent, or updates it.
- Kind
- Asks first
detach_agent_mcp_server- What it does
- Detaches an MCP server from an agent.
- Kind
- Asks first
list_artifacts- What it does
- Lists the files an agent made.
- Kind
- Reads
download_artifact_file- What it does
- Saves a download link for an agent's file to a new private file.
- Kind
- Reads
Agent sessions
list_sessions- What it does
- Lists an agent's sessions.
- Kind
- Reads
create_session- What it does
- Starts a session with an agent, which can begin work at once.
- Kind
- Asks first
retrieve_session- What it does
- Reads a session, with its messages and state.
- Kind
- Reads
rename_session- What it does
- Renames a session.
- Kind
- Asks first
send_message- What it does
- Sends a message in a session and lets the agent continue.
- Kind
- Asks first
cancel_session- What it does
- Stops a running session.
- Kind
- Asks first
upload_session_file- What it does
- Uploads a file into a session.
- Kind
- Asks first
resolve_session_approvals- What it does
- Answers what a paused session is waiting on, like a tool approval.
- Kind
- Asks first
list_queued_messages- What it does
- Lists the messages waiting in a session's queue.
- Kind
- Reads
queue_session_message- What it does
- Queues a message for after the agent's current turn.
- Kind
- Asks first
update_queued_message- What it does
- Changes a queued message.
- Kind
- Asks first
delete_queued_message- What it does
- Removes a queued message.
- Kind
- Asks first
send_queued_message- What it does
- Sends a queued message now, interrupting the agent.
- Kind
- Asks first
Models and chat
create_chat_completion- What it does
- Sends a chat to any model Gumloop supports, which spends credits.
- Kind
- Asks first
list_models- What it does
- Lists the models you can use.
- Kind
- Reads
route_model- What it does
- Asks Gumloop's router which model it would pick for a message, and why.
- Kind
- Reads
Connected MCP servers
list_mcp_servers- What it does
- Lists the MCP servers you can see.
- Kind
- Reads
retrieve_mcp_server- What it does
- Reads one MCP server.
- Kind
- Reads
list_mcp_server_tools- What it does
- Lists an MCP server's tools.
- Kind
- Reads
list_mcp_server_resources- What it does
- Lists an MCP server's resources.
- Kind
- Reads
read_mcp_server_resource- What it does
- Reads one resource from an MCP server.
- Kind
- Reads
list_mcp_server_prompts- What it does
- Lists an MCP server's prompts.
- Kind
- Reads
get_mcp_server_prompt- What it does
- Fills in one of an MCP server's prompts.
- Kind
- Reads
call_mcp_tools- What it does
- Runs up to five MCP tool calls at once.
- Kind
- Asks first
Company Brain
search_brain- What it does
- Searches your Company Brain, which spends credits.
- Kind
- Asks first
list_brain_sources- What it does
- Lists your Company Brain sources.
- Kind
- Reads
create_brain_source- What it does
- Creates a file-upload source in your Company Brain.
- Kind
- Asks first
get_brain_source- What it does
- Reads one Brain source.
- Kind
- Reads
delete_brain_source- What it does
- Deletes a Brain source and all its files, for good.
- Kind
- Asks first
list_brain_files- What it does
- Lists a source's files and how far indexing has got.
- Kind
- Reads
upload_brain_files- What it does
- Uploads up to 25 files to a Brain source.
- Kind
- Asks first
delete_brain_file- What it does
- Removes a file from a Brain source.
- Kind
- Asks first
get_brain_source_estimate- What it does
- Reads what indexing a source will cost in credits.
- Kind
- Reads
approve_brain_source- What it does
- Approves a draft source, which starts indexing and spends credits.
- Kind
- Asks first
Skills and browser profiles
list_skills- What it does
- Lists your skills.
- Kind
- Reads
create_skill- What it does
- Uploads a skill package with its SKILL.md.
- Kind
- Asks first
update_skill- What it does
- Replaces a skill's files.
- Kind
- Asks first
delete_skill- What it does
- Deletes a skill.
- Kind
- Asks first
download_skill_file- What it does
- Saves a download link for a skill to a new private file.
- Kind
- Reads
list_browser_profiles- What it does
- Lists your browser profiles, the sign-ins an agent's browser uses.
- Kind
- Reads
import_browser_profile_cookies- What it does
- Adds sign-in cookies you provide to a browser profile.
- Kind
- Asks first
Evaluations
list_evaluations- What it does
- Lists an agent's evaluation results.
- Kind
- Reads
run_evaluations- What it does
- Grades up to 200 of an agent's finished sessions.
- Kind
- Asks first
get_evaluation_metrics- What it does
- Counts an agent's grades and tags over a time window.
- Kind
- Reads
retrieve_evaluation- What it does
- Reads one evaluation result.
- Kind
- Reads
get_evaluation_config- What it does
- Reads an agent's evaluation settings.
- Kind
- Reads
update_evaluation_config- What it does
- Changes an agent's evaluation settings.
- Kind
- Asks first
get_evaluation_options- What it does
- Lists the values evaluation settings can take.
- Kind
- Reads
list_organization_evaluations- What it does
- Lists your organization's evaluations.
- Kind
- Reads
create_organization_evaluation- What it does
- Creates an organization evaluation.
- Kind
- Asks first
get_organization_evaluation- What it does
- Reads one organization evaluation.
- Kind
- Reads
update_organization_evaluation- What it does
- Changes an organization evaluation.
- Kind
- Asks first
delete_organization_evaluation- What it does
- Deletes an organization evaluation.
- Kind
- Asks first
set_organization_evaluation_targets- What it does
- Sets which agents an evaluation grades.
- Kind
- Asks first
run_organization_evaluation- What it does
- Grades up to 200 sessions with an organization evaluation.
- Kind
- Asks first
list_organization_evaluation_results- What it does
- Lists an evaluation's results across your agents.
- Kind
- Reads
get_organization_evaluation_result- What it does
- Reads one evaluation result in full.
- Kind
- Reads
get_organization_evaluation_metrics- What it does
- Counts an evaluation's grades over a time window.
- Kind
- Reads
Teams and organization admin
get_organization_audit_logs- What it does
- Reads your organization's audit log for a time period.
- Kind
- Reads
manage_project_users- What it does
- Adds or removes people from a workspace.
- Kind
- Asks first
manage_permission_group_users- What it does
- Adds or removes people from a custom role.
- Kind
- Asks first
list_role_credit_limits- What it does
- Lists each custom role's monthly credit limit.
- Kind
- Reads
get_role_credit_limit- What it does
- Reads one role's monthly credit limit.
- Kind
- Reads
set_role_credit_limit- What it does
- Sets or clears a role's monthly credit limit.
- Kind
- Asks first
export_data- What it does
- Starts a full data export for your organization, on Enterprise.
- Kind
- Asks first
get_export_status- What it does
- Reads an export's status, and saves the file once it's ready.
- Kind
- Reads
list_teams- What it does
- Lists your teams.
- Kind
- Reads
list_organizations- What it does
- Reads your organization.
- Kind
- Reads
Your accounts
list_accounts- What it does
- Lists the accounts you've set up, without their keys.
- Kind
- Reads
Is the Gumloop MCP server safe?
Runs spend credits, and agents can act in your connected apps. So 42 tools ask first: every flow run, chat, session message and approval, every upload, every change to agents, skills, Brain sources and evaluations, and every admin change. They're the ones marked "Asks first" in the tool tables above.
Reading flows, sessions, results and settings never asks, because it changes nothing.
When your AI calls one of them, the call needs a yes first. Where you use it decides who gives it:
- Claude Code (2.1.246 and later) asks you before every call, in every one of its permission modes.
- An app that can show forms asks you in a form.
- Any other app takes your AI's
confirm: trueas the yes, so tell your AI to check with you first. - An agent with no person to ask needs
GUMLOOP_CONFIRM=model, so itsconfirm: truecounts in every app. - In a terminal, you add
--confirmto the command.
If the answer is no, nothing reaches Gumloop.
Make it read-only
Set GUMLOOP_READ_ONLY=1 and every tool that asks first disappears from the tool list, leaving 50 reading tools.
Keep a log of every write
Set GUMLOOP_AUDIT_LOG to a file path. The server writes one line per attempted write, allowed or blocked, with what it was about to do and who approved it.
Watch out: Agent replies, Brain documents and tool results can hold text from other people, and one can try to give your AI orders. Treat them as data, and use GUMLOOP_READ_ONLY=1 for an agent working on its own.
Your data
Your requests go straight to Gumloop, with no server of ours in between and no tracking. Your key stays in your app's config, your shell or your token file.
Downloads and exports go to new private files, and download links are saved rather than followed. Session files and Brain uploads go to Gumloop, so its own terms apply.
To cut access, delete the key on the Connectors page, and remove the server from your app's config.
Connect more than one Gumloop account
Set GUMLOOP_ACCOUNTS to a JSON list with a name, a key or a token file, and the user and team IDs for each account, and GUMLOOP_DEFAULT_ACCOUNT to the one that acts when a tool names none. Every tool takes an optional account.
An account never borrows another one's key or IDs, so a call for one account can't run as another.
Gumloop MCP server settings
Every setting is an environment variable, in your app's config or your shell.
GUMLOOP_API_KEY- Default
- none
- What it does
- Holds your Gumloop API key
GUMLOOP_TOKEN_FILE- Default
- none
- What it does
- Points at a private file holding the key, instead
GUMLOOP_USER_ID- Default
- none
- What it does
- Holds your user ID, for calls that need one
GUMLOOP_TEAM_ID- Default
- none
- What it does
- Holds your team ID, for team flows
GUMLOOP_ACCOUNTS- Default
- none
- What it does
- Lists several accounts, with their user and team IDs, as JSON
GUMLOOP_DEFAULT_ACCOUNT- Default
- the first one
- What it does
- Picks the account that acts when a tool names none
GUMLOOP_REQUEST_TIMEOUT_MS- Default
30000- What it does
- Gives up on a Gumloop request after this many milliseconds
GUMLOOP_MAX_RETRIES- Default
2- What it does
- Retries a rate-limited read this many times, and never a write
GUMLOOP_MIN_REQUEST_INTERVAL_MS- Default
150- What it does
- Waits this many milliseconds between requests
GUMLOOP_READ_ONLY- Default
- off
- What it does
1hides every tool that spends credits or changes something
GUMLOOP_ALLOW_DESTRUCTIVE- Default
- on
- What it does
0refuses the tools that ask first
GUMLOOP_AUDIT_LOG- Default
- none
- What it does
- Names a file that gets one line per attempted write
GUMLOOP_SURFACE- Default
full- What it does
searchlists three tools that find, describe and run the rest
GUMLOOP_TOOL_TIMEOUT_MS- Default
- none
- What it does
- Gives up on any tool after this many milliseconds
GUMLOOP_CONFIRM- Default
human- What it does
modellets your AI'sconfirm: trueapprove on its own, for an agent with no person to ask
GUMLOOP_HTTP_PORT- Default
8787- What it does
- Sets the port for
--http
GUMLOOP_HTTP_HOST- Default
127.0.0.1- What it does
- Sets the address for
--http, and any other needs a token
GUMLOOP_HTTP_TOKEN- Default
- none
- What it does
- Sets the bearer token every
--httprequest needs
GUMLOOP_HTTP_ALLOWED_ORIGINS- Default
- none
- What it does
- Lists other websites allowed to call
--http, comma separated
GUMLOOP_DEBUG- Default
- off
- What it does
1prints debug lines
Troubleshooting
Run the doctor first. It names the step that failed and the fix.
| What you see | What to do |
|---|---|
| A 401 or 403 error | The account isn't on Pro or above, the key was deleted, or your role lacks access. Check the key on the Connectors page |
| A flow says the user is missing | Set GUMLOOP_USER_ID, and GUMLOOP_TEAM_ID for team flows |
| A flow's inputs are refused | Read the flow's inputs with get_input_schema and use their exact names |
| A run finished with no outputs | Only a flow's output steps show up as outputs. Add one to the flow in Gumloop |
| A message gets a 409 error | The agent is busy. Queue the message, and it goes out after the current turn |
| A 429 error | You've hit a limit, like how many agents can run at once. Wait, and check before you try again |
| "…so it will not run without confirm: true" | That's the safety check working. Approve it when your app asks |
If the server doesn't show up in your app at all, run the command your app runs, in a terminal, and read the error.
More free tools for automation
Work in Gmail and Google Drive, or run your community in Circle.
Free tools
FAQs about the Gumloop MCP server & CLI
Here are the questions people ask most about the Gumloop MCP server and CLI.
The Gumloop MCP server & CLI is a free, open source program that lets an AI app like Claude, Codex or Cursor run flows and agents in your Gumloop account.
It has 92 tools for flows, agents, sessions, Brain, skills, MCP servers and evaluations, and the same tools run as a CLI that agents like Claude Code and Codex use, or that you type yourself.
An MCP server is a standard way to give an AI app real access to a tool, so it can act instead of guessing.
MCP stands for Model Context Protocol, and Claude, Codex, Cursor and many other AI apps speak it.
Every server I've made is on my MCP servers page.
The Gumloop CLI is the same program as the Gumloop MCP server, run as commands.
AI agents like Claude Code, Codex and OpenCode run them for you, and you can type them in a terminal or a script.
One npm package installs both.
Use the Gumloop MCP server in an AI app with no terminal, like Claude Desktop's chat, and the CLI in a terminal, a script or a cron job.
In an AI app that can run commands, like Claude Code, Codex or Cursor, the CLI is the lighter choice, because it costs nothing until it runs.
Yes, the Gumloop MCP server is free and open source under the AGPL-3.0-or-later license.
Gumloop's API needs the Pro plan or above, and runs, chats and Brain searches spend Gumloop credits.
You need the Pro plan or above, because Gumloop's API keys come with those plans.
You generate the key on the Connectors page.
A personal key acts as you, with your own connected accounts.
A team key can act as any team member, and each flow step's settings decide whose connected accounts it uses.
Yes, it answers a paused session's approvals, one session at a time, after you approve that answer.
Your AI shows you what the agent wants first.
Yes, the Gumloop MCP server connects as many accounts as you set up in GUMLOOP_ACCOUNTS, each with its own key and IDs.
Every tool takes an optional account, and an account never borrows another one's key.
To disconnect the Gumloop MCP server, delete its key on the Connectors page, which cuts access right away.
Then remove the server from your AI app's config.
The Gumloop MCP server works with any app that speaks MCP.
That includes Claude Code, Claude Desktop, Codex, Cursor, VS Code, Windsurf, Zed, Cline, GitHub Copilot CLI, Gemini CLI, OpenCode, OpenClaw, Antigravity and Hermes.
I did.
I'm Navid Moazzez, and I made the Gumloop MCP server & CLI as one of my free tools on navid.me.
You can read more about me.
The code is on GitHub under the AGPL-3.0-or-later license, and the package is on npm.
More MCP servers & CLIs
Related free tools
Navid.me is reader-supported. When you buy through links on this site, I may earn an affiliate commission. Read the affiliate disclaimer.
On this page
The most actionable AI newsletter for founders
Every week, get proven AI strategies, curated tools, and step-by-step systems to grow your audience, create better content, and build a profitable creator business.
No fluff, no filler, no BS. Just five minutes each week that might level up your online business and life.
P.S. Sign up now to get free access to my ultimate AI tools guide for creators.
