Openevidence Mcp
Unofficial MCP server connecting OpenEvidence to AI agents via authenticated browser sessions
- Transport
- Not stated
- Package
- —
- Registry id
- io.github.bakhtiersizhaev/openevidence-mcp
No install snippet on purpose. A working MCP config is a command, its arguments and an environment block — the last two are where API keys live, so this catalogue never stores them and cannot publish them. Follow the link above for the authors' own instructions.
No API key is required. Authenticate once with npm run login:session; the server reuses your local browser profile. Registry metadata version 0.2.2 continues to use the existing npm package 0.2.1.
OpenEvidence MCP is an unofficial Model Context Protocol server that connects OpenEvidence to Codex, Claude Code, Claude Desktop, Cursor, Cline, Continue, and other MCP-compatible clients through your own authenticated browser session.
Important
This project is unofficial and is not affiliated with OpenEvidence. It does not provide medical advice, does not bypass access controls, and should only be used with your own OpenEvidence account in compliance with applicable terms, privacy rules, and clinical governance requirements.
Translations: Русский | Español | 简体中文 | 繁體中文（台灣） | 한국어 | हिन्दी
Agent Onboarding & Installation
Using Codex, Claude Code, Cursor, or another local AI coding agent? You can let the agent handle the entire setup, compilation, and local MCP configuration for you!
Copy and paste this short bootstrap prompt directly into your local AI coding assistant:
Please install OpenEvidence MCP for me: clone https://github.com/bakhtiersizhaev/openevidence-mcp, install dependencies, run build, auto-configure this MCP server in my local client (Claude Desktop/Codex/Cursor), guide me through the one-time Edge/Chrome login using `npm run login:session`, and run `npm run smoke` to verify. Keep everything strictly local and secure.
For the comprehensive, step-by-step setup playbook and rules, see docs/AGENT_INSTALL_PROMPT.md.
What it does
OpenEvidence MCP runs a local stdio MCP server that lets MCP clients use your existing OpenEvidence browser session for:
- checking whether the saved session is authenticated;
- listing your OpenEvidence question/article history;
- fetching a full article payload by ID;
- asking an OpenEvidence research question and optionally waiting for completion;
- polling an existing OpenEvidence article until it completes.
No official OpenEvidence API token is required.
What it does NOT do
- It is not affiliated with, endorsed by, or approved by OpenEvidence.
- It does not provide medical advice or replace clinical judgment.
- It does not bypass authentication, paywalls, or access controls.
- It does not collect credentials.
- It does not send your browser session state anywhere except to OpenEvidence through local requests from your machine.
- It should not be used for patient-specific diagnosis or treatment decisions without appropriate human review.
Who it is for
- clinicians using their own OpenEvidence account;
- medical researchers;
- AI operators building evidence-research workflows;
- MCP developers integrating local tools with Codex, Claude, Cursor, Cline, Continue, or similar clients.
Tested / Target Clients
This project is designed for MCP-compatible clients and local agent workflows. Only Codex and Claude-style local configuration examples are maintained in this repository unless otherwise noted.
From the project's README.