Skip to main content
A hosted MCP Gateway can be used by Fetch Hive agents in any workspace on your account. The agent calls only the tools you select. External MCP clients (Claude, ChatGPT, Cursor) keep using the published gateway URL and their own client tokens. They are not affected by which tools you attach to an agent. You need at least one workspace to create or attach an agent. You do not need a workspace to own a gateway.

​
How do I attach a gateway to an agent?

  1. Publish the gateway so its status is Live.
  2. Open an agent that uses a model with remote MCP support, then add MCP Gateways from the tool picker.
  3. Select at least one published tool. You can attach up to 50 tools. There is no “all tools” default.
  4. Save. The gateway appears as a node on the agent canvas.
From a live gateway’s overview you can also click Create Agent. That creates a workspace agent with the gateway already attached and a starter set of tools (up to 20). If your account has no workspace yet, create one first and try again.

​
How do I choose tools?

The attach sheet lists the currently published tools. Search, then check the tools the agent should receive. New tools that appear after a later publish stay unchecked until you add them. If you republish the gateway and some selected tools disappear, the agent skips those names. The editor shows which tools are missing. You can drop them from the selection. The stored list is not rewritten silently.

​
What does pause do?

Pausing a gateway stops hosted MCP clients from calling it. Agents that have it attached skip those tools for that turn instead of failing the whole run. Resume (publish again) restores both external clients and attached agents.

​
Can I pin a version for an agent?

Yes. An attached agent can follow the published version (default) or pin a specific published version. Pinning is only for that agent. External clients always follow the live published version.

​
How do workflows use a gateway?

Workflows do not have a dedicated MCP Gateway step. Run an agent step that already has the gateway attached.

​
Connected MCP servers

Connected MCP servers are third-party MCP endpoints you add yourself (not hosted by Fetch Hive). They live on the MCP Gateway page under the Connected MCP servers tab. Bookmarks to workspace Settings → Connected MCP servers redirect there. Create a connected server with its URL and credentials. Secrets are stored encrypted and are not shown again after save. Leave a token or header value blank to keep the saved secret. Use Clear token to remove it. Last tested updates when a connection test succeeds.