Literature Review Council runs on your own machine — the client starts it, so there is no endpoint to ping. 54 installs a week from pypi. Last commit 23 Jun 2026.
Multi-agent literature review: research, peer review, and synthesize grounded reports.
What the code does
We read the source, 4 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
topic_path = os.path.join(output_dir, f"{slug}.md")
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add lit-review-council -e 'OPENROUTER_API_KEY=<OPENROUTER_API_KEY>' -e 'GITHUB_TOKEN=<GITHUB_TOKEN>' -e 'TAVILY_API_KEY=<TAVILY_API_KEY>' -- uvx lit-review-council{
"mcpServers": {
"lit-review-council": {
"command": "uvx",
"args": [
"lit-review-council"
],
"env": {
"GITHUB_TOKEN": "<GITHUB_TOKEN>",
"OPENROUTER_API_KEY": "<OPENROUTER_API_KEY>",
"TAVILY_API_KEY": "<TAVILY_API_KEY>"
}
}
}
}[mcp_servers.lit-review-council]
command = "uvx"
args = ["lit-review-council"]
env = { OPENROUTER_API_KEY = "<OPENROUTER_API_KEY>", GITHUB_TOKEN = "<GITHUB_TOKEN>", TAVILY_API_KEY = "<TAVILY_API_KEY>" }{
"mcpServers": {
"lit-review-council": {
"command": "uvx",
"args": [
"lit-review-council"
],
"env": {
"GITHUB_TOKEN": "<GITHUB_TOKEN>",
"OPENROUTER_API_KEY": "<OPENROUTER_API_KEY>",
"TAVILY_API_KEY": "<TAVILY_API_KEY>"
}
}
}
}{
"servers": {
"lit-review-council": {
"type": "stdio",
"command": "uvx",
"args": [
"lit-review-council"
],
"env": {
"GITHUB_TOKEN": "<GITHUB_TOKEN>",
"OPENROUTER_API_KEY": "<OPENROUTER_API_KEY>",
"TAVILY_API_KEY": "<TAVILY_API_KEY>"
}
}
}
}Put your own values in place of
<OPENROUTER_API_KEY> (OpenRouter API key for LLM access), <GITHUB_TOKEN> (GitHub personal access token for practitioner track searches), <TAVILY_API_KEY> (Tavily API key for web search).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
OPENALEX_API_KEY (OpenAlex API key for academic search), ENG_MODEL (Model for engineer agents (default: openrouter/moonshotai/kimi-k2.6)), RESEARCH_MODEL (Model for research agents (default: openrouter/z-ai/glm-5.1)), JUDGE_MODEL (Model for reviewer/synthesis agents (default: openrouter/deepseek/deepseek-v4-pro)).
Alternatives to Literature Review Council
same job, measured the same wayMCP connector for Liftaven SEO research, connected search reports and reviewed website proposals.
Site growth from your agent: GA4, Search Console, PageSpeed, SEO research and weekly reports.
Deep Research MCP for multi-round investigations, traceable evidence, and cited reports.
Synthetic persona research and world simulations, with previewed credits and report files
Run the Grok Build CLI as MCP tools: agent runs with live progress, code review, web research.
Use saved Instagram reports in AI assistants; compare evidence and prepare owner-reviewed research.
Multi-LLM AI Research & Analysis — smart routing, consensus analysis, due diligence reports
I do everything related to research and reports
Literature Review Council — questions
Answers built from our own checks of this server.