Hosted MCPs

Hosted MCPs let your organization build and deploy custom MCP servers on Gumloop’s infrastructure. You write the code in a GitHub repository, and Gumloop handles building, deploying, monitoring, and routing requests to your server. Gumloop logs every tool call, and you control access through custom roles.

​

Where to find it

Go to Settings → Organization → Hosted MCPs at gumloop.com/settings/organization/hosted-mcps.

​

Initial setup

Before creating your first hosted MCP, you need to connect GitHub. Go to Hosted MCPs → Settings (or visit gumloop.com/settings/organization/hosted-mcps/setup) to configure two connections:

​

Server list

The main Hosted MCPs page shows a table of all your organization’s servers. Each row displays:

• Server name with a status indicator. A green dot means active and a yellow dot means disabled.
• Linked GitHub repository with a badge linking to the repo
• Tool count showing how many tools the server exposes
• Last Updated timestamp

​

Filtering

Use the toolbar above the table to:

• Search by server name or repository
• Filter: My Servers Only to show only servers you created
• Filter: Show Disabled Servers to include disabled servers in the list
• Click Settings to go to the GitHub integration setup page
• Click Create to start the new server wizard

​

Creating a new hosted MCP

Click the Create button to launch a 3-step wizard that sets up a new MCP server with a GitHub repository.

​

Step 1: Basic info

Fill in:

• Server Name: A display name for your MCP server (up to 100 characters)
• Description (optional): A brief description of what your server does
• GitHub Repository: Choose which GitHub account or organization should own the repo
• Repository Name: The name for the new GitHub repo (letters, numbers, hyphens, underscores, dots)
• Visibility: Public, Private, or Internal

​

Step 2: Authentication & environment

Configure how users authenticate with your server:

• No Authentication: Anyone with access can use the server without credentials
• API Key / Credentials: Users provide API keys or tokens. You define the credential fields that users fill out in the Gumloop UI: variable name, display label, and placeholder text
• OAuth 2.0: Users authenticate through an OAuth flow with a third-party provider

You can also add Environment Variables that get injected into your server at runtime. These are developer secrets, such as database URLs and API keys for external services, and are different from user-provided credentials.

​

Step 3: Review

Review your configuration and click Create. Gumloop then:

1. Create a new GitHub repository with boilerplate MCP server code
2. Register the server in your organization
3. Redirect you to the server detail page

From there, you can push code to your repo and deploy.

​

Server detail page

Every hosted MCP has a detail page with six tabs:

​

Overview

The overview tab gives you a snapshot of server health and activity for the last 7 days:

• Total Calls: Total number of tool calls
• Unique Users: How many distinct users made calls
• Error Rate: Percentage of calls that failed
• Avg Latency: Average response time
• MCP Server URL: A unique, stable URL that always points to your current production deployment. Copy this to configure MCP clients.
• Live Deployment: Shows the current deployed commit, author, and date
• Recent Activity: A quick-look table of the most recent tool calls

The header also provides quick actions:

• Copy URL (link icon): Copy the server URL to your clipboard
• Repository button: Jump to the GitHub repo
• Deploy button: Trigger a new deployment

​

Tools

The Tools tab shows every tool your server exposes and lets you control access per custom role. The matrix view shows:

• Tool name and description for each tool
• Usage count: How many calls each tool has received
• Custom role columns: Toggle access on or off for each role
• Disable Server row: Block all tools for a specific role at once

Click Save in the toolbar to save your changes.

​

Activity

The Activity tab is a server-scoped version of the global Connector Activity page. It shows the same histogram and table, but filtered to just this server. The histogram here uses latency-based color coding:

• Green (P25): Fast calls
• Orange (P85-95): Moderately slow calls
• Red (P95+): Slowest calls

You get the same filtering, export, and refresh capabilities as the global Activity page.

​

Deployments

The Deployments tab shows your deployment history. Each deployment entry includes:

• Commit hash and message
• Status: Building, Deploying, Live, Ready, Failed, or Rolled Back
• Author: Who pushed the commit (from GitHub)
• Date: When the deployment happened

Pushes to the main branch trigger deployments automatically once you install the GitHub App. You can also manually deploy from the Deploy button in the header, choosing a specific branch or commit. The server must be active for a manual deployment. If another manual deployment is in progress, wait for it to finish before trying again.

​

Monitoring

The Monitoring tab shows live infrastructure status:

• Active Pods: How many server instances are running
• Pod Restarts: Number of times pods have restarted since the last deployment
• Runtime Logs: A live, streaming log view of your server’s output, including health checks, request logs, and errors

Use this tab to diagnose startup issues, confirm your server is healthy, or watch logs in real time.

​

Settings

The Settings tab lets you manage:

• Server Image: Upload a PNG or JPEG logo under 5 MB, shown in lists and cards
• Server Name: Update the display name
• Description: Update what the server does
• MCP Server URL: View and copy the server’s unique URL
• Authentication Method: Shows the auth type you chose during creation. You can’t change it afterward.
• Environment Variables: Add, edit, or remove developer secrets injected at runtime
• Disable Server: Temporarily disable the server. It can be re-enabled later.
• Delete Server: Permanently delete the server and all associated configuration

​

FAQ