CloudOps MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AWS_REGION | No | AWS region for CloudWatch. | |
| AWS_PROFILE | No | AWS profile name for credentials. | |
| CLOUDOPS_MCP_MODE | No | The mode of the server. Use 'aws' for AWS CloudWatch mode, or omit for fake mode. | fake |
| AWS_DEFAULT_REGION | No | AWS default region for CloudWatch. | |
| CLOUDOPS_MCP_CONFIG | No | Path to the configuration TOML file (required in AWS mode). | |
| CLOUDOPS_MCP_SCENARIO | No | The fake scenario to simulate. Options: healthy, bad_deploy, partial. | healthy |
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_servicesC | List known services and which capabilities are configured for each. |
| get_service_healthB | Provider-reported health signal for a service, never inferred |
| get_recent_deploymentsC | Get recent deployment events for a service, bounded by time/count |
| get_logsB | Get log events for a service, bounded by time range, count, and message length. Message content is opaque and never interpreted. |
| get_metricsA | Get metric series for a service. metric_names must be canonical names from get_services' available_metrics for that service. Always includes deterministic aggregates (min/max/average/last); raw points only when include_points=True, bounded. |
| get_operational_snapshotB | Get a bounded operational snapshot for a service: recent deployments, its configured snapshot metrics, recent logs, and health. Each section reports its own status independently; a failure or unconfigured capability in one section never hides the others. Reports facts only, never a root cause. |
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 6 tools
Each tool targets a distinct observability resource or action: service inventory, deployments, health, logs, metrics, and a composite snapshot. The composite snapshot is explicitly scoped as a bounded aggregation, so it does not blur with the individual tools. No two tools appear to do the same thing.
All six tools use the same get_ verb prefix and snake_case convention, with clear noun phrases (get_services, get_recent_deployments, get_service_health, get_logs, get_metrics, get_operational_snapshot). The pattern is predictable and easy to scan.
Six tools is a well-scoped size for a read-only CloudOps observability server. Each tool covers a distinct monitoring concern without redundant or filler endpoints.
The surface covers core operational data: services, deployments, health, logs, metrics, and a combined snapshot. Minor gaps exist for adjacent operational context such as alerts/incidents or deployment detail views, but core diagnostic workflows are supported.