literature-review-toolslisted

Recommend AND run open-source AI tools, agents, Claude Code / Codex skills, and MCP servers for any stage of a literature review — searching, reading, extracting, synthesizing, screening, citation-checking, and paper writing. Use when the user asks "what tool should I use to..." OR "install/run/use <tool> to ..." for research/lit-review work: automating a survey or related-work section, PDF→Markdown extraction for LLMs (MinerU/marker/docling), PRISMA / systematic review (ASReview), citation-backed Q&A over PDFs (PaperQA2), wiring papers into Claude/Cursor via MCP (arxiv/paper-search/zotero servers), or chatting with a Zotero library. Ships a launcher (scripts/litrun.py) that installs each tool in an isolated venv and runs it. Curated catalog of 70+ vetted projects. 支持中英文（用于「文献综述工具选型」与「一键安装/运行」）。
brycewang-stanford/lit-review-agent-tools · ★ 4 · AI & Automation · score 74

Install: claude install-skill brycewang-stanford/lit-review-agent-tools

# Literature Review Tools — Select & Run A curated, use-case-organized catalog of the strongest **open-source** AI tools for literature review — **plus a launcher that actually installs and runs the top ones.** Covers: end-to-end research agents, deep-research / auto-survey generators, autonomous "idea→paper" systems, citation-backed RAG over PDFs, PRISMA screening, MCP servers, Zotero/Obsidian integrations, PDF→structured extraction, citation graphs, and paper-writing / peer-review assistants. Full source of truth (README, always current star counts): <https://github.com/brycewang-stanford/lit-review-agent-tools> ## Two modes - **Recommend** — user asks "what should I use to …". Route with the tables below; cite the catalog for details. - **Run** — user asks to *install / run / use* a specific tool ("turn this PDF into Markdown with MinerU", "ask PaperQA2 about these papers", "set up the arXiv MCP server"). Drive [`scripts/litrun.py`](scripts/litrun.py) via Bash — do not hand the user raw pip commands to copy. ## Run mode — how to drive `scripts/litrun.py` The launcher installs each supported tool into its own venv under `~/.lit-review-tools/` (uses `uv` if present, else `python -m venv`) and reads API keys from one shared `~/.lit-review-tools/.env`. Machine-readable recipes: [`recipes/recipes.json`](recipes/recipes.json). Typical flow when the user wants to *use* a tool: 1. `python3 scripts/litrun.py doctor` — check toolchain + which API keys are already set. 2. `py