Reported issues for openevidence-mcp
Pod holds 11 of 11 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.
Back to openevidence-mcp.
Most discussed
oe_ask always returns 403 Cloudflare block regardless of IP, browser, or auth state
Hi, first of all thank you for this project — the setup was smooth and oe_auth_status and npm run smoke both return ok: true and authenticated: true consistently. The issue is exclusively with oe_ask.
Environment:
OS: Windows 11 Node.js: v24.15.0 npm: 11.12.1 MCP client: Claude Desktop Playwright Chromium: installed via npx playwright install chromium Login method: npm run login:browser (with PLAYWRIGHT_CHROMIUM_EXECUTABLE_PATH pointing to system Chrome)
Problem:
Every call to oe_ask
Read the thread · 2026-05-29 · closed · external user · 4 comments
"npm run smoke" failed at authentication, and can be solved by adding "--password-store=basic" flag
Thank you for your fast update about the Cloudflare's protection issue. This repo helps alot in my AI-aided medical articles reviewing/searching workflow. I stepped on an obstacle re-installing this mcp and re-login, and Claude Code helped me fix this.
Environment:
OS Garuda Linux x86_64 (based on Arch linux) ├ Kernel Linux 7.0.10-zen1-1-zen ├ Packages 10 (flatpak-system), 26 (flatpak-user), 1572 (pacman)[stable] └ Shell fish 4.7.1
DE KDE Plasma 6.6.5 ├ Window Manager KWin (Wayland) ├
Read the thread · 2026-06-03 · closed · external user · 1 comment
docs: put copy-paste agent install prompt in README
Problem
Read the thread · 2026-05-20 · closed · 0 comments
docs: add Korean and Taiwan README localization
Goal
Read the thread · 2026-05-20 · closed · 0 comments
Add availability notes, README translations, client matrix, and Codex MCP setup
Summary
Read the thread · 2026-05-20 · closed · 0 comments
Harden OSS/MCP docs, security, and tool descriptions
Summary
Read the thread · 2026-05-20 · closed · 0 comments
test: add automated CI with GitHub Actions
Goal
Set up GitHub Actions to run build + smoke test on every push/PR.
Tasks
- Create .github/workflows/ci.yml
- Run on Node 20 + 22
- Run on ubuntu-latest, macos-latest, windows-latest
- Cache node_modules and Playwright browsers
- Badge in README
Why
CI badge in README signals project quality. Automated testing catches regressions.
Read the thread · 2026-02-21 · closed · 0 comments
feat: add config templates for Cursor, Cline, Continue, Windsurf
Goal
Provide ready-to-use config snippets for all popular MCP clients beyond Codex and Claude Desktop.
Tasks
- Cursor config template
- Cline config template
- Continue config template
- Windsurf config template
- OpenClaw config template
- Add all to examples/ directory
- Document in README
Why
More config templates = lower friction = more users.
Read the thread · 2026-02-21 · closed · 0 comments
Most recent
feat: streaming response support for oe_ask
Goal
Add an option to stream partial responses from oe_ask as they arrive, instead of waiting for full completion.
Tasks
- Investigate OpenEvidence streaming behavior (SSE/WebSocket)
- Implement streaming output in MCP tool response
- Add
stream: trueparameter tooe_ask - Update smoke test
Why
Long clinical questions can take 30-60s. Streaming gives the user partial results immediately.
Read the thread · 2026-02-21 · closed · 0 comments
feat: add Docker container support
Goal
Provide a Dockerfile so users can run the server in a container without installing Node.js or Playwright locally.
Tasks
- Create Dockerfile based on mcr.microsoft.com/playwright
- Add docker-compose.yml for easy startup
- Mount auth state volume for session persistence
- Document in README
Why
Docker simplifies deployment in clinical IT environments where installing global npm packages is restricted.
Read the thread · 2026-02-21 · closed · 0 comments
feat: publish npm package for npx one-command install
Goal
Enable installation via:
npx openevidence-mcp
Tasks
- Prepare package.json for npm publish (bin entry, files, engines)
- Add shebang to server entry point
- Test npx execution on macOS, Windows, Linux
- Publish to npmjs.com
- Update README with npx install method
Why
npm is a major discovery channel for MCP servers. npx install reduces friction from 5 steps to 1.
Read the thread · 2026-02-21 · closed · 0 comments
The remaining reports are on the project's issue tracker.