openevidencelisted

Query OpenEvidence (clinical evidence assistant) without an MCP server. Mirrors the openevidence-mcp tool surface 1:1 - check auth, list question history, fetch an article, or ask a new question (with optional follow-up thread). Use when the user asks medical / evidence-based clinical questions, references OpenEvidence, asks for "OE answers", or wants citations + BibTeX from OpenEvidence. Portable to claude.ai's /mnt sandbox - just drop the folder and a fresh cookies.json next to scripts/oe.py.
htlin222/openevidence-mcp · ★ 42 · AI & Automation · score 83

Install: claude install-skill htlin222/openevidence-mcp

# OpenEvidence (portable) A stdlib-only Python port of `openevidence-mcp`. One CLI (`scripts/oe.py`) with four subcommands matching the MCP tools. | MCP tool | Skill command | Purpose | | ----------------- | ------------------------------------------ | -------------------------------------------------------- | | `oe_auth_status` | `python3 scripts/oe.py auth-status` | Confirm `cookies.json` still authenticates `/api/auth/me` | | `oe_history_list` | `python3 scripts/oe.py history` | Paginated question history with optional search | | `oe_article_get` | `python3 scripts/oe.py article <uuid>` | Fetch an article, extract answer + figures, save artifacts | | `oe_ask` | `python3 scripts/oe.py ask "<question>"` | Submit a new question, optionally wait, save artifacts | Output of every command is a single JSON object on stdout - same shape the MCP returns to its client. ## Setup (one time) 1. **Cookies**. Export the OpenEvidence cookies from a logged-in browser tab (e.g. "Cookie-Editor" extension → "Export → JSON"). Save as `cookies.json` next to this `SKILL.md`. The format is either a flat array of cookie objects or `{ "cookies": [...] }` (Playwright storage state). The file is gitignored. 2. **Verify**. `python3 scripts/oe.py auth-status` should print `"authenticated": true`. Status `401`/`403` means the cookies expired - re-export. Cookie looku