We redesigned ReadMe from the ground up. Here's what's new: 1. Simpler admin interface that's easier to navigate 2. AI-native editor with Markdown MDX that keeps you in the loop 3. AI Writer that watches your GitHub commits and creates docs from them 4. CLI tool for working with docs locally 5. A new homepage that shows how it all fits together

AI Writer — When your team pushes code changes to GitHub, ReadMe creates a branch with suggested doc updates for you to review and merge. Docs stay current with product development without the manual chase. Connect your repo to get started: readme.com/blog/ai-writer

Your AI Dropdown now shows MCP connection options. If your project has MCP enabled, developers browsing your docs can connect their AI tools right from the page. No hunting for URLs or setup instructions. Enable it in your AI settings to try it out!

Not every doc update starts with a code change. Sometimes you just need to edit a description, add a note, or update a detail. The ReadMe MCP server lets you do this right from your IDE. A few prompts to try in your docs: 🔍 Update our docs to say the Agent uses Opus 4.6" 📝 Add a note about the new rate limit to our API reference 🔑 Rewrite the authentication section to mention SSO support Behind the scenes it creates a new branch from your live docs, applies and verifies your changes, and returns a review link so you can preview and merge. Like a pull request for your docs, without managing any of it yourself.

Developers are building in Cursor, Claude, and VS Code. Is your API connected and accessible? Generate an MCP server from your @readme docs in 3 steps so AI agents can search and execute your API directly inside their workflow. Check out the walkthrough in the comments below.