|
| 1 | +--- |
| 2 | +title: Model Context Protocol |
| 3 | +description: Learn how to use the Model Context Protocol (MCP) to integrate AI capabilities with your Fern documentation |
| 4 | +--- |
| 5 | + |
| 6 | +<Note> |
| 7 | +The MCP generator is in development. Interested in offering an MCP server for your API? Reach out via Slack or [email protected]. |
| 8 | +</Note> |
| 9 | + |
| 10 | +[Model Context Protocol (MCP)](https://modelcontextprotocol.io) is an open standard by Anthropic that streamlines how AI applications connect with external data sources and tools, enabling AI agents to directly use your product’s APIs. |
| 11 | + |
| 12 | +A “Built with Fern” MCP server augments your existing TypeScript SDK with MCP capabilities and integrates seamlessly with popular AI-powered tools including Cursor, Claude Desktop, and Windsurf. You can find a full list of MCP clients [here](https://modelcontextprotocol.io/clients). |
| 13 | + |
| 14 | +## How it works |
| 15 | + |
| 16 | +**Fern can build a production-ready MCP server on top of your existing TypeScript SDK.** We maintain the package in its own `git` repository, making it easy for your existing developer community to discover and contribute to the project. We can also automatically publish new versions of the package to `npm` for you. |
| 17 | + |
| 18 | +End users of a “Built with Fern” MCP server can typically get started with a **single config**: |
| 19 | + |
| 20 | +```json |
| 21 | +{ |
| 22 | + "mcpServers": { |
| 23 | + "<your-company>": { |
| 24 | + "command": "npx", |
| 25 | + "args": [ "-y", "<your-company>-mcp-server@latest" ] |
| 26 | + } |
| 27 | + } |
| 28 | +} |
| 29 | + |
| 30 | +``` |
| 31 | + |
| 32 | +To learn more about Model Context Protocol (MCP) servers, check out the [MCP server docs](https://modelcontextprotocol.io/quickstart/server). |
| 33 | + |
| 34 | +## Case study: Webflow |
| 35 | + |
| 36 | +**We worked with Webflow to launch their [official MCP server](https://www.npmjs.com/package/webflow-mcp-server)** using the existing [Fern-generated TypeScript SDK](https://github.com/webflow/js-webflow-api). |
| 37 | + |
| 38 | +Check out the [source code on GitHub](https://github.com/webflow/mcp-server) and read the announcement from Webflow’s CTO on X: |
| 39 | + |
| 40 | +<blockquote class="twitter-tweet"><p lang="en" dir="ltr">🚢 We just launched our Webflow MCP server! Check out Allan’s thread to learn more, watch the demo video below, then give it a try here: <a href="https://t.co/T2K3OpJ6O8">https://t.co/T2K3OpJ6O8</a> <a href="https://t.co/bFUfC64pcf">https://t.co/bFUfC64pcf</a> <a href="https://t.co/oonYuyjHiT">pic.twitter.com/oonYuyjHiT</a></p>— Webflow (@webflow) <a href="https://twitter.com/webflow/status/1907465818088054843?ref_src=twsrc%5Etfw">April 2, 2025</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> |
| 41 | + |
| 42 | +## Why "Built with Fern"? |
| 43 | + |
| 44 | +There are a few advantages in partnering with Fern to build your MCP server: |
| 45 | + |
| 46 | +- **Keep your MCP server in sync with your API** - our implementation augments your existing TypeScript SDK. |
| 47 | +- **Integrate with Fern Docs and AI Chat** - give your users the ability to query your docs directly from inside of Cursor, Claude Desktop, and more. |
| 48 | +- **For APIs at scale** - leverage our team’s expertise developing, testing, and deploying MCP servers for products with hundreds of API endpoints. |
| 49 | +- **Thought partnership** - the AI ecosystem is changing fast and we’re here to navigate it together with you, from the latest techniques to the tools that power them. |
| 50 | + |
| 51 | +## How else can Fern support my MCP server launch? |
| 52 | + |
| 53 | +We can provide **ready-to-use social media assets** for announcing your MCP support: |
| 54 | + |
| 55 | +- LinkedIn post template |
| 56 | +- X (Twitter) post template |
| 57 | +- Email announcement template |
| 58 | +- Social media graphics |
| 59 | + |
| 60 | +As well as all of the **detailed documentation** that you’ve come to expect from Fern: |
| 61 | + |
| 62 | +- Getting started guide |
| 63 | +- API reference |
| 64 | +- Usage guidelines and best practices |
0 commit comments