ReadMe MCP. Find any detail across your entire knowledge base.
ReadMe connects your AI client directly to your developer documentation hub. It turns your agent into an expert technical reader, allowing it to instantly find specific guides, API references, or changelogs without leaving the chat window. Your AI can search every page, track recent updates, and pull complex content from your entire knowledge base.
Give Claude and any AI agent real-world access
The agent performs full-text searches across every guide, reference page, and custom document.
You can fetch the complete Markdown text for any single documented page or API reference.
The agent maps out your entire knowledge base, showing all major categories and sub-guides available.
You can pull recent updates, new features, or deprecation notices directly from published changelogs.
The agent provides details on the overall organization and scope of your entire ReadMe project.
Ask an AI about this
Waiting for input…
What AI agents can do with ReadMe with 10 Tools
These tools allow your agent to perform every action necessary: searching documents, listing categories, retrieving content, and tracking project updates.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using ReadMe MCPList Categories
Lists all major organizational groups within your entire set of documentation.
Get Category
Fetches detailed information about one specific section or category of guides.
Get Category Docs
Lists every single individual documentation page that belongs to a selected guide...
Get Doc
Retrieves the full, raw content of any specific documented article or page.
Search Docs
Runs a comprehensive search across all articles and guides to find relevant...
List Changelogs
Pulls a list of the titles and dates for all published product update announcements.
Get Changelog
Retrieves the full text content for one specific, named changelog post.
List Custom Pages
Shows a list of standalone pages that exist outside the main category structure.
Get Custom Page
Retrieves the full content for any specific custom, non-categorized page.
Get Project
Gathers metadata about the overall scope and configuration of your entire...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with ReadMe, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by ReadMe. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Keeping up with documentation is a massive time drain.
Today, getting reliable technical answers requires jumping through hoops. You might search the main site, copy a snippet from an API reference guide, then open the changelog to see if that feature was updated. Then you have to manually paste all those pieces into your chat or document and ask for a summary. It's messy, slow, and highly prone to missing outdated details.
With this MCP connected through Vinkius, the process changes completely. You just talk to your agent. You ask one question—like 'What were the rate limit changes in v2?'—and the agent handles the entire workflow behind the scenes, gathering data from multiple sources and giving you a single, synthesized answer.
ReadMe MCP gives you instant access to your full documentation set.
The manual steps that vanish are the repetitive searches across different tabs. You don't need to manually pull a list of categories, then individually visit each guide to check for related information. The agent organizes it all for you.
Now, your AI client acts as an internal expert who knows every page and every update. It doesn't just point to the documentation; it reads it and answers the question.
What ReadMe MCP does for your AI
This MCP lets you connect your internal developer documentation directly to your agent. You no longer have to copy-paste snippets or switch between tabs just to find an API endpoint definition. Instead, your AI reads the source of truth—your published guides and technical specs—and answers questions using that data.
It handles everything from complex full-text searches across all categories to fetching the exact content for a specific changelog entry. You can even ask it to list all available documentation sections or analyze how different parts of your project are structured. This capability is critical because it keeps your agent grounded in your company's official information, not general web data.
By connecting this MCP via Vinkius, you ensure that any compatible AI client—whether running locally or on a cloud platform—has immediate access to the full depth and breadth of your technical knowledge.
019d75fc-ed18-7242-997a-4e24253948d1 How to set up ReadMe MCP
The bottom line is that you get reliable, real-time access to your entire technical knowledge base from a single conversation thread.
Authorize the ReadMe MCP in your environment and provide your API key.
Instruct your AI client to perform a task, like summarizing an API endpoint or listing all categories.
The agent uses the tool to read the documentation and responds with accurate, source-backed information.
Who uses ReadMe MCP
Technical Writers and Developer Advocates need this. They constantly battle context switching—jumping between their IDE, the docs site, and the chat window—to ensure accuracy. Engineers also benefit when they can instantly pull official API specs into their workflow without leaving their coding environment.
Auditing existing documentation for outdated references or finding precise content to draft new guides.
Creating accurate tutorials and quick-start guides by referencing the most up-to-date API definitions and best practices.
Quickly pulling official company API documentation into a chat or IDE to validate code against published standards.
Benefits of connecting ReadMe MCP
Instantly check product status: Instead of hunting through multiple sources, use the list_changelogs tool to see a list of all recent updates and announcements immediately.
Audit content accuracy: If you need to verify an old reference, calling get_doc lets your agent pull the full text of that specific page for review, without needing manual logins or searches.
Understand structure quickly: Use list_categories to map out your entire documentation hierarchy. Your agent reports back on all major sections available in a single response.
Write targeted content: If you need details on one topic but the guide is nested deep, use get_category_docs to list all relevant sub-pages before drafting.
ReadMe MCP use cases
The engineer needs API specs for a new feature.
Instead of searching Google or asking a colleague, the agent uses search_docs and retrieves the exact current endpoint requirements. This lets the software engineer validate their code against official standards in minutes.
The developer advocate needs to create an 'Authentication' guide.
They ask the agent to list all related documentation (get_category_docs for Authentication). The AI provides a comprehensive map, ensuring no necessary sub-guide is missed before writing begins.
The technical writer needs to summarize the latest v2 API changes.
They run list_changelogs first, identifying 'v2-api-release'. Then they use get_changelog to pull the full content, allowing them to generate a summary for internal stakeholders immediately.
The team needs to know what's in the project.
They use list_custom_pages and get_project together. The agent confirms that key standalone guides exist, providing an overview of content outside the main structured categories.
ReadMe MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Asking general questions about APIs
Asking your AI client, 'How does webhook authentication usually work?' The agent provides generic internet answers that might not match your company's specific implementation.
You must use the search_docs tool. By running a search query through this MCP, you force the agent to ground its answer using only content from your private documentation.
Copying text into the chat manually
Finding an API reference on one tab and pasting it into the chat window for summarization. This is tedious and fails if the original page changes.
Let the agent use get_doc or search_docs. You simply tell your AI client, 'Summarize the endpoint documented at X,' and it pulls the source content directly.
Assuming documentation is up-to-date
A colleague points to a guide you found last month. You assume it's current, but it contains deprecated information.
Always check list_changelogs first. This ensures your agent has access to the most recent product updates before trusting any guides.
When to use ReadMe MCP
Use this MCP if your primary need is for your AI client to answer questions, write drafts, or summarize information based only on internal, structured developer documentation (e.g., API specs, user guides, changelogs). If you are building a Retrieval-Augmented Generation (RAG) system that needs deep context from proprietary knowledge bases, this is essential. Don't use it if your goal is to perform general web research or monitor real-time external events; for those, you need generic search tools. Also, don't use this just because the answer sounds nice—always verify that the agent explicitly used a ReadMe tool call (like get_doc or search_docs) in its response.
Frequently asked questions about ReadMe MCP
How does ReadMe MCP help me find a specific API endpoint? +
You use the search_docs tool. Instead of guessing keywords, your agent performs a full-text search across all guides and returns direct links and content snippets matching the endpoint you need.
Can I list everything in my documentation? +
Yes, start by using list_categories to see the main sections. Then, use get_category_docs on any category name to get a full manifest of all related pages.
How do I know what was changed recently? +
Run the list_changelogs tool first. This gives you a list of titles and dates for all updates, helping you pinpoint exactly which version you need to read about next with get_changelog.
Does ReadMe MCP work only on guides? +
No, it's more comprehensive. Besides structured guides, you can also check standalone content by using list_custom_pages and fetching the details with get_custom_page.
What if I need to summarize a whole guide? +
You should use get_doc on the specific page you want summarized. While the tool fetches the content, your agent can then process that full text into the summary you request.