MCP.so
ログイン
O

OpenEvidence MCP

@bakhtiersizhaev

OpenEvidence MCP について

Open-source MCP server that connects OpenEvidence clinical evidence workflows to AI clients using browser-session auth (Playwright), no API key required.

基本情報

カテゴリ

ブラウザ自動化

トランスポート

stdio

公開者

bakhtiersizhaev

投稿者

Bakhtier Sizhaev

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "openevidence": {
      "command": "npx",
      "args": [
        "-y",
        "openevidence-mcp"
      ]
    }
  }
}

ツール

4

validate account session (`/api/auth/me`)

list conversation history (`/api/article/list`)

fetch full article payload by ID

ask a question and optionally wait for completion

概要

What is OpenEvidence MCP?

OpenEvidence MCP is an unofficial Model Context Protocol server that bridges OpenEvidence to MCP clients (Codex CLI, Claude Desktop/Code, Cursor, Cline, Continue). It uses your own browser session via Playwright storage state to enable clinical evidence workflows from AI assistants, since OpenEvidence lacks a public API token flow.

How to use OpenEvidence MCP?

Provide a captured Playwright storage state from your authenticated OpenEvidence browser session, then configure your MCP client to invoke the server. Use the provided tools (oe_auth_status, oe_history_list, oe_article_get, oe_ask) in your AI coding assistant.

Key features of OpenEvidence MCP

  • Bridges OpenEvidence to popular MCP clients
  • Uses your own browser session via Playwright storage state
  • Offers four tools: auth check, history list, article fetch, ask
  • Supports macOS, Windows, and Linux
  • No public API token required
  • Open source under Apache‑2.0

Use cases of OpenEvidence MCP

  • Query clinical evidence while coding in Claude Desktop
  • Fetch full article payloads by ID from Cursor
  • List conversation history to review past questions
  • Check account session validity before running workflows
  • Automate clinical evidence retrieval in Cline or Codex CLI

FAQ from OpenEvidence MCP

What is OpenEvidence MCP and why was it created?

It is an unofficial MCP server that bridges OpenEvidence to MCP clients. It was created because OpenEvidence has no public API token flow for third‑party integrations, so it uses your own browser session instead.

What tools does OpenEvidence MCP provide?

It provides four tools: oe_auth_status (validate account session), oe_history_list (list conversation history), oe_article_get (fetch full article by ID), and oe_ask (ask a question with optional completion wait).

What platforms are supported?

macOS, Windows, and Linux are supported.

How does authentication work?

Authentication is handled by your own browser session captured as a Playwright storage state. No API token is needed; the server uses your existing OpenEvidence login.

Is this an official integration?

No, it is an unofficial server. The official OpenEvidence platform does not provide a public API token flow for third‑party MCP integrations.

コメント

「ブラウザ自動化」の他のコンテンツ