Real World Evidence MCP Server

Real World Evidence MCP server exists for a simple reason — assistants are far more useful when they can act on Real World Evidence directly instead of describing what you should do. RWE tool.

What you get

A local Model Context Protocol (MCP) server that exposes a single Real-World Evidence (RWE) tool to Claude. The tool returns aggregated, de-identified patient cohort statistics across four dimensions:

What the assistant can call

Once Real World Evidence is connected, these are the calls the assistant has available:

• Hypertension — Heart Failure
• COPD — Asthma
• Dimension — Values
• Gender — Male, Female, Unknown/Other
• Longitudinal — 2018 – 2024 (year-over-year trend)
• macOS — ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows — %APPDATA%\Claude\claude_desktop_config.json
• condition — string
• dimensions — string[]
• year_start — int
• year_end — int
• region — string

Configuration and credentials

You will need one environment variable: MCP_TRANSPORT. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Setting it up

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Choosing this one

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Real World Evidence's toolset — Hypertension, COPD, Dimension and 11 more — is a fair guide to whether it matches your workflow.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Real World Evidence.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the real world evidence mcp server does with a few real requests.