Used for project cloning and source code management during development and installation
Used for package management and running build scripts for the MCP server
Provides tools to search PubMed articles related to medical conditions, integrating medical research capabilities
Leverages SMART on FHIR APIs for EMR integration with systems like Cerner and Epic, enabling authentication and data access
Agent Care: An MCP Server for EMRs like Cerner and Epic
A Model Context Protocol (MCP) server that provides healthcare tools and prompts for interacting with FHIR data and medical resources on EMRs like Cerner and Epic using Claude Desktop and Goose Desktop.
Demo

Features
EMR integrartion using SMART on FHIR APIs
Uses OAuth2 to authenticate with EMRs
Anthropic Claude Desktop integration
Medical research integration (PubMed, Clinical Trials, FDA)
Response caching
Error handling
Null-safe data formatting
Comprehensive clinical analysis
Screenshots
Tools
FHIR Tools
find_patient- Search for a patient by name, DOB, or other identifiersget_patient_observations- Retrieve patient observations/vital signsget_patient_conditions- Get patient's active conditionsget_patient_medications- Get patient's current medicationsget_patient_encounters- Get patient's clinical encountersget_patient_allergies- Get patient's allergies and intolerancesget_patient_procedures- Get patient's proceduresget_patient_careteam- Get patient's care team membersget_patient_careplans- Get patient's active care plansget_vital_signs- Get patient's vital signsget_lab_results- Get patient's laboratory resultsget_medications_history- Get patient's medication historyclinical_query- Execute custom FHIR queries
Medical Research Tools
search-pubmed- Search PubMed articles related to medical conditionssearch-trials- Find relevant clinical trialsdrug-interactions- Check drug-drug interactions
Usage
Each tool requires specific parameters:
Required Parameters
Most tools require
patientIdSome tools have additional parameters:
lab_trend_analysis: requireslabTypesearch-pubmed: requiresqueryand optionalmaxResultssearch-trials: requiresconditionand optionallocationdrug-interactions: requiresdrugsarray
Development Configuration
To use with Cerener: Go to https://code-console.cerner.com and create a sandbox account, create a new provider app and get the clientId/secret. (note: ec2458f2-1e24-41c8-b71b-0e701af7583d below is the tenant id for cerner developer sandbox)
To use with Epic: Go to https://fhir.epic.com/Developer/Apps , sign up as developer and create a new app and get the clientId/secret.
For PubMed, Clinical Trials and FDA, you need to get the API keys from the respective websites.
https://clinicaltrials.gov/api/v2/studies
https://eutils.ncbi.nlm.nih.gov/entrez/eutils
https://api.fda.gov/drug/ndc.json
For local testing Create a .env file in the root directory or use these environment variables in claude desktop launch configuration.
Cerner
Epic
Start MCP Server Locally
Use claude desktop
Use MCP Inspectopr
(MCP Server using inspector. Make sure to update the .env file with the correct values.)
Test User Logins
(commonly used for sandbox/dev)
Cerner: portal | portal
Epic: FHIRTWO | EpicFhir11!
Troubleshooting:
If Claude desktop is running it uses port 3456 for Auth. You need to terminate that process using the following command:
Use Goose
Goose is an open Source AI Agent frameowrk from Block(Stripe) that works with MCP servers. Goose Desktop is like Claude Desktop that can work with MCP servers. But Goose can be configured to use models other than Anthropic as well. More info: https://block.xyz/inside/block-open-source-introduces-codename-goose
See below how Goose Desktop works with Agent Care: (goose extension will be configured with command: /Users/your-username/{agentcare-download-path}/agent-care-mcp/build/index.js)