> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fetchhive.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Gateway

> Turn an OpenAPI document into a hosted MCP server with curated tools, client tokens, and plan quotas

MCP Gateway publishes your API as a hosted MCP server. You import an OpenAPI document, curate the generated tools, store upstream credentials, mint client tokens, and publish a version that MCP clients can call.

You do not need a workspace to use MCP Gateway. It is account-scoped.

## How do I create a gateway? <a href="#create-a-gateway" id="create-a-gateway" />

Open **MCP Gateway** and click **Create**. Give the gateway a name and a URL slug. The public MCP path is `/g/{slug}` on the hosted MCP host.

Choose a source:

* **URL** — a public HTTPS OpenAPI document. Fetch Hive fetches it through the hosted runtime, not from your browser.
* **Upload** — an OpenAPI 3.0 or 3.1 document up to 5 MB.

Compile runs automatically. Small specs finish in the create request. Larger specs stay in **Compiling** until you refresh.

Tool names, titles, and descriptions come from the OpenAPI metadata. You can rename, retitle, disable, or reorder tools after compile. Those edits survive a recompile. Operations that disappear from a later spec stay in the list as disabled orphans so you can see what changed.

## How do I connect the upstream API? <a href="#upstream-credentials" id="upstream-credentials" />

Set upstream credentials before you publish if the API requires auth. Supported types:

* None
* Bearer token
* Basic username and password
* API key header
* Custom headers

Fetch Hive stores credentials encrypted. The dashboard never shows the secret again after you save it. Use **Test** to confirm the hosted runtime can authenticate to the API. Test does not echo the upstream body.

Only account owners can set, rotate, or clear credentials.

## How do I mint MCP client tokens? <a href="#client-tokens" id="client-tokens" />

MCP clients authenticate with a gateway token, not your Fetch Hive login and not the upstream API key.

Create a token with a name. The raw value is shown **once**. Store it in the MCP client. Later list views show only the prefix and last four characters.

Revoke a token to drop it from the live server immediately. Only account owners can mint or revoke tokens.

## How do I publish, pause, or roll back? <a href="#publish" id="publish" />

**Publish** freezes the current compiled tools and credentials into a live version. Later edits go to a new working copy and do not change what MCP clients see until you publish again.

**Unpublish** pauses the gateway. MCP clients receive an unavailable response until you publish again.

**Rollback** points traffic at a previously published version without changing your working copy.

## What are the plan limits? <a href="#quotas" id="quotas" />

MCP Gateway uses your existing Fetch Hive plan. Typical caps:

| Plan       | Gateways | Tools per gateway | Requests per day |
| ---------- | -------- | ----------------- | ---------------- |
| Developer  | 1        | 25                | 100              |
| Growth     | 5        | 100               | 5,000            |
| Pro        | 20       | 500               | 50,000           |
| Enterprise | Custom   | Custom            | Custom           |

Lifetime plans match the equivalent Growth or Pro caps. Hitting a gateway or tool cap returns an upgrade error. Hitting the daily request cap returns a rate-limit error until UTC midnight.

Request logs follow your plan's log retention window. Widen the range past that window and the API asks you to upgrade.

## Connecting an MCP client

After publish, point the client at the hosted MCP URL for your slug and send the gateway token as a bearer token. Do not send upstream API keys to the MCP client.