ietf-llm 0.17.0

Maintain a local, LLM-queryable corpus of an IETF Working Group's public record (drafts, mailing list, GitHub issues, meetings), with an MCP server, semantic search, and NotebookLM export.

ietf-llm

Maintain a local, queryable corpus of an IETF effort's public record — a Working Group, an IRTF Research Group, a mailing list, or a set of drafts. It pulls together charter, drafts, RFCs, meeting agendas, minutes, slides, transcripts, attendance, 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.

Tip: for an IRTF Research Group, pass its shortname (e.g. cfrg, hrpc, pearg) wherever the docs use <name> — it works the same as a WG.

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 — one server subprocess per client, on your own machine. <-- Best starting point
   • As a shared HTTP MCP server — one process serving many concurrent clients (hosted).
2. Use it from the CLI — 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.

All three read a corpus you first gather with ietf-llm <corpus>. By default a gather of a corpus covered by the public seed store starts from a prebuilt snapshot and only freshens the delta — skipping most of the embedding and download cost. It is opt-out (--no-seed, or IETF_LLM_SEED_URL=off) and best-effort: an unreachable or unlisted corpus just gathers from scratch.