About this integration
Amazon ElastiCache Management MCP provides elasticache cluster discovery, elasticache service metrics. Run with --readonly and authorized AWS permissions. This is the service management package, separate from the existing Valkey/Memcached data-connection artifacts.
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Package
- awslabs.elasticache-mcp-server
- Last compatibility test
- Not independently tested
Connect your agent
awslabs.elasticache-mcp-serverThe reviewed launcher enters the MCP request loop without an interactive terminal session. Run with --readonly and authorized AWS permissions. This is the service management package, separate from the existing Valkey/Memcached data-connection artifacts. Declared launcher: awslabs.elasticache-mcp-server. See the separately cited authentication and connection facts for prerequisites. Publisher documentation and source reviewed; package and endpoints not executed or independently tested. Initial provisioning and MCP client tool permissions must be configured by the operator.
Capabilities: ElastiCache cluster discovery, ElastiCache service metrics
Connected profiles
Additional details
awslabs.elasticache-mcp-server
Source ↗ · Checked 2026-09-170.2.1
Source ↗ · Checked 2026-09-17The reviewed launcher enters the MCP request loop without an interactive terminal session. Run with --readonly and authorized AWS permissions. This is the service management package, separate from the existing Valkey/Memcached data-connection artifacts.
Source ↗ · Checked 2026-09-17Requires preconfigured AWS machine credentials and IAM permissions for the reviewed operations. Interactive SSO/MFA acquisition is excluded. Python requirement: >=3.10. Additional resource and access prerequisites are stated in the Unattended configuration fact.
Source ↗ · Checked 2026-09-17Use the declared awslabs.elasticache-mcp-server console executable from the awslabs.elasticache-mcp-server Python package with stdio. Apply the flags and configuration described in the Unattended configuration fact. The MCP client must permit the selected tools without interactive approval.
Source ↗ · Checked 2026-09-17Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-17