AWS Health MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level (DEBUG, INFO, WARNING) | INFO |
| AWS_REGION | No | Region (Health API is us-east-1 only) | us-east-1 |
| AWS_PROFILE | No | AWS credentials profile | |
| HEALTH_API_TIMEOUT | No | API timeout in seconds | 30 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_service_healthA | Get current AWS service health events. Returns active and upcoming AWS health events with descriptions and timelines. Consider summarize_health_events first: this returns full descriptions and can be very large on a busy account. Args: regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2']. Example prompts:
|
| get_affected_entitiesA | Get affected entities for all open AWS health events. Shows resources impacted by active health events, grouped by event and status. Example prompts:
|
| get_service_eventsA | Get health events for a specific AWS service. Args: service: The AWS service name (e.g., 'EC2', 'RDS', 'LAMBDA'). Case insensitive. Use list_event_types to discover the codes AWS Health uses. regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2']. Example prompts:
|
| get_completed_eventsA | Get completed/closed health events. Args: service: Optional. The AWS service name to filter by. Case insensitive. regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2']. Example prompts:
|
| get_scheduled_changesA | Get all scheduled changes/maintenance events across AWS services. Returns upcoming maintenance windows, planned updates, and infrastructure improvements. Args: regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2']. Example prompts:
|
| get_org_health_eventsA | Get health events across your AWS Organization. If no arguments are provided, returns all active org health events. Args: service: Optional. The AWS service name to filter by. Case insensitive. account_id: Optional. The AWS account ID to filter events for. status: Optional. 'active' (default) or 'closed'. regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2']. Example prompts:
|
| get_org_service_healthA | Get current AWS service health events across your organization. Provides a comprehensive overview of active health events across all accounts in your AWS Organization. Example prompts:
|
| get_org_affected_entitiesA | Get affected entities for AWS health events across your organization. Args: account_id: Optional. The AWS account ID to filter events for. event_arn: Optional. The ARN of a specific event to get details for. Example prompts:
|
| get_org_service_eventsA | Get health events for a specific AWS service across your organization. Args: service: The AWS service name (e.g., 'EC2', 'RDS', 'LAMBDA'). Case insensitive. regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2']. Example prompts:
|
| get_org_account_eventsA | Get health events for a specific AWS account in your organization. Args: account_id: The 12-digit AWS account ID. regions: Optional. Restrict to these AWS regions, e.g. ['us-west-2']. Example prompts:
|
| get_org_scheduled_changesA | Get scheduled changes/maintenance events across your AWS Organization. Returns upcoming maintenance affecting accounts in your organization. Example prompts:
|
| get_event_detailsA | Get the full detail of specific AWS health events by ARN. Use this to drill into events surfaced by the listing tools, instead of pulling every description for every event. Args: event_arns: One or more event ARNs, as returned by the listing tools. Example prompts:
|
| summarize_health_eventsA | Count active AWS health events without returning their descriptions. A cheap overview for "is anything wrong?" questions. Listing tools return full descriptions and can run to tens of thousands of tokens; this returns counts only. Args: group_by: One of 'service', 'status', 'category' or 'region'. include_closed: Include resolved events as well as open/upcoming ones. Example prompts:
|
| count_affected_entitiesA | Count the resources affected by events, without listing them. Use this before the entity-listing tools when an event could touch thousands of resources. Args: event_arns: One or more event ARNs. Example prompts:
|
| list_affected_accountsB | List the organization accounts affected by a single health event. Args: event_arn: The ARN of an organization health event. Example prompts:
|
| list_event_typesA | List the event types AWS Health can report, optionally for one service. Also the way to discover valid service names: the service codes AWS Health uses do not always match the marketing name (Step Functions is 'STATES', EventBridge is 'EVENTS'). Args: service: Optional. Restrict to one AWS service. Case insensitive. category: Optional. One of 'issue', 'accountNotification', 'scheduledChange', 'investigation'. Example prompts:
|
| find_events_for_resourcesA | Find which health events affect specific resources of yours. Answers "is my instance / cluster / database affected by anything?". Matching goes through DescribeAffectedEntities, where entity values match exactly. The equivalent filter on DescribeEvents cannot be used for this: it also returns events that have no entities at all, so a resource ID that exists nowhere still comes back with matches. Args: entity_values: Resource identifiers, e.g. ['i-1234567890abcdef0']. include_closed: Also search resolved events, not just open/upcoming. Example prompts:
|
| check_health_accessA | Diagnose whether this server can actually reach the AWS Health API. Reports the calling identity, whether the account's support plan allows Health API access, and whether organization view is enabled. Run this first when other tools return access errors. Example prompts:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
There are systematic org/non-org pairs (get_service_health vs get_org_service_health, get_affected_entities vs get_org_affected_entities, etc.) which are nameable-apart, but the fuzzy boundaries between get_service_health and get_service_events, and between the several overlapping event-listing tools, create real misselection risk.
All names follow a consistent snake_case verb_noun pattern (get_, list_, count_, summarize_, find_, check_) with predictable prefixes for org-scoped variants.
18 tools is at the upper end but justified by the read-only domain spanning single-account, org-wide, entity, and summary operations. It is slightly heavy but each tool earns a place.
The surface covers listing, drilling into details, affected entities, counts, summaries, event-type discovery, org-wide views, and an access diagnostic — strong lifecycle coverage for a read-only API. Minor gaps around pagination/continuation handling keep it from a 5.