Skip to content
Cloud InfrastructureAuto-generatedScore: 46

Amazon HealthLake MCP Server

Amazon HealthLake is a fully managed, HIPAA-eligible service from Amazon Web Services (AWS) designed to centralize the management of healthcare data in the cloud.

Quick Start Summary

The Amazon HealthLake MCP server is a Model Context Protocol bridge that connects AI assistants — including Claude Desktop, Cursor, Windsurf, and VS Code Copilot — to the Amazon HealthLake API through natural language. It exposes 10 API endpoints as callable tools, such as CreateFHIRDatastore, DeleteFHIRDatastore, DescribeFHIRDatastore, and more. No authentication is required — setup takes approximately 30 seconds. The server uses STDIO transport and can be installed by running npx -y @mcp/amazonaws-com-healthlake. This integration is sourced from the auto Amazon HealthLake OpenAPI specification (v2017-07-01) and has a quality score of 46/99 (fair documentation coverage).

10Endpointstools mapped
NoneAuthopen access
46/99Qualityfair
~30 secSetupno auth

Server Details

Category
Cloud Infrastructure
Authentication
None
Endpoints
10 operations
Transport
STDIO
Spec Version
v2017-07-01
Install Command
npx -y @mcp/amazonaws-com-healthlake

Environment Variables

AMAZON_HEALTHLAKE_API_KEY

Example: your_amazon_healthlake_api_key

Top Endpoints

POST
/#X-Amz-Target=HealthLake.CreateFHIRDatastore

CreateFHIRDatastore

POST
/#X-Amz-Target=HealthLake.DeleteFHIRDatastore

DeleteFHIRDatastore

POST
/#X-Amz-Target=HealthLake.DescribeFHIRDatastore

DescribeFHIRDatastore

POST
/#X-Amz-Target=HealthLake.DescribeFHIRExportJob

DescribeFHIRExportJob

POST
/#X-Amz-Target=HealthLake.DescribeFHIRImportJob

DescribeFHIRImportJob

Own this API?

Verify ownership of this listing to control the description, configuration details, and documentation links. Choose between free manual verification or instant premium placement.

Option 1: Free Verification

Slow manual review. Requires creating a GitHub issue with verified documentation or domain verification.

  • • Verified badge on page
  • • Standard search sorting
  • • 2-3 business days review
Start Free Claim →
Instant & Boosted

Option 2: Featured Upgrade($9/mo)

Instant verification plus premium styling, featured badges, and directory placement boost.

  • • ★ Featured star & amber highlight border
  • • Top of directory search placement
  • • Instant activation via claim token

📖 Detailed MCP Integration Guide

A technical breakdown of capabilities, agent workflows, and security/configuration best practices.

