All MCP Servers
Web & SearchMCP Registryremote14 toolsD · 33

Memorystore MCP

com.googleapis.memorystore · Updated

Provides tools to manage Memorystore for Valkey instances and backups.

At a glance

Memorystore MCP is an MCP server in the Web & Search category. It is hosted remotely and connects over HTTP, and declares no required credentials. It exposes 14 tools, including list_instances, get_instance and create_instance. It scores D (33/100) on the MCP Skills Hub health score as of Oct 28, 2026.

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install Memorystore MCP in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install Memorystore MCP in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add --transport http memorystore https://memorystore.googleapis.com/mcp
  2. Verify it's connected

    bash
    claude mcp list
  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes (e.g. list_instances, get_instance, create_instance). It discovers them automatically.

What tools does Memorystore MCP expose? (14)

Read from the live server. Click any tool for its input schema.

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Third-party hosted service — Your requests and any data in them are sent to memorystore.googleapis.com.
  • No local execution — Nothing is installed or run on your machine.
  • No source repository — This registry entry does not link to a public repo, so its code cannot be reviewed before you install it.

Client compatibility

Claude Code: NativeClaude Desktop: Via mcp-remoteCursor: NativeCodex CLI: Via mcp-remoteWindsurf: NativeCline: NativeVS Code: Native

Health score

D · 33

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%not measurable

    No commit history available.

  • Adoption20%not measurable

    No usage data available.

  • Transparency20%25%

    1/4: ✗ public source repo, ✗ declared license, ✗ documentation, ✓ discoverable tool list.

  • Provenance15%0%

    No source repository to trace the code back to.

  • Packaging15%75%

    Remote endpoint; authentication requirements not declared.

Maintain Memorystore MCP? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![Memorystore MCP on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/com-googleapis-memorystore-mcp)](https://mcp-skills-hub.vercel.app/mcps/com-googleapis-memorystore-mcp)

Catalog data refreshed . Something wrong? Report it.