- Add file size metadata to get_option declarations - Add range parameters to get_file with sensible defaults - New MCP server idea for indexing nixpkgs packages Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
TODO - Future Improvements
Usability
- Progress reporting during indexing ("Fetching nixpkgs... Parsing options... Indexing files...")
- Add
search_filesMCP tool - search for files by path pattern (e.g., find all nginx-related modules) - Include file size metadata in
get_optiondeclarations (byte size and/or line count) so clients know file sizes before fetching - Add range parameters to
get_file(offset,limit) with sensible defaults (~200-300 lines) to avoid dumping massive files
Robustness
- PostgreSQL integration tests with testcontainers (currently skipped without manual DB setup)
- Graceful handling of concurrent indexing (what happens if two clients index the same revision?)
New MCP Servers
nixpkgs-packages- Index and search nixpkgs packages (similar architecture to nixos-options, but for packages instead of options)
Nice to Have
- Option history/diff - compare options between two revisions ("what changed in services.nginx between 24.05 and 24.11?")
- Auto-cleanup - prune old revisions after N days or keep only N most recent
- Man page generation
- Shell completions (bash, zsh, fish)