RTFM
Related Servers
Alternatives to RTFM
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceProvides intelligent code indexing with 15 MCP tools for symbol extraction, hybrid search (FTS5+vector), call graphs, and incremental indexing of local folders and remote repos, enabling token-efficient code retrieval for AI agents.3MIT
- FlicenseAqualityDmaintenanceA local-first document retrieval engine that mounts as an MCP tool for agents to index files, search for relevant passages, and let the agent's own LLM answer.4-
- AlicenseAqualityAmaintenanceLocal-first RAG MCP server that indexes local documents and provides hybrid search (semantic + keyword) with file ingestion, URL fetching, and a CLI, keeping data on-device.1167MIT
- AlicenseNot gradedqualityBmaintenanceTurns any folder of PDFs, markdown, and text files into a local, queryable knowledge base exposed as an MCP server. Enables MCP-compatible agents to semantically search indexed documents, retrieve relevant passages with source and relevance scores, list or reindex documents, and inspect cache and token usage — instead of reading whole files into context.1MIT
- AlicenseCqualityAmaintenanceLocal-first MCP server that turns project documentation and source code into durable, evidence-backed context for AI agents, with bounded retrieval and explicit gap reporting.81,003 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceLocal-first documentation for AI agents1,428 npm412Apache 2.0
TDQS
Scored across 8 tools
Most tools are clearly distinct, but rtfm_search and rtfm_context both accept a subject and return paths plus line ranges with no content, making their boundaries unclear. The descriptions do not offer a crisp rule for choosing between them, though the other six tools are easy to tell apart.
All tools share the rtfm_ prefix and use snake_case, which is good, but the pattern mixes verbs (search, discover, expand) with bare resource nouns (books, coverage, context, graph, history). A consistent verb_noun convention like rtfm_list_books or rtfm_get_coverage would be more predictable.
Eight tools is a well-scoped size for a knowledge-base/index server: enough to cover search, context, reading, exploration, coverage, history, and project discovery without feeling bloated. Each tool has a reasonable place in the workflow even if search and context could potentially be consolidated.
The server covers the core read-only workflows well: finding sources, reading content, exploring relationships, checking coverage, and viewing history. Minor gaps exist around explicit index management and book-specific operations, but most agent tasks involving querying an indexed codebase can be completed without dead ends.