AWS Infrastructure Operations MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_REGION | Yes | The AWS region, e.g., ap-southeast-1 | |
| AWS_PROFILE | Yes | The AWS profile to use, e.g., mcp-lab-runtime | |
| AWS_LOG_GROUP_PREFIX | No | Optional prefix for log groups, default /aws/mcp-lab | |
| AWS_SSM_DOCUMENT_NAME | No | Optional SSM document name, default mcp-lab-get-nginx-status |
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_instance_healthC | Check EC2 state and AWS system and instance health checks. |
| get_instance_metricsC | Get fixed EC2 performance and status metrics from CloudWatch. |
| get_recent_errorsC | Get recent CloudWatch application and operating-system errors. |
| get_service_statusB | Check the current state of an approved service on an instance. |
| get_service_journalA | Get a bounded nginx systemd journal through a fixed SSM document. |
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 5 tools
Each tool clearly targets a distinct aspect: instance health, metrics, errors, service status, and service journal. There is minimal overlap, and the descriptions specify distinct data sources (CloudWatch, SSM) and resources (EC2 instance vs. service).
All tool names follow a uniform `get_` prefix followed by a descriptive noun phrase, such as `get_instance_health` and `get_service_journal`. The pattern is consistent and predictable, making the API easy to navigate.
With 5 tools, the server is well-scoped for a monitoring-focused infrastructure ops API. Each tool serves a specific operational need, and the count is neither too thin nor bloated for the apparent purpose.
The tool set covers core monitoring needs: health, metrics, errors, service status, and logs. Minor gaps exist (e.g., no list operations, no instance control), but for a read-only diagnostics server, the coverage is solid and workable.