Overview
OpenEvidence MCP is an unofficial Model Context Protocol server that connects OpenEvidence via your own browser session. It supports local auth status checks, history retrieval, article fetch by ID, and question execution with completion polling.
What Is OpenEvidence?
OpenEvidence is a clinical evidence assistant used by physicians to quickly review literature-backed answers. This repository provides the MCP bridge so your AI workflow can query OpenEvidence from one place.
Tool Surface
oe_auth_status- Validate account session through
/api/auth/me. oe_history_list- Read previous conversations through
/api/article/list. oe_article_get- Fetch full article payload by article ID.
oe_ask- Create a new question and optionally wait for completion.
When Doctors Use It
- Differential diagnosis follow-ups with source-backed context
- Treatment option comparisons and quick evidence checks
- Long case threads where history and follow-up continuity matter
- Clinical knowledge workflows shared across team AI tools
Install Targets & MCP Clients
- macOS
- Windows
- Ubuntu / Linux
- Codex CLI / Claude Desktop / Claude Code / OpenClaw / Cursor / Cline / Continue
SEO / GEO / Parser Readiness
- Static semantic HTML, no JS framework dependency
- Canonical URL + OpenGraph + JSON-LD metadata
robots.txtandsitemap.xmlincludedllms.txtandllms-full.txtfor AI parsers- Dedicated semantic map:
docs/SEMANTIC_CORE.md
Example Workflows
- Differential Diagnosis Follow-up
- Ask OpenEvidence about a complex case, get source-backed answers with citations, then follow up in the same thread - all from your Claude Desktop or Codex CLI session.
- Treatment Comparison
- Query two treatment approaches side by side. The MCP server preserves conversation context so follow-up questions refine the answer.
- Journal Club Prep
- Pull recent articles on a topic via oe_history_list and oe_article_get. Feed them into your AI workflow for summary and discussion points.
- Team Knowledge Base
- Multiple clinicians can run their own sessions. Each authenticates with their own OpenEvidence account - no shared credentials needed.