ReadMe MCP. Search your entire developer knowledge base from chat.

Your AI client needs direct access to your company's knowledge base. This server connects it straight to your ReadMe developer documentation, letting your agent search, read, and manage every guide, changelog, and custom page like a human tech writer would.

Searching the Guides. When you need specific info, you run search_docs to perform full-text queries across all published guides and API references. That tool finds relevant snippets instantly, so your agent doesn't waste time reading pages it doesn't need to.

Pinpointing Content. If you know the exact page ID, you use get_doc to pull the complete Markdown content of that specific documentation page. For standalone sections that don't fit into a main guide, you use get_custom_page to get its full text. You can also check out high-level structural details for your whole ReadMe setup by calling get_project.

Mapping the Structure. To understand how everything fits together, you list all top-level documentation categories using list_categories. That gives you a map of the site's content structure. If you want to drill down into what belongs in one of those sections, you use get_category_docs to list every individual page under a specified category, and then get_category retrieves specific details about that single category itself.

Handling Custom Builds. For pages built outside the standard documentation flow, your agent first calls list_custom_pages to see what exists. It then uses get_custom_page to pull in the full content of any standalone page you've created.

Tracking Changes and History. Keeping track of updates is a job for two tools. You run list_changelogs to get an index of every published changelog post, letting your agent see what major changes have happened over time. When you need the full scoop on one release, you use get_changelog to retrieve all the detailed content for that specific title or identifier.

Your AI client can now execute these actions—search, list, get details, and fetch content across guides, categories, changelogs, and custom pages—all from a single chat interface.