med-lit-mcp
med-lit-mcp is an MCP server for medical literature reviews. It takes a review through four deliberate stages, search → screening → fetch → wiki, and ends with an evidence-linked wiki you can open in Obsidian.
Your MCP client's model does the reading and writing (screening decisions, entity extraction, syntheses). med-lit-mcp searches the databases (PubMed, PMC, OpenAlex, Europe PMC, Semantic Scholar, Scopus), stores everything, checks the model's work against the source text, and exports the wiki. Every screening decision, extracted mention and synthesis citation must be a verbatim quote or a reference to the stored text.
- Clients: Hermes (terminal and Desktop), Claude Code, Claude Desktop, Codex, pi and ChatGPT desktop Work/Codex.
- Platforms: Linux, macOS and Windows.
- Requirements: a contact email (
NCBI_EMAIL). No embedding endpoint, model API key or build step. - Bots: with Hermes, a scheduled bot can keep a review up to date by screening new articles and adding them to the wiki.
Install
| Client | How |
|---|---|
| Hermes, Claude Code, Codex, pi | uvx med-lit-mcp setup (needs uv); for pi see med-lit in pi |
| Claude Desktop | Install med-lit-<version>.mcpb from the latest release under Settings → Extensions, then switch it on |
| ChatGPT desktop (macOS, Windows x64) | Run med-lit-macos-<version>.dmg or Install med-lit.bat from the latest release and fill in the browser form |
Setup asks for your email, a folder for your reviews (default ~/med-lit) and optional database API keys. Keys are stored in private local files, never in the chat. See Setup for every client, manual registration and updating.
Use
Talk to your agent. It starts each stage only when you ask and confirms the search question with you first:
Start a new review on how large language models are used in shared decision making in healthcare.
Looks good, run it.
Screen it. Include studies of LLMs supporting patient–clinician decisions; exclude purely technical benchmarks.
Fetch the included articles and build the wiki.
Each review is a self-contained project folder. Open it in Obsidian with Open folder as vault.
What's new in 0.2.0
- pi support.
uvx med-lit-mcp setup --client piadds med-lit to pi'smcp.json. It writes only med-lit's own entry and leaves pi's model, sign-in and settings alone. An optional pi package (pi install git:github.com/junhewk/med-lit-mcp@v0.2.0) adds two things: the research policy in study folders, and fresh subagent workers that get only the tools their task names. See med-lit in pi. - Batches that fit the client.
- Screening, triage and wiki-task results are sized by the bytes the client actually receives (default 18 KiB,
MED_LIT_RESPONSE_BYTES), so a client that cuts long tool results (pi at 20 KiB) gets every abstract whole. - A single record too large on its own is sent with its abstract cut at a word boundary and marked.
- Screening, triage and wiki-task results are sized by the bytes the client actually receives (default 18 KiB,
- The page limit holds on every route.
next_wiki_article,get_article_pageandrecord_extractionall keep towiki.max_pages.- Changed: a per-call
max_pagescan only ask for fewer pages. To read more of an article, raise the setting withproject_settings.
- Changed: a per-call
- The rules travel with each task. The entity types, roles and evidence rules, and the duplicate and synthesis rules, are defined once. They are included in every task
wiki_taskshands out, so a subagent follows them whether or not it reads a guide.- Changed: a plan names the tools its tasks may use (
kind,tools). - Changed: a long step comes in portions (
total_tasks,remaining_tasks); callwiki_tasksagain for the rest.
- Changed: a plan names the tools its tasks may use (
These changes came from comparing hosts on a pilot review: Hermes left subagents free to read past the page limit and to start the duplicate review, and pi with a stripped-down host received the rules more reliably. With 0.2.0 the backend enforces the limit and every task carries its rules, and the two hosts reached the same results.
Documentation
| Topic | |
|---|---|
| Setup | Installing for each client, manual registration, updating |
| Configuration | Email, keys and environment variables; per-review settings and defaults |
| Running a review | Projects, how search, screening, fetch and wiki work, tools, the viewer |
| med-lit in pi | Registration, the optional pi package (research policy, scoped workers), recommended settings |
| Bots | Keeping a review up to date with Hermes scheduled jobs |
| The wiki | Obsidian, entity types, roles and relationships, Simple Graph Builder |
| Ontology | The full knowledge-graph contract and graph export format |
| Development | Running from a checkout, tests, compatibility |
| Installation and release | Building and signing the installers |
| Validation | Platform and installer test records |
License
med-lit-mcp is licensed under the PolyForm Noncommercial License 1.0.0. You may use, modify and share it for any noncommercial purpose, including research, teaching, and use by educational institutions, public research organizations and public health organizations. Commercial use needs a separate license; open an issue to ask. NOTICE records the MIT-licensed origin of the search engine.
Metadata
Release files for med-lit-mcp 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| med_lit_mcp-0.2.0.tar.gz | 299.6 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| med_lit_mcp-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 472.8 kB
Release files / med_lit_mcp-0.2.0.tar.gz
| Download URL | med_lit_mcp-0.2.0.tar.gz |
|---|---|
| Size | 299.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6ce498b9703b00b6d931f7d2a360bab8bdf74d88f29f6f9a7ffc5ee82007f6cb
|
|
BLAKE2b-256 checksum How to use checksums |
377eb8baf222d10da265d488217d5de6556ac64c6529ffb9329268447d4fd50c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logRelease files / med_lit_mcp-0.2.0-py3-none-any.whl
| Download URL | med_lit_mcp-0.2.0-py3-none-any.whl |
|---|---|
| Size | 173.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
35899d3cf496e1240382653475601a70fa62fff42cd191d188a3a17d5e861613
|
|
BLAKE2b-256 checksum How to use checksums |
0bb8992931d7193334dc5871f336e7cfed7d5422319b033e5657f107b39725aa
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logSecurity for med-lit-mcp 0.2.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for med_lit_mcp-0.2.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 20, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.