https://github.com/mnot/ietf-llm
https://github.com/mnot/ietf-llm
Last synced: about 2 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/mnot/ietf-llm
- Owner: mnot
- License: mit
- Created: 2026-03-24T04:33:23.000Z (4 months ago)
- Default Branch: main
- Last Pushed: 2026-06-05T03:08:33.000Z (about 2 months ago)
- Last Synced: 2026-06-05T03:14:31.756Z (about 2 months ago)
- Language: Python
- Homepage:
- Size: 1.45 MB
- Stars: 2
- Watchers: 1
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE.md
Awesome Lists containing this project
README
# ietf-llm
Maintain a local, queryable corpus of an [IETF](https://www.ietf.org/) Working Group's public
record — charter, drafts, RFCs, meeting agendas, minutes, slides, transcripts, mailing list
archives, and GitHub issues — for use with LLM-based tools.
## What it's for
A working group's history is spread across mailing list archives, Datatracker, GitHub, and meeting
materials — too much to hold in your head, and too scattered to search well by hand. With the record
gathered into one queryable corpus, an LLM can help you:
- **Get up to date with the state of discussions** — what's open, what was recently decided, where a
debate currently stands.
- **Summarise the arguments already made** about an issue — every distinct position on a topic, who
holds it, and how the chairs ruled.
- **Formulate a new proposal** — surface the objections raised against similar ideas before, so you
can anticipate them.
- **Fact-check assertions** about what's happened so far — grounded in the actual list traffic and
chair statements, not someone's recollection.
> ***Not just WGs***: ietf-llm also works with [IRTF](https://irtf.org/) Research Groups. Pass the
> RG's shortname (e.g. `cfrg`, `hrpc`, `pearg`) wherever the docs use ``.
## Modes of operation
There are three supported workflows:
1. **Use it as an MCP server** — register it with Claude, Codex, Cursor, Gemini, Zed,
etc. and ask questions across any corpus you've gathered. Two ways to run it:
- **[Local MCP](https://github.com/mnot/ietf-llm/blob/main/docs/mcp-local.md)** — one server subprocess per client, on your own machine. <-- **Best starting point**
- **[As a shared HTTP MCP server](https://github.com/mnot/ietf-llm/blob/main/docs/mcp-server.md)** — one process serving many concurrent
clients (hosted).
2. **[Use it with NotebookLM](https://github.com/mnot/ietf-llm/blob/main/docs/notebooklm.md)** — export the gathered corpus as a directory of
clean text files and ingest it as a notebook (or push directly to NotebookLM Enterprise).
3. **[Use it from the CLI](https://github.com/mnot/ietf-llm/blob/main/docs/search-cli.md)** — run semantic search over the cache directly with
`ietf-llm-search`, no LLM client required.
See the workflow documentation linked above for installation and use instructions, or the
[full documentation listing](https://github.com/mnot/ietf-llm/blob/main/docs/README.md).