
Overview
When a feature ships, the docs page that explains it goes stale. Fixing it means finding the right file in your docs repo, rewriting the section and getting it reviewed.
Connect Fern through its official MCP server and Agent M hands docs changes to Fern’s editor, which works in your docs site’s GitHub repo and opens a draft pull request. You review it and merge it, and merging publishes the change.
Any member can connect their own Fern account from its connector page in Maintouch.
Approve access in Fern’s sign-in window. There is no API key to paste.
Your connection starts private to you. Turn on sharing to let your teammates’ chats use it too.
Ask for a docs change and Agent M hands it to Fern’s editor, then gives you the pull request to review and merge.
Agent M can read your docs analytics, reader feedback and the questions readers ask Fern’s Ask AI.
A custom agent can keep your docs current as part of its instructions and report the pull request to review.
Agent M works through your Fern account, so it only reaches the docs sites your account can.
A GitHub repo connected to your Fern docs site. Fern’s editor makes its changes in that repo, so without one it cannot edit.
Only through a pull request you merge. Every change lands in a draft pull request on your docs repo, and nothing goes live until you merge it.
Agent M cannot merge the pull request, create API keys or change who is in your Fern organization. It also cannot do anything your Fern account cannot.
Only if you share it. A new connection is private to you, and you can open it to your org from the Fern connector page.