OpenEvidence MCP

Use the canonical htlin222/openevidence-mcp implementation. It sends OpenEvidence requests through a localhost relay and a Chromium extension running inside the user's logged-in browser tab.

Never reimplement the OpenEvidence API, send direct HTTP requests to its private API, or fall back to an exported-cookie Python client. Plain server requests are blocked by bot detection. If the MCP tools are unavailable, install or repair the MCP instead.

Route the request

1. If the user wants to install, update, inspect, clean up, or uninstall the MCP, run the matching command from scripts/oe-mcp.sh.
2. If the user wants OpenEvidence data and the oe_* MCP tools are available, call those tools directly.
3. If the user wants OpenEvidence data but the tools are unavailable, do not substitute a direct HTTP client. Install the MCP only when the user asked for setup or authorizes the prerequisite; otherwise explain the missing dependency and ask them to approve installation. Complete the manual browser step and reconnect the MCP client before attempting the query.
4. Read references/tools.md when choosing among the complete tool set.

Resolve the skill directory containing this SKILL.md, then invoke:

bash <skill-directory>/scripts/oe-mcp.sh <install|update|status|cleanup|uninstall>