Two MCP servers, one for each side of your docs: the Editor MCP lets your team’s AI agents write and publish pages, and the Reader MCP lets your readers’ AI tools search and read what you have published.
Want the agent that works inside DeveloperHub instead? That is the AI Agent →
First, Claude Code adds a callout through the Editor MCP, saved as a draft. Then the same docs in Git, and in the visual editor.
Work on your docs from Claude Code, Claude, Cursor, Codex or any other AI client that supports MCP. Everyone connects as themselves, so their agent can reach exactly what they can, and nothing more.
claude mcp add --transport http developerhub https://ai.developerhub.io/mcpYour agent finds the right page and reads it before it writes a word.
Ask for a new page, a rewrite or a quick fix. It lands as a draft for your team to review.
When you are happy, ask it to publish a page, a section or a whole version.
Hand it a new OpenAPI spec and your API reference is updated as a draft, ready for review.
Ask it to find the broken links across your docs, and to fix them while it is there.
It reads what readers searched for and could not find, and what they said about your pages.
Search analytics and written feedback come with Pro and Enterprise.Everything it can do →
Every page an agent writes or rewrites waits as a draft. Your team reads it in the editor, tweaks what needs tweaking, and publishes when it is ready. Your readers never see a half-finished change.
Every request to the Acme API carries an API key. Keys belong to one project, and you can rotate them at any time.
Send the key as a bearer token in the Authorization header of every request.
Create an MCP key for a release pipeline, a scheduled job or a script, and it can work on your docs without anyone signing in.
Your release pipeline asks the agent to write up what shipped. The notes arrive as a draft, ready for someone to read and publish.
A nightly job checks your docs for broken links, so you hear about them before a reader does.
A weekly job collects the searches that came back empty and turns them into your next pages to write.
Search analytics come with Pro and Enterprise.
Your agent learns DeveloperHub’s format from the server itself, and everything it writes is checked, so nothing gets lost on the way in. Callouts, code blocks, tabs and tables come out the way your writers would make them.
Create an order with one call. Use your test key while you build.
Your readers build against your product with an AI assistant open. Switch the Reader MCP on and their assistant can search your docs and read any page or API endpoint, straight from the source.
claude mcp add --transport http developerhub-docs https://docs.developerhub.io/mcpIt sees what any visitor sees. Pages you have not published, or have kept for certain readers, stay out of sight.
The Reader MCP comes with the AI Assistant on Pro and Enterprise, for public docs. Private docs? Talk to us.
Not every AI tool connects to a server. Most simply fetch a page, and your docs are ready for them too.
Every page and every API endpoint, listed for AI tools and kept up to date for you.
Each page also comes as clean Markdown, so assistants such as ChatGPT, Claude and Perplexity read your content, not your layout.
Your docs offer tools to AI agents working in the reader’s browser. It is brand new, and browsers are only starting to support it.
No. What an agent writes waits as a draft until someone publishes it. For automations, you can create keys that cannot publish at all.
Claude Code, Claude, Cursor, Codex and any other AI client that supports MCP. Connecting Claude Code takes one command.
An agent can only do what the person who connected it can do, and only in projects where an admin has switched it on. MCP keys go further: you choose what each key can do and when it expires.
The Editor MCP is for your team: their agents write, edit and publish your docs. The Reader MCP is for your readers: their AI tools search and read what you have published.
Yes, both servers are. The Editor MCP is listed as io.developerhub/editor and the Reader MCP as io.developerhub/docs.
The Editor MCP and MCP keys are on every plan, Free included. The Reader MCP comes with the AI Assistant on Pro and Enterprise, for public docs.
Fourteen days free, no card. Switch the Editor MCP on, connect your AI client, and ask it for your first draft.