# Memorystore for Valkey MCP server

> Manage Memorystore for Valkey instances, maintenance schedules and backups on Google Cloud.

- Listing: https://mcp.tc/i/memorystore-valkey
- Connect: use the server's own URL `https://memorystore.googleapis.com/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Databases & Backend](https://mcp.tc/c/databases)
- Vendor: Google Cloud
- Verified: yes, mcp.tc checked that this is the official server (https://mcp.tc/verify). It says who runs the server, not that it is safe.
- Homepage: <https://docs.cloud.google.com/memorystore/docs/valkey/reference/mcp>

## About

Connects to the Google Cloud Memorystore for Valkey API. You can list, inspect, create, update and delete instances, fetch an instance's certificate authority, reschedule maintenance, and work with backup collections and backups, including creating, exporting and deleting them.

It runs as a hosted streamable HTTP endpoint at memorystore.googleapis.com/mcp. Access uses Google OAuth 2.0 with IAM permissions on your Google Cloud project. Memorystore for Redis has its own separate endpoint.

## What it can do

- List and inspect Valkey instances
- Create, update and delete instances
- Get an instance's certificate authority
- Reschedule maintenance for an instance
- Back up an instance and set a backup TTL
- List and inspect backup collections and backups
- Export backups to a Cloud Storage bucket
- Delete backups

## Tools (14)

- `list_instances`: List Memorystore for Valkey instances, with filter, ordering and paging. (read-only)
- `get_instance`: Get detailed information about an instance. (read-only)
- `create_instance`: Create a Valkey instance.
- `delete_instance`: Delete a Valkey instance. (can modify or delete data)
- `update_instance`: Update a Valkey instance using an update mask.
- `get_certificate_authority`: Get the certificate authority for an instance. (read-only)
- `reschedule_maintenance`: Reschedule maintenance for an instance.
- `list_backup_collections`: List backup collections. (read-only)
- `get_backup_collection`: Get details of a backup collection. (read-only)
- `list_backups`: List backups. (read-only)
- `get_backup`: Get details of a backup. (read-only)
- `delete_backup`: Delete a backup. (can modify or delete data)
- `export_backup`: Export a backup to a Cloud Storage bucket.
- `backup_instance`: Create a backup of an instance.

## Example prompts

- "List all Memorystore for Valkey instances in my project"
- "Back up the Valkey instance named cache-prod"
- "Export my latest Valkey backup to the bucket my-backups"
- "Reschedule maintenance for instance cache-staging to next Sunday"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http memorystore-valkey https://memorystore.googleapis.com/mcp
```

2. Start Claude Code, type `/mcp`, pick **memorystore-valkey** and choose **Authenticate**. A browser window opens for the Google Cloud sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Settings → Connectors** and click **Add custom connector**.

2. Name it **Memorystore for Valkey** and paste this URL:

```url
https://memorystore.googleapis.com/mcp
```

3. Click **Add**, then **Connect**, and sign in when Google Cloud asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Memorystore%20for%20Valkey&connectorUrl=https%3A%2F%2Fmemorystore.googleapis.com%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://memorystore.googleapis.com/mcp` and click **Add**.

3. Click **Connect** and sign in when Google Cloud asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, open **Settings → Security and login** and turn on **Developer mode**.

2. Go to `chatgpt.com/plugins` and click **+** to create an app for a remote MCP server.

3. Paste `https://memorystore.googleapis.com/mcp` as the server URL and choose **OAuth**. ChatGPT sends you to Google Cloud to sign in.

Developer mode is available on the web for Plus, Pro, Business, Enterprise and Education accounts.

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=memorystore-valkey&config=eyJ1cmwiOiJodHRwczovL21lbW9yeXN0b3JlLmdvb2dsZWFwaXMuY29tL21jcCJ9>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "memorystore-valkey": {
      "url": "https://memorystore.googleapis.com/mcp"
    }
  }
}
```

Cursor shows **Needs login** next to the server. Click it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=memorystore-valkey&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmemorystore.googleapis.com%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"memorystore-valkey","type":"http","url":"https://memorystore.googleapis.com/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "memorystore-valkey": {
      "type": "http",
      "url": "https://memorystore.googleapis.com/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "memorystore-valkey": {
      "serverUrl": "https://memorystore.googleapis.com/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add memorystore-valkey --url https://memorystore.googleapis.com/mcp
codex mcp login memorystore-valkey
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.memorystore-valkey]
url = "https://memorystore.googleapis.com/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http memorystore-valkey https://memorystore.googleapis.com/mcp
```

Then, inside Gemini CLI, run `/mcp auth memorystore-valkey` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "memorystore-valkey": {
      "type": "http",
      "url": "https://memorystore.googleapis.com/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://memorystore.googleapis.com/mcp`.

## Details

- Server version: ESF
- MCP protocol version: 2025-11-25
- Last checked: 2026-10-03 (reachable)
- Listed: 2026-10-03
- Updated: 2026-10-03

---
Source: https://mcp.tc/i/memorystore-valkey (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
