← Explore all mcp servers

CLOUD OPERATIONS / Amazon Web Services

AWS ElastiCache MCP Server

Talks to ElastiCache in an account you administer. It does not invent a cache hit rate.

“The official MCP Server for interacting with AWS ElastiCache control plane.”

01 / THE REASONING

Why this made the selection.

  • The README is the ElastiCache control-plane server, and it sends cache data access to the Valkey or Memcached servers instead.
  • Mutations can be turned off with --readonly, and calls use the process AWS credentials.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • src/elasticache-mcp-server/README.md
  • LICENSE

Our findings

  • README contains awslabs.elasticache-mcp-server@latest.
  • README contains a uvx command.
  • The server is the ElastiCache control plane. Cache contents are out of scope; the README sends those to the Valkey MCP Server or the Memcached MCP Server.
  • It uses standard AWS credentials, including AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_SESSION_TOKEN. An omitted region_name falls back to AWS_REGION or us-west-2.
  • Create, update, and delete stay available unless the client passes --readonly. The README does not make read-only the default.

Not established by this review

  • No AWS API call was made.
  • The server was not started and its tools were not called.
  • A pin does not verify transitive dependencies.
  • No tools/list or tool call was made.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

uvx awslabs.elasticache-mcp-server@latest

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Register the uvx command.
  2. Use credentials for the account you mean.
  3. The one-line command above is the uvx launch in the README client block at this commit, not a separate installer. It was not run.

Before you start

  • uv
  • AWS credentials for the service

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "awslabs.elasticache-mcp-server": {
      "command": "uvx",
      "args": [
        "awslabs.elasticache-mcp-server@latest",
        "--readonly"
      ],
      "env": {
        "AWS_PROFILE": "default",
        "AWS_REGION": "us-west-2",
        "FASTMCP_LOG_LEVEL": "ERROR"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. Server documentation ↗Checked

    https://github.com/awslabs/mcp/blob/49de7cc11ae064b9224f07ae050c612c3f92dd55/src/elasticache-mcp-server/README.md

    Supports: Package name and uvx launch

  2. Repository licence ↗Checked

    https://github.com/awslabs/mcp/blob/49de7cc11ae064b9224f07ae050c612c3f92dd55/LICENSE

    Supports: Redistribution terms

Evidence & Ask