Skip to main content
Glama
Hospital Data MCP Server

Hospital Data MCP Server

by Nniol

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

  1. uv run -m wxo_bootcamp_mcp_server.app_sse : Run the SSE server

Terminal 2

  1. npx @modelcontextprotocol/inspector : Run the inspector for testing

Running: STDIO

Terminal

  1. npx @modelcontextprotocol/inspector : Run the inspector for testing

  2. Use the following setup:

    • Transport Type: STDIO

    • Command: uv run -m wxo_bootcamp_mcp_server.app_stdio

    • Arguments: --no-banner

Podman

You can do this for Terminal 1

  1. from root

  2. podman build .

  3. podman run -p 8080:8080 [Container ID]

  4. npx @modelcontextprotocol/inspector

  5. https://localhost:8080/sse

Deploy to a TechZone zone Code Engine

Pre Reqs:

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 tools
wxoGetDrugAlternativeTreatmentsC

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

    A3.5/5.0

    Scored across 8 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers