Skip to main content
Turn a public OpenAPI or Swagger 3.x document into a hosted MCP server. You can try a public spec before creating an account.

​
How does it work?

  1. Paste a public OpenAPI URL, or upload a .json / .yaml file.
  2. Review the generated tools. Enable, disable, rename, or reorder them.
  3. Create a free account to deploy. Hosted MCP on the Developer plan does not require a card.
  4. Copy the client snippet into Cursor, Codex, Claude Code, ChatGPT, or VS Code.
The hosted server proxies your live API. MCP clients authenticate with a gateway token, not your upstream API key. A WIP or branch API on your laptop is not reachable from hosted MCP Gateway — self-host the CLI for that.

​
What is supported?

  • OpenAPI 3.0 and 3.1
  • File upload or URL import
  • Tool curation before deploy
  • A free Developer tier
Swagger 2.0 is not supported. Convert the document to OpenAPI 3.x first.

​
Try before you sign up

You can preview tools from a public spec on the app without creating an account. Deploying, minting client tokens, and storing upstream credentials require a Fetch Hive account.

​
What is the agent readiness report?

After compile, Fetch Hive scores how ready the generated tools are for agents. You see:
  • How many tools were compiled
  • Blocking issues and warnings
  • An estimate of how many tokens the tool list costs on every model turn
  • Compatibility notes for ChatGPT, Claude, and Gemini
The report explains each finding. Detailed remediations, including rewritten tool descriptions, unlock when you create an account. One sample rewrite is shown during the preview so you can see the quality of the guidance.