Capabilities & Use Cases
Amazon HealthLake is a fully managed, HIPAA-eligible service from Amazon Web Services (AWS) designed to centralize the management of healthcare data in the cloud. It provides a robust infrastructure for storing, transforming, querying, and analyzing Fast Healthcare Interoperability Resources (FHIR)-formatted data, enabling organizations to build interoperable, analytics-ready healthcare solutions. The core API endpoints facilitate the entire lifecycle of a FHIR datastore, from creation and deletion to monitoring import and export jobs. Typical enterprise use cases include aggregating disparate electronic health records (EHRs) from various sources into a single, queryable repository, running population health analytics to identify trends or at-risk cohorts, enabling clinical research by providing a clean dataset, and supporting compliance initiatives by maintaining a standardized, auditable data lake. Consumer-facing applications, such as patient health portals that aggregate data from multiple providers or personal health record apps, can also leverage HealthLake to provide a unified view of an individual's medical history.
🤖AI Agent Value
Exposing the Amazon HealthLake API as tools within a Model Context Protocol (MCP) server unlocks significant value for AI coding assistants by transforming them into powerful healthcare data engineering and analysis partners. With this integration, an AI agent can directly interact with the complex, schema-rich FHIR data layer, bridging the gap between high-level developer intent and low-level API calls. For instance, a developer can instruct the AI to "set up a new FHIR data store for oncology trial data," and the agent can execute the CreateFHIRDatastore call with the appropriate configuration parameters. This capability drastically accelerates prototyping and reduces the cognitive load on developers, allowing them to focus on application logic rather than infrastructure provisioning or intricate API payload construction. The AI acts as a force multiplier, enabling rapid iteration on data pipelines and analytics workflows within a secure, governed environment.
💬Example Workflows
Practical workflows enabled by this MCP integration include automated data ingestion and transformation tasks. A developer could instruct the AI agent to "start an import job for the latest batch of HL7v2 messages from our lab interface," which would involve the agent invoking the StartFHIRImportJob endpoint with the correct S3 input location and data store ID. Furthermore, the AI can perform dynamic querying and monitoring by responding to commands like "query the data store for all diabetic patients over 50 and summarize the recent lab results," potentially leveraging HealthLake's built-in FHIR search capabilities or triggering an export job for downstream analysis. The agent can also orchestrate administrative tasks, such as "list all active FHIR data stores and their tags to audit our resource costs," using the ListFHIRDatastores and ListTagsForResource endpoints to provide immediate, contextual insights without the developer leaving their integrated development environment.
🛡️Security & Auth
Critical configuration and security practices are paramount when setting up an MCP server for HealthLake. Although the endpoint description specifies "None" for authentication, in practice, every HealthLake API request must be cryptographically signed using AWS Signature Version 4. This requires the MCP server runtime to be configured with valid AWS credentials (an access key ID and secret access key) or, preferably, an IAM role with the minimum necessary permissions. Following the principle of least privilege, the associated IAM policy should strictly grant only the specific HealthLake actions required (e.g., healthlake:CreateFHIRDatastore, healthlake:StartFHIRExportJob) and be scoped to the specific resource ARNs (Amazon Resource Names) of the data stores being managed. Developers must ensure that these credentials are never hard-coded or exposed in client-side code, utilizing secure secret management services like AWS Secrets Manager or environment variables within a trusted execution environment, such as an AWS Lambda function or a dedicated container with an attached IAM role.

Similar APIs

Other APIs in the Cloud Infrastructure category.

Related MCP Server Integrations

Supabase API MCP Setup

Manage Supabase projects, databases, authentication, and storage through your AI agent.

Cloud InfrastructureConfigure →

Cloudflare API MCP Setup

Manage Cloudflare DNS, CDN, Workers, and security settings through your AI agent.

Cloud InfrastructureConfigure →

Vercel API MCP Setup

Deploy projects, manage domains, and monitor deployments through your AI agent.

Cloud InfrastructureConfigure →

DigitalOcean API MCP Setup

The DigitalOcean API is a comprehensive, RESTful interface provided by DigitalOcean, a leading cloud infrastructure provider focused on simplifying cloud computing for developers, startups, and enterprises. It serves as the programmatic backbone for managing the entire DigitalOcean ecosystem, enabling users to provision, configure, and control cloud resources such as Droplets (virtual private servers), Kubernetes clusters, managed databases, networks, storage volumes, and application platforms. Core capabilities include full lifecycle management of these resources, from creation and scaling to monitoring and deletion, mirroring the functionality available in the DigitalOcean control panel. Its primary use cases range from automating infrastructure setup for CI/CD pipelines and enabling infrastructure-as-code practices to supporting dynamic application scaling and resource optimization for SaaS products, e-commerce sites, and development environments. The API is designed for both developers seeking to automate their cloud operations and businesses that require programmable, scalable cloud infrastructure without the complexity of larger hyperscale providers.

Cloud InfrastructureConfigure →

Access Analyzer MCP Setup

The AWS Identity and Access Management Access Analyzer API provides a powerful, policy-as-code service that automatically identifies resources accessible from outside your AWS account or organization. At its core, the service continuously evaluates resource-based policies—such as Amazon S3 bucket policies, AWS Identity and Access Management (IAM) roles, Amazon KMS key policies, and AWS Lambda function policies—using logic-based reasoning to determine which resources grant access to unknown external principals. Its primary use case is for security and compliance teams within enterprises to proactively detect unintended data exposure, enforce least privilege principles, and audit cross-account and cross-service access. The API endpoints allow programmatic control to create, configure, and query analyzers, manage archive rules for storing findings, and generate custom policy documents, making it a foundational tool for automating cloud security posture management at scale.

Cloud InfrastructureConfigure →