MCP Server for Google Cloud Healthcare API
Google Cloud Healthcare API(FHIR)를 위한 MCP 서버
Claude와 Goose와 같은 MCP 클라이언트를 사용하여 Google Cloud Healthcare API 및 PubMed와 같은 공공 의료 연구 API의 FHIR 리소스와 상호 작용하기 위한 의료 도구를 제공하는 MCP(모델 컨텍스트 프로토콜) 서버입니다.
이는 EHR용 AgentCare MCP Server의 약간 수정된 버전입니다. https://github.com/Kartha-AI/agentcare-mcp
가장 큰 차이점은 이 저장소가 Firebase 인증으로 보호되는 SmartonFHIR 게이트웨이를 통해 Google Cloud Healthcare FHIR API와 통신한다는 것입니다.
건축
Related MCP server: Secure Remote MCP Server
데모
클로드: 데모/claude-demo.mp4
구스: 데모/구스-데모.mp4
스크린샷
도구
FHIR 도구
find_patient- 이름, 생년월일 또는 기타 식별자로 환자 검색get_patient_observations- 환자 관찰 결과/생명 징후 검색get_patient_conditions- 환자의 활성 상태 가져오기get_patient_medications- 환자의 현재 복용 약물을 가져옵니다.get_patient_encounters- 환자의 임상적 접촉을 가져옵니다.get_patient_allergies- 환자의 알레르기 및 불내증 정보 얻기get_patient_procedures- 환자의 시술 정보를 가져옵니다.get_patient_careteam- 환자의 케어팀 구성원을 가져옵니다get_patient_careplans- 환자의 활성 치료 계획을 가져옵니다.get_vital_signs- 환자의 생체 신호를 가져옵니다get_lab_results- 환자의 검사 결과 가져오기get_medications_history- 환자의 약물 복용 내역을 가져옵니다.clinical_query- 커스텀 FHIR 쿼리 실행
의학 연구 도구
search-pubmed- 의학적 상태와 관련된 PubMed 기사 검색search-trials- 관련 임상 시험 찾기drug-interactions- 약물 간 상호작용 확인
용법
각 도구에는 특정 매개변수가 필요합니다.
필수 매개변수
대부분의 도구에는
patientId필요합니다.일부 도구에는 추가 매개변수가 있습니다.
lab_trend_analysis:labType필요합니다.search-pubmed:query와 선택적maxResults필요합니다.search-trials:condition및 선택적location필요합니다.drug-interactions:drugs배열이 필요합니다
도구 사양은 /src/server/constants/tools.ts를 참조하세요.
클로드 데스크탑과 함께 사용하세요
지엑스피1
Smithery를 통해 설치
Smithery를 통해 Claude Desktop에 google-cloud-healthcare-api-mcp를 자동으로 설치하려면 다음을 수행합니다.
npx -y @smithery/cli install @Kartha-AI/google-cloud-healthcare-api-mcp --client claudeMCP Inspector를 사용하여 로컬에서 MCP 서버 시작
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 Inspector문제 해결:
Claude 데스크톱이 실행 중이면 인증을 위해 3456 포트를 사용합니다. 다음 명령을 사용하여 해당 프로세스를 종료해야 합니다.
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