rtfm-mcp 0.8.0__py3-none-any.whl
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -0,0 +1,122 @@
|
|
|
1
|
+
Metadata-Version: 2.5
|
|
2
|
+
Name: rtfm-mcp
|
|
3
|
+
Version: 0.8.0
|
|
4
|
+
Summary: Read The Full Manual — local document-corpus search MCP server.
|
|
5
|
+
Project-URL: Homepage, https://github.com/canlin-zhang/rtfm
|
|
6
|
+
Project-URL: Repository, https://github.com/canlin-zhang/rtfm
|
|
7
|
+
Project-URL: Issues, https://github.com/canlin-zhang/rtfm/issues
|
|
8
|
+
Author: Canlin Zhang
|
|
9
|
+
License-Expression: MIT
|
|
10
|
+
License-File: LICENSE
|
|
11
|
+
Keywords: documentation,mcp,pdf,search
|
|
12
|
+
Classifier: Development Status :: 4 - Beta
|
|
13
|
+
Classifier: Programming Language :: Python :: 3
|
|
14
|
+
Classifier: Programming Language :: Python :: 3 :: Only
|
|
15
|
+
Requires-Python: >=3.11
|
|
16
|
+
Requires-Dist: mcp[cli]<2,>=1.28.1
|
|
17
|
+
Requires-Dist: pymupdf
|
|
18
|
+
Requires-Dist: pypdf
|
|
19
|
+
Description-Content-Type: text/markdown
|
|
20
|
+
|
|
21
|
+
# rtfm
|
|
22
|
+
|
|
23
|
+
> **rtfm** — Read the ~~F-~~ **Full** Manual.
|
|
24
|
+
|
|
25
|
+
A local MCP server and Claude Code plugin that makes large, can't-read-by-hand technical
|
|
26
|
+
documentation searchable — PDF spec sets, documentation repositories (and, later, public
|
|
27
|
+
doc sites) — and answers questions strictly from that material, with grounded citations.
|
|
28
|
+
The server is also published as the `rtfm-mcp` Python package.
|
|
29
|
+
|
|
30
|
+
The eternal advice "read the manual" falls apart when the manual is a 400-page protocol
|
|
31
|
+
spec or a vendor doc-set no human can hold in their head. `rtfm` ingests the **full** manual
|
|
32
|
+
so the answer is one cited query away.
|
|
33
|
+
|
|
34
|
+
## Limitations
|
|
35
|
+
|
|
36
|
+
`rtfm` indexes the **extractable text** a document already carries. It does not OCR images
|
|
37
|
+
and does not execute JavaScript, so image-only/scanned PDFs and image-only or JS-rendered
|
|
38
|
+
web pages are out of scope — they index as empty. (See [ADR 0005](https://github.com/canlin-zhang/rtfm/blob/main/docs/adr/0005-text-extraction-only-no-ocr.md).)
|
|
39
|
+
|
|
40
|
+
## Install
|
|
41
|
+
|
|
42
|
+
### Claude Code
|
|
43
|
+
|
|
44
|
+
```bash
|
|
45
|
+
# in Claude Code:
|
|
46
|
+
/plugin marketplace add canlin-zhang/rtfm
|
|
47
|
+
/plugin install rtfm
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
### Any MCP client (PyPI)
|
|
51
|
+
|
|
52
|
+
The server is also published as `rtfm-mcp`:
|
|
53
|
+
|
|
54
|
+
```bash
|
|
55
|
+
uvx --from rtfm-mcp rtfm-server # or: pipx install rtfm-mcp && rtfm-server
|
|
56
|
+
```
|
|
57
|
+
|
|
58
|
+
Point the client's MCP configuration at that command:
|
|
59
|
+
|
|
60
|
+
```json
|
|
61
|
+
{
|
|
62
|
+
"mcpServers": {
|
|
63
|
+
"rtfm": {
|
|
64
|
+
"command": "uvx",
|
|
65
|
+
"args": ["--from", "rtfm-mcp", "rtfm-server"]
|
|
66
|
+
}
|
|
67
|
+
}
|
|
68
|
+
}
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
**Prerequisites:** `python3` on PATH is the only hard requirement for the plugin. It
|
|
72
|
+
uses `uv` when available and otherwise builds a private venv under `~/.rtfm/venv` on
|
|
73
|
+
first run. The PyPI path needs `uv` (for `uvx`) or `pipx`.
|
|
74
|
+
*Optional:* install `poppler-utils` (`pdftotext`) for best-quality PDF extraction.
|
|
75
|
+
|
|
76
|
+
## Two ways to use it
|
|
77
|
+
|
|
78
|
+
**Quick-and-dirty (the `default` drop-dir).** Drop PDFs or Markdown/text into `~/.rtfm/default`
|
|
79
|
+
and just `search` — the default dir re-indexes itself on search, so dropped files show up with
|
|
80
|
+
no extra step. Keep it small; it's a scratch space.
|
|
81
|
+
|
|
82
|
+
**Organized corpus (pointed-to folders).** For a large, structured doc set (e.g. a vendor's
|
|
83
|
+
documentation tree), add a `dir` source in `~/.rtfm/manifest.toml` pointing at the folder, then
|
|
84
|
+
build it once:
|
|
85
|
+
|
|
86
|
+
```
|
|
87
|
+
reindex("vendor-docs")
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
Searches are instant afterward. `dir` sources auto-reindex inline when the delta is small
|
|
91
|
+
(`RTFM_AUTO_REINDEX_MAX`, default 10); a larger delta returns a warning telling you to run
|
|
92
|
+
`reindex` once. `git_repo` sources are the exception to the budget: a stale or never-indexed
|
|
93
|
+
source always auto-reindexes inline on search — no budget gate, warns loudly on failure —
|
|
94
|
+
including the initial clone for managed sources, so the first search over a fresh corpus can
|
|
95
|
+
take a while. Byte-identical files that repeat across version subfolders are extracted once;
|
|
96
|
+
`find_duplicates` lists every path a given content lives at.
|
|
97
|
+
|
|
98
|
+
## Use
|
|
99
|
+
|
|
100
|
+
Drop PDFs / `.md` / `.mdx` / `.rst` / `.txt` into `~/.rtfm/default/`, then ask Claude to search them, or
|
|
101
|
+
add more sources by editing `~/.rtfm/manifest.toml` (see `manifest.example.toml`).
|
|
102
|
+
|
|
103
|
+
Or invoke the bundled **`read-the-manual`** skill (`/read-the-manual`) to have a question
|
|
104
|
+
answered strictly from the corpus — verbatim quotes with page/line citations, no
|
|
105
|
+
model-knowledge fallback.
|
|
106
|
+
|
|
107
|
+
## Status
|
|
108
|
+
|
|
109
|
+
Early but working. Today rtfm gives you zero-config search over a default drop-folder: PDF,
|
|
110
|
+
Markdown, reStructuredText, and text files are indexed into one content-addressed full-text
|
|
111
|
+
index with page/line citations, exposed through the `search` / `read` / `reindex` /
|
|
112
|
+
`find_duplicates` / `list_sources` / `health_check` tools and the `read-the-manual` skill, with
|
|
113
|
+
a uv-or-venv launcher and Claude Code plugin packaging. HTML with anchor citations, git-backed
|
|
114
|
+
repo sources with auto-refresh, file-curation tools, and OCR are planned — see the
|
|
115
|
+
[roadmap](https://github.com/canlin-zhang/rtfm/blob/main/docs/ROADMAP.md).
|
|
116
|
+
|
|
117
|
+
Architecture decisions live in [docs/adr/](https://github.com/canlin-zhang/rtfm/tree/main/docs/adr/); domain language in
|
|
118
|
+
[CONTEXT.md](https://github.com/canlin-zhang/rtfm/blob/main/CONTEXT.md).
|
|
119
|
+
|
|
120
|
+
## License
|
|
121
|
+
|
|
122
|
+
MIT © Canlin Zhang
|
|
@@ -0,0 +1,6 @@
|
|
|
1
|
+
rtfm_server.py,sha256=Ha-yKmReSrTg4sZH7MR-qBX17O6hWUNW4S_hWxgpqdY,103420
|
|
2
|
+
rtfm_mcp-0.8.0.dist-info/METADATA,sha256=KKpl_i49c5GbfrGhipd7V4jZnjSa5I9VO39opDg1ef8,4852
|
|
3
|
+
rtfm_mcp-0.8.0.dist-info/WHEEL,sha256=W3fkpkm7-wf9vBI5Z-7s0eWkeM-spu78I8Neb98DeEg,87
|
|
4
|
+
rtfm_mcp-0.8.0.dist-info/entry_points.txt,sha256=_zP_z1z0ZmzGDkUbamncYMo6bj2dRy4oyKdOTe7qF4A,49
|
|
5
|
+
rtfm_mcp-0.8.0.dist-info/licenses/LICENSE,sha256=jJN24YU8u1-uJ-AslZpH46v8hLLc0co2Y7jNg4FM588,1069
|
|
6
|
+
rtfm_mcp-0.8.0.dist-info/RECORD,,
|
|
@@ -0,0 +1,21 @@
|
|
|
1
|
+
MIT License
|
|
2
|
+
|
|
3
|
+
Copyright (c) 2026 Canlin Zhang
|
|
4
|
+
|
|
5
|
+
Permission is hereby granted, free of charge, to any person obtaining a copy
|
|
6
|
+
of this software and associated documentation files (the "Software"), to deal
|
|
7
|
+
in the Software without restriction, including without limitation the rights
|
|
8
|
+
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
|
|
9
|
+
copies of the Software, and to permit persons to whom the Software is
|
|
10
|
+
furnished to do so, subject to the following conditions:
|
|
11
|
+
|
|
12
|
+
The above copyright notice and this permission notice shall be included in all
|
|
13
|
+
copies or substantial portions of the Software.
|
|
14
|
+
|
|
15
|
+
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
|
|
16
|
+
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
|
|
17
|
+
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
|
|
18
|
+
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
|
|
19
|
+
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
|
|
20
|
+
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
|
|
21
|
+
SOFTWARE.
|