Skip to main content
Gumloop already has 50+ built-in connectors. Use one of these only when the server isn’t in the catalog.

​
Custom MCP

  1. Go to Connectors.
  2. Click Add Custom MCP in the top-right corner of the page.
  3. Enter the server URL in MCP Server URL and click Connect. If your organization has a Managed Tunnel, you first choose Public URL (HTTPS) or Private (via tunnel).
  4. Confirm the detected auth. If it’s OAuth, click Authenticate. Otherwise add a token, API key, or custom header.
  5. Open the agent, click + Add in the Connectors section, search for the server you just added, add it, and click Save.
The server must speak Streamable HTTP or SSE over HTTPS. localhost and STDIO aren’t supported. On Enterprise, Managed Tunnels can reach a server inside your network.

​
Proxied MCP

An admin registers one external URL at Organization → Proxied MCPs. Gumloop proxies traffic so the org gets activity logs and tool access control without deploying code. Auth is None, API Key, or OAuth 2.0. None / API Key shares one org secret. OAuth makes each person sign in. Full setup: Proxied MCPs.

​
Hosted MCP

An admin connects GitHub at Organization → Hosted MCPs. Gumloop builds, deploys, and routes the server. Custom roles gate access. Full setup: Hosted MCPs.

​
Whose credentials run on a shared agent

Gumloop doesn’t silently share one person’s personal login.

​
FAQ

One URL you already host → Custom. Org wants one governed external server → Proxied. Org wants to run its own server code without extra hosting → Hosted.
Gumloop must reach the server over the public internet (or an Enterprise managed tunnel). Deploy it, or expose it with Cloudflare Tunnel / ngrok.
Adding it in Connectors is not enough. Open the agent and add that custom MCP under Connectors.

Custom MCP servers

URL, headers, and OAuth

Hosted MCPs

Deploy from GitHub