practice-fusion-mcp
Enables read-only FHIR access to Practice Fusion EHR to search patients, appointments, conditions, medications, and lab results.
README
practice-fusion-mcp
An open-source, FHIR-first, read-only Model Context Protocol server for Practice Fusion. Connect Claude (Desktop / Code), Cursor, or any MCP client to a Practice Fusion EHR to search patients and review appointments, conditions, medications, and labs — running on Practice Fusion's free Open FHIR account.
Read-only by design. Audit-logged. No write access, no scheduling, no patient creation.
Architecture
flowchart LR
C["MCP client<br/>Claude Desktop / Code · Cursor"] -- stdio --> S
subgraph S["practice-fusion-mcp"]
direction TB
T["MCP tools<br/>search_patients · get_patient<br/>appointments · conditions<br/>medications · lab_results"]
A["Audit logger<br/>stderr + optional file<br/>PHI-redacted"]
F["FHIR client<br/>Bundle unwrap · shapers<br/>sanitized errors"]
TP["SMART backend-services<br/>TokenProvider<br/>signed JWT assertion · token cache"]
T -. audited .-> A
T --> F
F --> TP
end
TP -- "OAuth2 client-credentials" --> AUTH["PF token endpoint"]
F -- "read-only FHIR R4" --> PF["Practice Fusion<br/>Open FHIR API"]
AUTH -- access token --> F
Every tool call flows through the audit logger; the FHIR client only ever holds a short-lived token minted from a signed JWT assertion (SMART backend-services), and long free-text parameters are redacted before anything is logged.
Tools
All tools are namespaced with a practicefusion_ prefix (so they don't collide when loaded alongside other MCP servers), carry a readOnlyHint annotation, and return a typed outputSchema / structuredContent. List tools accept an optional limit (default 50, max 200) and report count and has_more.
| Tool | What it does |
|---|---|
practicefusion_search_patients |
Find patients by name / birthdate / gender / identifier |
practicefusion_get_patient |
One patient's demographics by id |
practicefusion_get_appointments |
Appointments by patient / status / date |
practicefusion_get_conditions |
A patient's problems / diagnoses |
practicefusion_get_medications |
A patient's medication requests |
practicefusion_get_lab_results |
A patient's laboratory observations |
Setup
- Register a free Practice Fusion Open FHIR developer account and create a System / backend-services app. Note your FHIR base URL, token URL, client id, and register your app's public key.
- Provide the environment variables below. In production, use your MCP client's
envblock (shown in step 3). For local development, copy.env.exampleto.env—pnpm devloads it automatically. - Add to your MCP client config, e.g. Claude Desktop:
{
"mcpServers": {
"practice-fusion": {
"command": "npx",
"args": ["-y", "practice-fusion-mcp"],
"env": {
"PF_FHIR_BASE_URL": "https://fhir.practicefusion.com/r4",
"PF_TOKEN_URL": "https://auth.practicefusion.com/token",
"PF_CLIENT_ID": "your-client-id",
"PF_PRIVATE_KEY": "-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----"
}
}
}
}
Environment variables
| Var | Required | Default | Notes |
|---|---|---|---|
PF_FHIR_BASE_URL |
yes | — | FHIR R4 base URL |
PF_TOKEN_URL |
yes | — | OAuth2 token endpoint |
PF_CLIENT_ID |
yes | — | Backend-services client id |
PF_PRIVATE_KEY |
yes | — | PKCS8 PEM private key (matches the registered public key) |
PF_SCOPES |
no | system/*.read |
Requested scopes |
PF_TOKEN_ALG |
no | RS384 |
JWT signing alg |
PF_AUDIT_LOG |
no | — | Optional file path for audit records (always also written to stderr) |
Security & HIPAA
This server handles Protected Health Information. You, the deployer, are the covered entity or business associate: you are responsible for your own Business Associate Agreement (BAA) with Veradigm/Practice Fusion and for running this in a HIPAA-appropriate environment. Every tool call is audit-logged (stderr, plus optional file) with long free-text parameters redacted. Tokens and keys are never logged. This project ships code, not a hosted data service. Not legal advice.
How it differs from the alternative
The other Practice Fusion MCP is built on Practice Fusion's proprietary Unity APIs (paid Integrator tier) and is write-heavy. This one is FHIR-based (runs on the free Open account), read-only (smaller risk surface), and audit-logged.
Development
pnpm install
pnpm test # unit tests (mocked FHIR)
pnpm build # bundle to dist/
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。