ReadMe

New @readme homepage! readme [.] com

ReadMe CLI — Write and lint docs from your terminal. Catches broken links, duplicate slugs, invalid frontmatter, and broken MDX. Auto-fixes most issues, and works with Claude or Codex for the rest. Write from ReadMe's editor, your IDE, or the CLI. Your customers just see great docs. Learn about the ReadMe CLI: readme.com/blog/cli

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

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

We’re shipping something big tomorrow. Here’s a little hint 👀

You're all still repping last year's swag and we love it 💙 Great seeing everyone at @writethedocs. This year's batch is coming off the printer hot!

We’re at @writethedocs in Portland this week so swing by to say hi, grab a custom engraved notebook, collect a few pins and a tote bag! 🦉

Learn more about it in our docs: docs.readme.com/main/docs/AskAI

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!

Your API Reference now supports CSV and plain text request body examples. Full coverage for application/json, application/x-www-url-formencoded, text/csv, application/csv, and text/plain. One of our most requested features, now live. 🚀

ReadMe's Agent just got a major upgrade. Agent multi-page edits is now live. Instead of editing one page at a time, the agent can now make changes across your entire docs at once. Try it with one of these prompts: - Replace all instances of 'whitelist' and 'blacklist' with 'allowlist' and 'blocklist' - Find every page missing a code example and list them by section - Replace all instances of [Old Brand] with [New Brand] across the docs Big refactors just got a lot faster.

Try updating your docs with ReadMe's MCP Server: docs.readme.com/main/docs/read…

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.

🤔 readme.com/ai

Cluttered sidebar? We fixed that. Enable Collapsible Categories to tuck away subpages and only surface them when your customers actually need them. Here's how to do it: Admin Settings → Page Navigation → Collapsible Categories ✅ Instant before-and-after. ✨

Read the full blog post: readme.com/blog/api-docum… Learn how to generate your own MCP server: docs.readme.com/main/docs/gene…

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.