TL;DR
Fern Agent is one agent for every part of running your docs site, live now in your Dashboard, Slack, and coding agent via MCP.
Running a docs site on Fern involves many different kinds of tasks: rewriting a paragraph, reorganizing the nav, updating the CSS, reading through user feedback, and finding out which pages people abandon. Each one usually means leveraging a tool to pull the data and another tool to make the changes.
More tasks has always meant more tools, but agents are changing that arithmetic: now, one person can do more tasks in parallel with fewer tools. That's why we built Fern Agent: one agent for the content, styling, information architecture, and analytics behind your docs site. For our customers, it's live today in your Dashboard.
Meet Fern Agent
| You ask | What Fern Agent does |
|---|---|
| "Which pages do people leave without finding what they came for?" | Reads your usage data and answers |
| "Move the SDK guides under Reference and fix the links." | Restructures navigation in docs.yml |
| "My custom component overflows on mobile." | Evaluates your React and CSS |
| "Rewrite the authentication quickstart to cover the OAuth flow." | Edits the markdown |
| "Read the last quarter of feedback and tell me what's broken." | Groups feedback by theme |
Before it edits anything, Fern Agent reads what you've already published, searching the same index behind Ask Fern. This keeps its edit consistent with the pages around it. It fetches URLs when it needs context beyond your docs, and it screenshots pages when it needs to look at a design.
Fern Agent is also an expert on Fern itself. When you ask how to improve a page, it flags the component you hand-rolled and suggests a Fern component instead. If your API Explorer is sending empty optional parameters, Fern Agent tells you it's because send-optional-defaults is off. Because Fern Agent knows how your site is configured, the changes it makes are ones you can actually ship.
Use it from where you already work
Everything Fern Agent does in the Dashboard, it also does over MCP in your terminal and in Slack. Drive it from Claude Code or whatever agent you already use, and install both from the Dashboard chat panel with a single click.
You stay in control
Fern Agent's edits are restrained by default. We built it to modify only the lines that need changing rather than regenerate the page, so a small fix shows up as a small diff instead of a rewritten file you have to review line by line. Preview links and pull request comments work with the review process you already use.
By design, Fern Agent has no write access to your API keys, member invites and permissions, plan, or organization settings. When you ask it to update billing information or add a new teammate, it points you to the right Dashboard page so you can make those changes yourself.
Open your Dashboard
For our Fern Docs customers, Fern Agent is live now in beta. Support for SDKs, CLI, and MCP server generation is next.
Open your Dashboard and ask it something about your docs. If you're not on Fern yet, book a demo and we'll show you Fern Agent working on your own site.
Built by Clay Tondreau and Mathieu Legault. A post on how they built it is coming soon.