Skip to directory

About Memorystore MCP

Google Cloud managed MCP server for Memorystore. Exact tool names and accessible operations depend on the published server reference and configured Google Cloud permissions.

What you can use it for

  • List all Memorystore for Redis instances.
  • Get detailed information about a Memorystore for Redis instance.
  • Get the AUTH string for a Memorystore for Redis instance.
  • Create a Memorystore for Redis instance.
  • Update a Memorystore for Redis instance.
  • Upgrade the version for a Memorystore for Redis instance.
Connection and setup
Hosting
Google-managed remote
Transport
Streamable HTTP
Endpoint
https://redis.googleapis.com/mcp
Authentication
Google Cloud authentication: OAuth 2.0 using Application Default Credentials (ADC) in supported Google clients, or a client OAuth ID/secret or bearer token in compatible third-party clients. The principal needs mcp.tools.call plus the underlying product permissions; API key authentication is only available for services that explicitly support it.

Requirements

  • A Google Cloud project and access to the target product/resource.
  • Enable this MCP service and its underlying Google Cloud API as required by the product guide.
  • An MCP client that supports Streamable HTTP.
  • An identity with the MCP Tool User role (roles/mcp.toolUser) or equivalent mcp.tools.call permission, plus permissions for the underlying product operations.

Setup steps

  1. Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint.
  2. In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it.
  3. Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client.
  4. Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations.
  5. Add redis.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in.
  6. Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset.
Tools 11+

11 stored tools match Memorystore for Redis, not the full Redis Cluster or Valkey servers. get_instance_auth_string reveals a live Redis credential; treat as secret. Lifecycle/import/export/failover tools affect availability/data and may cost.

  • list_instances

    List all Memorystore for Redis instances.

    01
  • get_instance

    Get detailed information about a Memorystore for Redis instance.

    02
  • get_instance_auth_string

    Get the AUTH string for a Memorystore for Redis instance.

    03
  • create_instance

    Create a Memorystore for Redis instance.

    04
  • update_instance

    Update a Memorystore for Redis instance.

    05
  • upgrade_instance

    Upgrade the version for a Memorystore for Redis instance.

    06
  • import_instance

    Import a Redis Database (RDB) snapshot file from Cloud Storage into a Memorystore for Redis instance.

    07
  • export_instance

    Export Redis instance data into a Redis Database (RDB) format file in Cloud Storage.

    08
  • failover_instance

    Initiate a failover of the primary node to the current replica node for a Memorystore for Redis instance that has the STANDARD tier.

    09
  • delete_instance

    Delete a single Memorystore for Redis instance.

    10
  • reschedule_maintenance

    Reschedule maintenance for a Memorystore for Redis instance.

    11

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

Original sources
  • official server catalog

    Official Google Cloud catalog lists this product as an available remote MCP server.

  • official setup guide

    Google Cloud describes remote MCP client setup, Streamable HTTP transport, supported authentication options, and ADC setup.

  • official authentication guide

    Google documents supported identity types and authorization requirements for Google Cloud MCP calls.

  • official source

    Official Google Cloud MCP primary documentation checked 2026-10-28.

  • official source

    Official Google Cloud MCP primary documentation checked 2026-10-28.

Documentation checked 2026-10-28. Connection has not been runtime tested.