Hospital Data MCP Server
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., "@Hospital Data MCP Server show me the list of patients in the hospital"
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.
Hospital Data MCP Server
A repo to manage an MCP server to enable access to the data set providing hospital data
The data is entirely made up and bears no linkage and or repsentation to any person.
Running: SSE
Need two terminal:
Terminal 1
uv run -m wxo_bootcamp_mcp_server.app_sse: Run the SSE serverTerminal 2
npx @modelcontextprotocol/inspector: Run the inspector for testing
Running: STDIO
Terminal
npx @modelcontextprotocol/inspector: Run the inspector for testingUse the following setup:
Transport Type:
STDIOCommand:
uv run -m wxo_bootcamp_mcp_server.app_stdioArguments:
--no-banner
Podman
You can do this for Terminal 1
from root
podman build .
podman run -p 8080:8080 [Container ID]
npx @modelcontextprotocol/inspector
Deploy to a TechZone zone Code Engine
Pre Reqs:
You will need to build the image locally
You will need a cloud account with a container registry you can write too
Install ibmcloud cli (https://cloud.ibm.com/docs/containers?topic=containers-cli-install)
Run the following commands:
ibmcloud plugin install container-registry -r 'IBM Cloud'
ibmcloud plugin install ce
Use an external IBM Cloud Container Registry
Account A (The one with the Container Registry)
$ibmcloud login -a https://cloud.ibm.com --sso
Choose the account with the Container
$ibmcloud target -r [region]
$ibmcloud target -g [group_name]
$ibmcloud cr login
$ibmcloud cr namespace-add [NAMESPACE]
$podman tag wxo-bootcamp-mcp-sever us.icr.io/[NAMESPACE]/[IMAGE_NAME]:[TAG]
$podman push us.icr.io/[NAMESPACE]/[IMAGE_NAME]:[TAG]
$ibmcloud iam service-id-create [SERVICE_ID_NAME] --description "Service ID for cross-account Container Registry access"
$ibmcloud iam service-policy-create [SERVICE_ID_NAME] --roles Reader --service-name container-registry
$ibmcloud iam service-api-key-create [API_KEY_NAME] [SERVICE_ID_NAME] --description "API key for cross-account registry access" --file api-key.json
To view the API Key and get [API_KEY_VALUE]
$cat api-jey.json
Account B (The techzone one with the Code Engine)
$ibmcloud login -a https://cloud.ibm.com --sso
Choose the account with the Techzone Account
$ibmcloud ce login
$ibmcloud ce project select -n [PROJECT NAME]
The project name is visible in the Code Engine page
$ibmcloud ce registry create --name [REGISTRY_SECRET_NAME] --server us.icr.io --username iamapikey --password [API_KEY_VALUE]
$ibmcloud ce application create --name [APP_NAME] --image us.icr.io/[NAMESPACE]/[IMAGE_NAME]:[TAG] --registry-secret [REGISTRY_SECRET_NAME]
Related MCP server: healthcare-mcp-demo
Use everything on the Techzone instance
$ibmcloud login -a https://cloud.ibm.com --sso
Choose the account with the Techzone Account
$ibmcloud target -g [RESOURCE_GROUP]
Get the Resource GRoup from the Resource List
$ibmcloud cr login
$podman tag wxo-bootcamp-mcp-sever us.icr.io/[NAMESPACE]/[IMAGE_NAME]:[TAG]
The [NAMESPACE] is the only one available when you look at Container Registry in the techzone instance. You do not need to create one
$podman push us.icr.io/[NAMESPACE]/[IMAGE_NAME]:[TAG]
$ibmcloud iam api-key-create [API_KEY_NAME] --d "Tech Zone Code Engine registry access"
$ibmcloud ce project select -n [PROJECT NAME]
$ibmcloud ce registry create -name [REGISTRY_SECRET_NAME] --server us.icr.io --username iamapikey --password [API_KEY_VALUE]
THE [API_KEY_VALUE] will be available from the previous command
$ibmcloud ce application create --name [APP_NAME] --image us.icr.io/[NAME_SPACE]/[IMAGE_NAME]:[TAG] --registry-secret [REGISTRY_SECRET_NAME]
Test using MCP Inspector
$npx @modelcontextprotocol/inspector
Use the URL for the application (from Code Endgine) and append /sse as the URL
https://[APP_NAME].[IBM_CLOUD_URL_PART]/sse
To run using personal access token from GitHUb, for wxo
uvx --from git+https://YOUR_TOKEN@github.ibm.com/Benjamin-Janes/wxo-bootcamp-mcp-server.git wxo-bootcamp-data-server-stdio
Available Tools
8 toolswxoGetDrugAlternativeTreatmentsC
Retrieves information about alternative treatments for a given drug or None
Inputs: drug_name (required). Returns: conditions, alternatives, original_drug
wxoGetDrugContraindicationsB
Returns comprehensive drug contraindication medical inforamation for a given drug or None
Inputs: drug_name (required). Returns: drug, reason, rule_id, severity, +1 more
wxoGetDrugInformationC
Returns comprehensive drug medical inforamation for a given drug or None
Inputs: drug_name (required). Returns: rxcui, warnings, drug_name, mechanism, +9 more
wxoGetDrugInterationsB
Returns comprehensive drug interaction medical inforamation for two given drugs or None
Inputs: drug_name_1 (required), drug_name_2 (required). Returns: drug1, drug2, severity, mechanism, +3 more
wxoGetMedicalInformationC
Returns comprehensive patient medical inforamation regarding the diagnosis (condition), allergies and any given prescriptions or None
Inputs: patient_id (required). Returns: allergies, conditions, prescriptions
wxoGetPatient360A
Given a patient id, construct a 360 view of a patient, their information, medical data and most recent vital signs
Inputs: patient_id (required). Returns: medical, information, vital_signs
wxoGetPatientInformationA
Returns basic patient information from the healthcare database including personal details, contact information and insurance data or None.
Inputs: patient_id (required). Returns: age, sex, pregnant, patient_id, +4 more
wxoGetVitalSignsInformationA
Returns patient vital signs from the bedside system (Blood pressure, pulse, creatine data, bmi, weight, height) or None.
Inputs: age (required), sex (required), patient_id (required). Returns: bmi, when, height_cm, weight_kg, +5 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 8 tools
Most tools target distinct data types (drug info, vital signs, patient info, medical info). The only overlap is wxoGetPatient360, which explicitly aggregates the individual patient-related getters, but its purpose as a composite view is clear from the description.
All tools follow the exact same 'wxoGet' + PascalCase noun pattern, creating a predictable and uniform naming convention. The minor typo in 'DrugInterations' does not affect the consistent structure.
With 8 tools, the server is well-scoped for a hospital data access API. The number is within the ideal 3-15 range and each tool serves a clear query purpose.
The tool set covers core patient, medical, vital signs, and drug-related queries, but lacks search/list operations (e.g., find patients, search drugs) and any write capabilities. While likely read-only, the absence of basic lookup endpoints creates notable gaps for general hospital data exploration.
Maintenance
Related MCP Connectors
Privacy-preserving synthetic health data generation. FHIR R4/R5 compliant.
Hosted MCP server for the Healthie EHR & telehealth API: patients, appointments, charting, tasks.
Hosted MCP server exposing US hospital procedure cost data to AI assistants
Hosted MCP server for Cliniko — patients, appointments, availability, and invoices for AI agents.
Related MCP Servers
- AlicenseAqualityDmaintenanceA Claude-compatible MCP server that exposes health-domain tools over 100% synthetic data, built with security and compliance in mind.4MIT
- FlicenseNot gradedqualityDmaintenanceA healthcare MCP demo server exposing clinical resources, tools, and prompts over SSE with authentication, integrated with Pydantic AI and Gemini for natural language patient record updates.-
- FlicenseNot gradedqualityDmaintenanceAn MCP server that enables LLMs to securely query synthetic clinical data through validated, scoped tools (patient summaries, conditions, medications, lab trends, encounters) while maintaining audit logs and access controls.-
- AlicenseNot gradedqualityCmaintenanceThis MCP server enables secure, read-only access to synthetic preventive-care patient records and bounded IRIS namespace health metrics through a small set of allowlisted, parameterized tools.1MIT