InfraLens MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_REGION | Yes | AWS region (e.g., us-east-1) | |
| AWS_PROFILE | No | AWS CLI profile to use for authentication | |
| INFRALENS_LOG_LEVEL | No | Log level (e.g., DEBUG, INFO, WARNING) | |
| INFRALENS_MAX_LOG_EVENTS | No | Maximum number of log events to retrieve | |
| INFRALENS_LOOKBACK_MINUTES | No | How many minutes to look back for events and logs | |
| INFRALENS_REDACT_ACCOUNT_IDS | No | Whether to redact AWS account IDs in output (true/false) |
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 |
|---|---|
| investigate_ecs_serviceD | Run a complete ECS service investigation. |
| inspect_ecs_service_eventsC | Inspect recent ECS service events. |
| inspect_task_definitionD | Inspect a task definition. |
| inspect_target_healthC | Inspect target health for one target group. |
| search_service_logsC | Search service logs in CloudWatch Logs. |
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
Most tools have distinct targets: service events, task definitions, target health, and logs are clearly separate. The potential overlap is 'investigate_ecs_service', which appears to be a comprehensive umbrella that may include the others, but the description helps an agent choose it for a full investigation versus specific checks.
All names follow a verb_noun snake_case pattern with clear objects. The minor inconsistency is the use of both 'investigate' and 'inspect' as near-synonyms, and 'search' for logs, but the style is predictable and readable.
With 5 tools, this set is well-scoped for a focused ECS investigation server. Each tool addresses a clear aspect without unnecessary bloat.
The core investigation workflow covers service-level overview, events, task definitions, target health, and logs. Minor gaps exist such as listing ECS services or metrics, but these can be worked around if the service name is known.