Advertise
MCP.so
Sign In

MCP Server for AWS HealthLake (Mocked)

@anandkiran2007

Repository

Basic information

Category

Cloud & Infrastructure

Transports

stdio

Author

anandkiran2007

About MCP Server for AWS HealthLake

No overview available yet

#mcp-server#aws-healthlake#mock-server

MCP Server for AWS HealthLake config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "ahl-mcp-server": {
      "command": "python3",
      "args": [
        "-m",
        "venv",
        "venv"
      ]
    }
  }
}

MCP Server for AWS HealthLake tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is 🏥 MCP Server for AWS HealthLake (Mocked)?

This is an open-source Model Context Protocol (MCP) server that connects to (mocked) AWS HealthLake data sources and provides structured, standardized context bundles for clinical models.

How to use 🏥 MCP Server for AWS HealthLake (Mocked)?

Clone the repository, create a Python virtual environment, install dependencies with pip install -r requirements.txt, and run the server locally with uvicorn app.main:app --reload. By default the server runs in mock mode; set the environment variable USE_AWS=true to prepare for future AWS integration (AWS mode is not yet implemented). Access the interactive documentation at http://localhost:8000/docs.

Key features of 🏥 MCP Server for AWS HealthLake (Mocked)

  • Mocked AWS HealthLake APIs based on FHIR
  • Context bundling per MCP spec (FHIR + NLP)
  • Model registration and tailored context delivery
  • Mocked model invocation endpoint
  • Audit logging
  • Optional USE_AWS flag for future AWS integration

Use cases of 🏥 MCP Server for AWS HealthLake (Mocked)

  • Providing structured context bundles for clinical model predictions
  • Registering models and retrieving tailored patient context
  • Testing MCP workflows without incurring real AWS costs
  • Prototyping and validating FHIR-based integrations with HealthLake
  • Simulating patient data (conditions, medications, observations) for development

Frequently asked questions

1

What is the default mode of operation?

The server runs in mock mode by default, using mocked AWS HealthLake APIs. Real AWS integration is not yet implemented.

2

How can I prepare for real AWS integration?

Set the environment variable `USE_AWS=true` to switch to AWS mode. Note that AWS mode is not implemented yet but the infrastructure is ready for integration.

3

What FHIR endpoints are available for testing?

Mock endpoints include `POST /ahl/Patient`, `GET /ahl/Patient/{id}`, and `GET` endpoints for Condition, MedicationRequest, and Observation. You can also add mock data via `/ahl/mock/add_*` endpoints.

4

How can I run the tests?

Run `pytest tests/` from the project root.

5

What is the license?

The project is licensed under the MIT License.

Comments

More Cloud & Infrastructure MCP servers

Kubernetes MCP Server

manusa

Model Context Protocol (MCP) server for Kubernetes and OpenShift

1.8K

YesTechie — UniFi Network & Security Integrator

YesTechie

YesTechie builds enterprise UniFi networks, cameras, access control, cabling and Wi-Fi for businesses nationwide from its California HQ. Agents can read real project case studies and practical configuration guides, price

Terraform MCP Server

hashicorp

The Terraform MCP Server provides seamless integration with Terraform ecosystem, enabling advanced automation and interaction capabilities for Infrastructure as Code (IaC) development.

1.5K

🐳 docker-mcp

QuantGeekDev

A docker MCP Server (modelcontextprotocol)

490

Muumuu Domain MCP Server

pepabo

The official MCP server for Muumuu Domain by GMO Pepabo, Inc — the first remote MCP server in the Japanese domain registrar industry. Search and register domains, manage owned domains and contracts, and configure DNS rec

1
Advertise