Skip to main content
Custom, proxied, and hosted MCP are three ways to give your agents an MCP server that isn’t in Gumloop’s built-in connector catalog. The difference is who runs the server and how much your organization manages it:
  • Custom MCP: you already have the URL of a running MCP server. Paste it in and your agent can use it. Any user can do this, for themselves or their team.
  • Proxied MCP: same idea, a URL to a server someone else runs, but an org admin registers it once for the whole organization. Gumloop sits in the middle, logs every tool call, and controls which tools people can use.
  • Hosted MCP: you have the server’s code, not a running server. Put it in a GitHub repo and Gumloop builds, runs, and updates it for you.
Check the connector catalog first. If the app is already there, use the built-in connector instead.

Which one should I use?

Start at the top and follow your answers: In words: no running server yet means Hosted. A running server that only you or your team need means Custom. A running server the whole organization should share under admin control means Proxied.

When would I use each one?

How do they compare?

Custom MCP

  1. Go to your Connectors page (Customize > Connectors in the left sidebar).
  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 in Settings > Connectors & MCP > 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 in Settings > Connectors & MCP > 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

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