home / mcp / agent care mcp server
Provides EMR integration, FHIR access, and medical research tools via an MCP server for Cerner and Epic.
Configuration
View docs{
"mcpServers": {
"kartha-ai-agentcare-mcp": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/Users/your-username/Desktop"
],
"env": {
"FDA_API_KEY": "YOUR_FDA_API_KEY",
"OAUTH_SCOPES": "user/Patient.read",
"FHIR_BASE_URL": "https://fhir.example.com/r4",
"OAUTH_AUDIENCE": "https://fhir.example.com",
"PUBMED_API_KEY": "YOUR_PUBMED_API_KEY",
"OAUTH_CLIENT_ID": "YOUR_CLIENT_ID",
"OAUTH_TOKEN_HOST": "https://authorization.example.com",
"OAUTH_TOKEN_PATH": "/token",
"OAUTH_CALLBACK_URL": "http://localhost:3456/oauth/callback",
"OAUTH_CALLBACK_PORT": "3456",
"OAUTH_CLIENT_SECRET": "YOUR_CLIENT_SECRET",
"OAUTH_AUTHORIZE_PATH": "/authorize",
"CLINICAL_TRIALS_API_KEY": "YOUR_CLINICAL_TRIALS_API_KEY",
"OAUTH_AUTHORIZATION_METHOD": "'header'"
}
}
}
}Agent Care MCP Server provides healthcare tools and prompts to interact with FHIR data on EMRs like Cerner and Epic. It integrates with SMART on FHIR, supports OAuth2 authentication, and offers medical research integrations and clinical analysis capabilities. This guide walks you through practical usage, installation steps, and essential configuration to run Agent Care on your environment.
You will run the MCP server locally and connect it to your preferred MCP client (for example Goose Desktop or Claude Desktop). The server exposes FHIR-related tools (find patients, get observations, labs, medications, care teams, and more) and medical research tools (PubMed searches, clinical trials, and drug interactions). You interact with the server by starting it as a local process and pointing your MCP client at the appropriate stdio entry. Use the included environment variables to configure your OAuth and API keys for Cerner or Epic connections.
Prerequisites: you need Node.js installed on your system, plus access to a terminal. You should also have a compatible MCP client ready to connect to a local stdio server.
1) Clone the Agent Care MCP project and install dependencies.
2) Build the server so you can run the built index. Run the following commands in order.
Configuration and MCP connections are defined in concrete code blocks below. Two local stdio servers are used to run the Agent Care MCP server and the filesystem provider for local data. Real values should be supplied via environment variables in your deployment or launch configuration.
{
"mcpServers": {
"filesystem": {
"command": "npx",
"args": [
"-y",
"@modelcontextprotocol/server-filesystem",
"/Users/your-username/Desktop"
]
},
"agent-care": {
"command": "node",
"args": [
"/Users/your-username/{agentcare-download-path}/agent-care-mcp/build/index.js"
],
"env": {
"OAUTH_CLIENT_ID": "XXXXXX",
"OAUTH_CLIENT_SECRET": "XXXXXXX",
"OAUTH_TOKEN_HOST": "",
"OAUTH_TOKEN_PATH": "",
"OAUTH_AUTHORIZE_PATH": "",
"OAUTH_AUTHORIZATION_METHOD": "",
"OAUTH_AUDIENCE": "",
"OAUTH_CALLBACK_URL": "",
"OAUTH_SCOPES": "",
"OAUTH_CALLBACK_PORT": "",
"FHIR_BASE_URL": "",
"PUBMED_API_KEY": "",
"CLINICAL_TRIALS_API_KEY": "",
"FDA_API_KEY": ""
}
}
}
}Handle OAuth client IDs, secrets, and API keys securely. Do not commit credentials to source control. Use a secure secrets store or environment configuration in your deployment platform. Ensure redirection URIs for OAuth match the OAUTH_CALLBACK_URL in your environment.
Search for a patient by name, DOB, or other identifiers.
Retrieve patient observations and vital signs.
Get patient's active conditions.
Get patient's current medications.
Get patient's clinical encounters.
Get patient's allergies and intolerances.
Get patient's procedures.
Get patient's care team members.
Get patient's active care plans.
Get patient's vital signs.
Get patient's laboratory results.
Get patient's medication history.
Execute custom FHIR queries.
Search PubMed articles related to medical conditions.
Find relevant clinical trials.
Check drug-drug interactions.