MCP Server for Google Cloud Healthcare API
The MCP Server for Google Cloud Healthcare API enables interaction with FHIR resources and medical research APIs. With this server, you can:
Search for patients by demographics (name, gender, birth date)
Retrieve patient data including observations/vitals, conditions, medications, encounters, allergies, procedures, care plans, and appointments
Analyze patient history: vital signs, lab results, and medication history including changes
Search medical literature on PubMed and find clinical trials on ClinicalTrials.gov
Get drug information by generic name and check drug-drug interactions
Execute custom FHIR queries for advanced use cases
Uses Firebase Authentication to secure access to the FHIR gateway and healthcare data
Interfaces with Google Cloud Healthcare API to access and query FHIR healthcare resources including patient data, observations, conditions, medications, and clinical records
Enables searching of PubMed medical research articles related to specific conditions or topics
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Server for Google Cloud Healthcare API get patient John Smith's current medications"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP Server for Google Cloud Healthcare API (FHIR)
A Model Context Protocol (MCP) server that provides healthcare tools for interacting with FHIR resources on Google Cloud Healthcare API and public medical research APIs like pubmed, using MCP clients like Claude and Goose.
This is a slightly modified version for AgentCare MCP Server for EHRs. https://github.com/Kartha-AI/agentcare-mcp
The maion differnce is that this repo talks to Google Cloud Healthcare FHIR APIs thru a SmartonFHIR gateway that's secured by Firebase Auth.
Architetcure
Related MCP server: Secure Remote MCP Server
Demo
Claude: demo/claude-demo.mp4
Goose: demo/goose-demo.mp4
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
refer to: /src/server/constants/tools.ts for tools specirfication
Use with claude desktop
for claude desktop:
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
(use the env variables as shown above)
{
"mcpServers": {
"google-cloud-healthcare-api-mcp": {
"command": "node",
"args": [
"/Users/your-username/{google-cloud-healthcare-api-mcp dir}/build/index.js"
],
"env": {
"FIREBASE_API_KEY":"XXXXXXXXX",
"FIREBASE_AUTH_DOMAIN":"XXXXXXXX",
"FIREBASE_PROJECT_ID":"XXXXXXX",
"FIREBASE_STORAGE_BUCKET":"XXXXXXXXX",
"FIREBASE_MESSAGING_SENDER_ID":"XXXXXXX",
"FIREBASE_APP_ID":"XXXXXXXXX",
"FIREBASE_MEASUREMENT_ID":"XXXXXXXX",
"FIREBASE_AUTH_CALLBACK_PORT":"3456",
"FHIR_BASE_URL":"{gchapi-fhir-gateway-host}/fhir",
"PUBMED_API_KEY":"your_pubmed_api_key",
"CLINICAL_TRIALS_API_KEY":"your_trials_api_key",
"FDA_API_KEY":"your_fda_api_key"
}
}
}
}Installing via Smithery
To install google-cloud-healthcare-api-mcp for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @Kartha-AI/google-cloud-healthcare-api-mcp --client claudeStart MCP Server Locally with MCP Inspector
git clone git@github.com:Kartha-AI/google-cloud-healthcare-api-mcp.git
cd google-cloud-healthcare-api-mcp
npm install
npm run build
npm install -g @modelcontextprotocol/inspector
mcp-inspector build/index.js
http://localhost:5173
Set up the env vars on InspectorTroubleshooting:
If Claude desktop is running it uses port 3456 for Auth. You need to terminate that process using the following command:
kill -9 $(lsof -t -i:3456)Available Tools
15 toolsfind_patientC
Search for a patient by demographics
Inputs: lastName (required), birthDate, firstName, gender.
get_appointmentsC
Get patient's Appointments
Inputs: patientId (required), dateFrom, dateTo.
get-drug-infoC
Get Drug details by a generic name
Inputs: genericName (required).
get_lab_resultsC
Get patient's lab results
Inputs: patientId (required), category, timeframe.
get_medications_historyC
Get patient's medication history including changes
Inputs: patientId (required), includeDiscontinued.
get_patient_allergiesC
Get allergies and intolerances for a patient
Inputs: patientId (required), category, status, type.
get_patient_careplansC
Get care plans for a patient
Inputs: patientId (required), category, dateFrom, dateTo, +1 more.
get_patient_conditionsC
Get medical conditions/diagnoses for a patient
Inputs: patientId (required), onsetDate, status.
get_patient_encountersC
Get healthcare encounters/visits for a patient
Inputs: patientId (required), dateFrom, dateTo, status.
get_patient_medicationsC
Get medication orders for a patient
Inputs: patientId (required), status.
get_patient_observationsC
Get observations (vitals, labs) for a patient
Inputs: patientId (required), code, dateFrom, dateTo, +1 more.
get_patient_proceduresC
Get procedures performed on a patient
Inputs: patientId (required), dateFrom, dateTo, status.
get_vital_signsC
Get patient's vital signs history
Inputs: patientId (required), timeframe.
search-pubmedC
Search PubMed for medical literature
Inputs: query (required), maxResults.
search-trialsC
Search ClinicalTrials.gov for relevant studies
Inputs: condition (required), location.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 15 tools
Each tool has a clearly distinct purpose targeting specific healthcare data types (e.g., appointments, lab results, medications, allergies). There is no overlap in functionality, and an agent can easily differentiate between tools based on the resource they retrieve.
Most tools follow a consistent verb_noun pattern (e.g., get_patient_allergies, get_patient_conditions), but there are minor deviations with hyphenated names (get-drug-info, search-pubmed, search-trials) and one tool using 'find' instead of 'get' (find_patient). Overall, the naming is readable and mostly predictable.
With 15 tools, the server is well-scoped for a healthcare API, covering a comprehensive range of patient data and external medical resources. Each tool serves a specific and necessary function without redundancy, making the count appropriate for the domain.
The tool set provides extensive read-only coverage for patient data (e.g., conditions, medications, encounters) and includes useful external searches (PubMed, clinical trials). Minor gaps exist, such as lack of write operations (e.g., create or update patient records), but the surface supports most agent workflows for data retrieval and research.
Related MCP Connectors
Hosted MCP server for the Healthie EHR & telehealth API: patients, appointments, charting, tasks.
Hosted MCP for denial, prior auth, reimbursement, workflow validation, batch scoring, and feedback.
Guardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation
Hosted MCP server for Cliniko — patients, appointments, availability, and invoices for AI agents.
Related MCP Servers
- AlicenseBqualityDmaintenanceEnables AI assistants to interact with and manage Google Cloud Platform resources including Compute Engine, Cloud Run, Storage, BigQuery, and other GCP services through a standardized MCP interface.16MIT
- AlicenseNot gradedqualityDmaintenanceActs as an AI Gateway for MCP servers using Azure API Management, implementing the latest MCP Authorization specification.131MIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that provides access to Google's API Discovery Service, allowing agents to discover and interact with Google APIs through natural language commands.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables interaction with Google's Cloud Healthcare API, allowing users to manage healthcare data, FHIR resources, DICOM stores, and healthcare datasets through natural language commands.-
Appeared in Searches
- Agentic RAG: Understanding or Exploring Its Meaning and Applications
- Research on Patient-Disease-Gene-Drug Relationships and Pharmacogenomics Using Digital Imaging Data
- Developing a FHIR-Based Digital Health Application with EHR, PHR, and Phenotyping Frameworks
- A database of diseases with associated genetic variants and sequencing information
- Information about Google Calendar