Generate an instant MCP server for your API

Generate a hosted MCP server from your OpenAPI spec. Every operation becomes a tool that Claude Code, Cursor, and any other MCP client calls directly.

Animation: an OpenAPI spec is wrapped into a hosted MCP server at yourco.fernmcp.dev/api. Claude Code, Cursor, Copilot, and ChatGPT open one at a time from a dock, connect to the server, and call a tool from their chat window, and the matching endpoint in the spec answers.

Agents can now find and call our API, not just read about it. Fern is helping us drive more API adoption by doing less. It’s one more return on the spec we already maintain to power our Docs, SDKs, and CLI.

Christel BuchananCofounder and CEO
ChatAndBuild

Generated from your spec, hosted by Fern

One tool per operation

Every supported operation in your spec becomes a tool with a typed input schema.

Curate the tools agents see

Filter, group, and merge operations into fewer, clearer tools, so agents pick the right one.

Add custom tools and hooks

Write tools and request hooks in TypeScript for workflows no single operation covers.

Hosted at your own URL

Fern builds and runs the server at yourco.fernmcp.dev, so there is no infrastructure to manage.

Same URL on every release

Regenerate with the same slug and the server updates in place, so agent configs keep working.

Safe deploys

If a deploy fails, the server keeps serving the previous deployment and agents keep working.

From spec to agent in three steps

Add an MCP target to your Fern config, run one command, and connect any agent to the URL it prints.

yourco-api
sdk-config.yml
fernsdk-config.yml
1schemaVersion: sdk-config/v12sdkName: api3source:4  specs:5    - id: api6      type: openapi7      path: ./openapi.json8targets:9101112
Problems0
Output
Debug Console
Terminal
Ports
Spell Checker1
zsh+
>test
Ln 9, Col 1Spaces: 4UTF-8LFYAML

Every endpoint, a tool

Each operation in your spec becomes a tool, and its parameters and request body become the input schema agents see in tools/list. Rename any tool with x-fern-mcp-name in an overlay.

Connect any agent with one snippet

The dashboard builds the connect snippet for each client, with the credential your API expects already in place.

Ready for any MCP client

The Connect button builds setup for Claude Code, Cursor, VS Code, raw JSON, or a plain URL.

Your auth, passed through

Agents send your API’s own credential as a header. A missing one returns an error that names the header to add.

Monitor it from the dashboard

Every hosted server gets an overview with its connection URL, tools, generation history, and analytics.

Manage in the dashboard

Roll back in one click

Pick an earlier successful generation and Fern redeploys it at the same URL.

See agent traffic

Analytics shows how often agents call your server, starting with the first request.

Pause without deleting

Take the endpoint offline, then resume on the same deployment when you're ready.

Make your API callable by every agent

Bring your OpenAPI spec. Fern generates the MCP server, hosts it, and redeploys it when the spec changes.