Rtfmbro▌

by marckrenn
Rtfmbro is an MCP server for config management tools—get real-time, version-specific docs from GitHub for Python, Node.j
Stay ahead with instantly up-to-date, version-specific docs for any package. rtfmbro is an MCP server that delivers precise, real-time documentation from GitHub at the exact version your project uses. It supports popular ecosystems like Python and Node.js, features smart caching, full context extraction, and tight integration with coding agents. AI assistants can access READMEs, documentation trees, and search repositories, ensuring coding help is always accurate and current. Perfect for developers or AI tools needing the right docs, right when you need them—without stale data or version mismatches.
github stars
★ 77
best for
- / AI coding assistants needing current package docs
- / Developers working with legacy or specific package versions
- / Teams maintaining projects with pinned dependencies
capabilities
- / Download README files for specific package versions
- / Browse documentation folder structures
- / Read multiple documentation files at once
- / Search GitHub repositories for packages
what it does
Fetches exact version-specific documentation for packages directly from GitHub repositories. Ensures AI assistants and developers get accurate, up-to-date docs that match the exact package versions being used.
about
Rtfmbro is an official MCP server published by marckrenn that provides AI assistants with tools and capabilities via the Model Context Protocol. Rtfmbro is an MCP server for config management tools—get real-time, version-specific docs from GitHub for Python, Node.j It is categorized under developer tools. This server exposes 4 tools that AI clients can invoke during conversations and coding sessions.
how to install
You can install Rtfmbro in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server supports remote connections over HTTP, so no local installation is required.
license
MIT
Rtfmbro is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
rtfmbro-mcp
rtfmbro provides always-up-to-date, version-specific package documentation as context for coding agents. An alternative to context7.
https://github.com/user-attachments/assets/dbe0b3b4-a42c-4e91-8bcd-a94d430ef0b8
Demonstration of rtfmbro in use, fetching a specific version (3.1.1) of Flask's readme and docs.
Overview
rtfmbro is a Model Context Protocol (MCP) server that provides real-time, version-aware documentation fetching for packages across multiple ecosystems. It bridges the gap between AI agents and accurate, up-to-date package documentation by fetching docs directly from GitHub repositories at the exact version your project uses.
Supported Ecosystems
| Ecosystem | Registry | Status |
|---|---|---|
| Python | PyPI | ✅ Full Support |
| Node.js | npm | ✅ Full Support |
| Swift | SPM | 🚧 Alpha |
| GitHub | Direct | ⚠️ Fallback |
Why rtfmbro?
The Problem
- Stale Documentation: AI models often rely on outdated training data about packages
- Missing Context: Source code in
node_modulesetc. lacks high-level documentation, browsing it is usually token-consuming and inefficient - Version Mismatches: Generic documentation doesn't match your specific package version, especially for legacy projects or brand new packages
The Solution
rtfmbro tries to solve these issues by:
- Version-Precise Fetching: Retrieves documentation from the exact git tag/commit that matches your lockfile
- Comprehensive Coverage: Extracts all documentation files (
.md,.mdx,.txt,.rst,.html) from the repository - Intelligent Caching: SHA-based currency checking ensures docs stay fresh without unnecessary re-fetching
- Agent Integration: Seamlessly integrates with AI coding assistants via the Model Context Protocol
- Great DX: Zero seting up for developers, just add the server to your MCP configuration, instructions and start fetching docs
MCP Tools
The server exposes four primary tools to AI agents:
| Tool | Purpose | Parameters | Returns |
|---|---|---|---|
get_readme | Fetches and returns the README file for a specific package version | package, version, ecosystem | README content as string |
get_documentation_tree | Generates a comprehensive folder structure of all documentation files | package, version, ecosystem | Tree structure as string |
read_files | Reads specific documentation files with optional line range slicing | package, version, ecosystem, requests[] | Dictionary mapping paths to content |
search_github_repositories | Searches for GitHub repositories using the GitHub Search API | query, sort, order, per_page | Formatted repository search results |
Installation & Setup
Quick Start
Claude Code
claude mcp add-json rtfmbro '{ "type": "http", "url": "https://rtfmbro.smolosoft.dev/mcp/" }'
Claude Desktop / VS Code / etc.
Add the remote server to your MCP configuration:
{
"rtfmbro": {
"type": "http",
"url": "https://rtfmbro.smolosoft.dev/mcp/"
}
}
Cursor
Agent Integration
To truly integrate rtfmbro with your AI coding agent of choice, copy the appropriate meta-instruction file to your project:
- GitHub Copilot: Copy
.github/copilot-instructions.mdto your project - Claude Code: Copy
CLAUDE.mdto your project root - Cursor: Copy
.cursor/rulesto your project root - Other agents: Adapt the instructions from either file above to your agent's format
How It Works
Documentation Workflow
- Registry Lookup: Queries the package registry (PyPI, npm, etc.) for metadata
- GitHub Discovery: Extracts the GitHub repository URL from package metadata
- Version Resolution: Fetches available git tags and matches them against your semantic version
- Smart Fetching: Clones the repository at the exact matched tag/commit
- Content Filtering: Extracts only documentation files, removing source code and build artifacts
- Caching & Currency: Stores results with SHA-based currency checking for efficient re-access
Caching Strategy
- SHA-Based Validation: Compares current repository commit SHA with cached version
- Automatic Invalidation: Re-fetches documentation when new commits are detected
- Persistent Storage: Maintains local cache to avoid redundant GitHub API calls
- Metadata Preservation: Stores documentation tree structure for fast browsing
Prerequisites
- Package must be published to a supported registry (PyPI, npm)
- Package metadata must contain a valid GitHub repository link
- Repository must use git tags for version management
- Documentation files must be present in the repository (not just generated sites)
Roadmap
Near Term
- Ecosystem independent fallback: Implement a fallback mechanism for unsupported ecosystems
- Provide rtfmbro source code: Open source the server codebase
- Public docker image: Create a public Docker image for easy deployment
- Private repo support: Allow authenticated access to private repositories
- Add Tests: Implement unit and integration tests for core functionality
- Enhanced Python Support: Include pydocs and docstring extraction
- Search Capabilities: Search across documentation corpus
Future Ecosystems / Languages / Registries
- Rust (crates.io)
- Go (pkg.go.dev)
- Java/Kotlin (Maven Central)
- C#/.NET (NuGet)
- Ruby (RubyGems)
Source code hosting and repository support:
- GitHub: Support for GitHub repositories
- Gitlab: Support for GitLab repositories
- Bitbucket: Support for Bitbucket repositories
- Launchpad: Support for Launchpad repositories
Known Issues
- Some packages may have documentation in separate standalone repos
- Large repositories may take a bit of time to clone and process initially
Similar / Additive Projects
- mcp-package-docs: Another MCP server for package documentation, focusing on documentation extraction, LSP servers, etc. May be a great supplement to rtfmbro.
- rust-docs-mcp-server: MCP server for Rust documentation, focused on Rust-specific features and documentation formats.
- mcp-ragdocs: MCP server for RAG (Retrieval-Augmented Generation) documentation, aimed at improving the documentation experience for AI models.
- godoc-mcp: MCP server for Go documentation, providing access to Go package documentation via the Model Context Protocol.
- context7: Alternative to rtfmbro
Differences between context7 and rtfmbro
| Aspect | context7 | rtfmbro |
|---|---|---|
| Actuality | Scrapes documentation ahead-of-time at intransparent intervals or upon user trigger. As of writing, the "latest" Next.js docs are already 2 days old. | Fetches documentation just-in-time, ensuring it's always up-to-date. |
| Version-specific docs | Theoretically allows scraping older versions (useful for legacy or longtime projects), but the process is complicated, limiting practical availability effectively to latest versions. | Fetches older documentation just-in-time, and always remains current, identical to latest docs. |
| Search strategy | Uses either A) optionally token-limited RAG search to filter/preprocess docs which can be hit-or-miss, or B) dumps all content into LLM's context, resulting in excessive token-use. | Employs agentic discovery (as used by Claude Code itself) |
| Developer Experience | Requires explicitly mention of context7 in every prompt. | Operates via defined rules/instructions, auto-selecting appropriate package name/version from lock file ("set and forget"). |
| Support | Language/ecosystem independent. | Currently language/ecosystem-specific; planned additional languages/ecosystems and language-independent fallback mechanism soon. |
FAQ
- What is the Rtfmbro MCP server?
- Rtfmbro is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for Rtfmbro?
- This profile displays 10 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Ratings
4.5★★★★★10 reviews- ★★★★★Shikha Mishra· Oct 10, 2024
Rtfmbro is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Piyush G· Sep 9, 2024
We evaluated Rtfmbro against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Chaitanya Patil· Aug 8, 2024
Useful MCP listing: Rtfmbro is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Sakshi Patil· Jul 7, 2024
Rtfmbro reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
- ★★★★★Ganesh Mohane· Jun 6, 2024
I recommend Rtfmbro for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Oshnikdeep· May 5, 2024
Strong directory entry: Rtfmbro surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Dhruvi Jain· Apr 4, 2024
Rtfmbro has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Rahul Santra· Mar 3, 2024
According to our notes, Rtfmbro benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Pratham Ware· Feb 2, 2024
We wired Rtfmbro into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
- ★★★★★Yash Thakker· Jan 1, 2024
Rtfmbro is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.