
Openevidence Mcp
Route clinical and medical evidence questions from your agent through OpenEvidence using an authenticated browser session bridge.
Overview
io.github.bakhtiersizhaev/openevidence-mcp is an Idea-phase MCP server that links OpenEvidence to AI agents via authenticated browser sessions for evidence-oriented research queries.
What is this MCP server?
- Unofficial MCP server linking OpenEvidence to AI agents (openevidence-mcp npm v0.2.1, stdio)
- Uses authenticated browser-session style access rather than a first-party public API listing
- YOUR_API_KEY required secret per catalog schema for service authentication
- Useful for health-adjacent builders grounding answers in evidence-oriented workflows
- GitHub: bakhtiersizhaev/openevidence-mcp for self-hosted agent research setups
- Version 0.2.1
- 1 required secret env var: YOUR_API_KEY per server schema
- Unofficial integration; stdio npm package openevidence-mcp
Community signal: 24 GitHub stars.
What problem does it solve?
Health and evidence-heavy projects stall when your agent cannot reach OpenEvidence-style sources and you end up copying queries manually between browser tabs and chat.
Who is it for?
Solo builders in medical, health, or bioinformatics exploration who already use OpenEvidence and want agent-assisted research during early product validation.
Skip if: General web search, regulated clinical deployment without human oversight, or teams that require official vendor APIs and contracts only.
What do I get? / Deliverables
After you configure the stdio server and API key, your agent can pursue OpenEvidence-connected research flows in one MCP-backed session instead of ad hoc copy-paste.
- MCP-linked OpenEvidence research path for agent-driven queries
- Reduced manual tab switching during evidence discovery
- Configurable stdio server entry for health-oriented agent prototypes
Recommended MCP Servers
Journey fit
Evidence lookup and synthesis belong in Idea research when you are validating medical, health, or bio adjacent product directions before Build. Research is the shelf because the server connects agents to OpenEvidence content via session auth—not shipping code or payment rails.
How it compares
Unofficial evidence-session MCP bridge, not a HIPAA-certified product or a generic browser automation marketplace entry.
Common Questions / FAQ
Who is io.github.bakhtiersizhaev/openevidence-mcp for?
Developers and researchers building health-adjacent agents who need OpenEvidence reachable through MCP during early evidence and idea research.
When should I use io.github.bakhtiersizhaev/openevidence-mcp?
Use it in the Idea research phase while validating clinical or medical information products, before you harden a regulated Build or Ship path.
How do I add io.github.bakhtiersizhaev/openevidence-mcp to my agent?
Install openevidence-mcp from npm, provide YOUR_API_KEY in the MCP server environment, configure stdio in Claude Code or Cursor, and follow the repository guidance for session authentication.