Rtfmbro MCP Server

rtfmbro provides always-up-to-date, version-specific package documentation as context for coding agents. An alternative to context7

Local serverstdioPython

What is the Rtfmbro MCP server?

Connect Rtfmbro to Claude, Cursor or any other MCP client and it stops being a tab you switch to. rtfmbro provides always-up-to-date, version-specific package documentation as context for coding agents. An alternative to context7. The rtfmbro mcp server is what makes that connection.

What the server does

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.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • get_readme — Fetches and returns the README file for a specific package version
  • get_documentation_tree — Generates a comprehensive folder structure of all documentation files
  • read_files — Reads specific documentation files with optional line range slicing
  • search_github_repositories — Searches for GitHub repositories using the GitHub Search API
  • Cursor — The Cursor tool exposed by this server

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Credentials and setup notes

  • 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)

Where it fits

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Rtfmbro's toolset — get_readme, get_documentation_tree, read_files and 2 more — is a fair guide to whether it matches your workflow. It is maintained by marckrenn; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Rtfmbro's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
get_readmeFetches and returns the README file for a specific package version
get_documentation_treeGenerates a comprehensive folder structure of all documentation files
read_filesReads specific documentation files with optional line range slicing
search_github_repositoriesSearches for GitHub repositories using the GitHub Search API
CursorThe Cursor tool exposed by this server.

Configuration

  • 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)

Example prompts to try

  • Use Rtfmbro to get readme.
  • Use Rtfmbro to get documentation tree.
  • Use Rtfmbro to read files.

Frequently asked questions

Python (PyPI) and Node.js (npm) have full support; Swift (SPM) is in alpha. A GitHub fallback is also available.