ReadMe

2.5K posts

ReadMe banner
ReadMe

ReadMe

@readme

Turn documentation into adoption. Build interactive docs that onboard users, scale with your product, and work for AI agents.

SF / Remote Katılım Eylül 2013
67 Takip Edilen2.5K Takipçiler
ReadMe
ReadMe@readme·
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.
English
1
0
1
103
ReadMe
ReadMe@readme·
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. ✨
English
0
0
1
211
ReadMe
ReadMe@readme·
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.
ReadMe tweet media
English
3
0
2
186
ReadMe
ReadMe@readme·
We helped @SocureID turn their docs into a developer experience. The numbers say it all. - 30% faster developer onboarding - 60% drop in support queries - 2.5x more doc engagement - Full ROI in under 4 months Check out the full story in the comments.
ReadMe tweet media
English
1
1
4
186.3K
ReadMe
ReadMe@readme·
What if your documentation was a competitive moat? We partnered with @SocureID to find out, and the results speak for themselves. ✅ 30% faster developer onboarding ✅ 60% drop in support queries ✅ 2.5x more doc engagement ✅ Full ROI in under 4 months Docs are often a developer's first touchpoint. Treat them like a product.
ReadMe tweet media
English
1
0
0
227
ReadMe
ReadMe@readme·
What if your documentation could do more than explain things? MCP servers make that possible, letting AI assistants use your docs to execute real API calls, not just reference them. Join us tomorrow, Feb 18 at 11AM PT for office hours to see it in action: → Generate an MCP server from ReadMe → Define custom tools → Control endpoint access → Let AI assistants execute real API calls from your docs Link to register in the comments 👇
English
1
0
0
84
ReadMe
ReadMe@readme·
Branches sync both ways between GitHub and ReadMe. Review diffs, merge from either side, and nothing publishes until you're ready. Let teams contribute to docs from wherever they want. Learn more about ReadMe's branches: docs.readme.com/main/docs/bran…
ReadMe tweet media
English
0
0
0
53
ReadMe
ReadMe@readme·
Bi-directional sync with GitHub or GitLab is expected at this point. What isn't: a branching workflow that actually fits how your teams work.
English
1
0
0
88
ReadMe
ReadMe@readme·
MCP servers turn your documentation into something AI assistants can actually build with, not just read. Join our AI Engineer, Anand Patel, for office hours on Feb 18 at 11AM PT to learn how to generate MCP servers from ReadMe, define custom tools, control endpoint access, and let AI execute real API calls. Register at the link in comments.
English
2
2
11
203.8K
ReadMe
ReadMe@readme·
@betocmn @cjc @gkoberger We'd love to send you a copy, Beto! 🦉 Just DM us and we'll get one on its way.
English
0
0
0
43
ReadMe
ReadMe@readme·
The gap: AI knows your endpoints but not your workflows. ReadMe's solution: MCP custom tools. Define plain-language functions for: → Validation checks → Auth reminders → Multi-step sequences AI assistants invoke them automatically when developers need them. Generate your MCP server today to write your own custom tools!
GIF
English
1
0
1
300