Skip to main content
An MCP server is an integration — Gmail, Slack, Linear, Notion, your own custom one — that exposes a set of tools your agents (or you, directly) can call. gumloop mcp lets you list the servers connected to your account, browse their tools, and invoke them on demand.

​
List servers

Prints SERVER_ID, NAME, TYPE, STATUS, TOOLS (tool count), and AUTH_URL. If a server’s STATUS is anything other than connected, the AUTH_URL column has a one-click link to finish connecting it — open it in your browser, approve, and you’re done.

​
Inspect a server

Shows the server’s full configuration — server_id, type, status, tool_count, description, the Gumloop auth URL, and the underlying MCP endpoint.

​
List the tools a server exposes

Returns a table of NAME, TOOL_CALL_ID, and DESCRIPTION. If the server isn’t connected yet, the CLI prints the auth URL you need to open instead.
You pass the tool’s NAME (not TOOL_CALL_ID) to gumloop mcp call. TOOL_CALL_ID is the internal identifier used when an agent invokes the tool through a workflow.

​
Call a tool

The arguments can come from three places (pick one): Examples:
The default text output groups results by tool, prints the status and any error, then the content of each result. MCP execution failures are reported per result, so check each printed status or use --json to pipe the structured response into another tool.