Skip to main content
Connect apps to Gumloop once, then use their tools from any MCP client connected to Gumloop. The Gumloop MCP server can call tools on other platforms, including Gmail, Slack, Linear, and custom MCP servers, so you don’t have to set up OAuth for every app in every client. Every call still follows your organization’s connector governance.

​
How it works

Connect custom MCP servers in Gumloop or connect apps from Connectors settings. The server catalog includes Gumloop-hosted servers, user-deployed Gumstack servers, and custom MCP servers, each with a connection status.
1

List connected and available servers

Call list_mcp_servers to browse the servers in the catalog and their connection status.
2

Inspect a server's tools

Call list_mcp_server_tools with the server_id to see the tools and connection status. If it isn’t connected, open the returned gumloop_auth_url to finish connecting.
3

Call a tool

Call call_mcp_tool with server_id, tool_name, and arguments. Include the optional ref to have it echoed in the results.
Use list_teams to find team IDs. For team-owned connections, pass the team ID as project_id. Other MCP capabilities include:
  • List resources with list_mcp_resources and read them with read_mcp_resource.
  • List prompts with list_mcp_prompts and render them with get_mcp_prompt.
For example, call call_mcp_tool with these arguments to list five recent emails through a Gmail connection:

​
Example prompts

Using my Gmail connection in Gumloop, find unread emails from today.

Create a Linear issue through Gumloop for the bug we discussed, and assign it to me.

Search my Slack messages through Gumloop for the latest project update.

Use my connected Notion tools through Gumloop to find the launch checklist.

​
Governance

Tool calls made through the Gumloop MCP server follow the same connector governance as tool calls made by Gumloop agents.
  • Credentials stay in Gumloop. Tools run inside Gumloop. Your MCP client receives tool results, never the app’s OAuth tokens.
  • Custom roles. If a custom role blocks an app or a specific tool, list_mcp_servers shows that server as blocked and call_mcp_tool rejects the call.
  • App Rules. Organization App Rules are checked on each call and can block it based on the tool and its arguments.
  • Account restrictions. Domain restrictions and App Claims control which accounts and workspaces people can connect.
  • Activity. Calls appear in Connector Activity, so admins can see who called which tool, from which source, and whether it succeeded.
You can call the same MCP tools through the REST API or the Gumloop CLI.