Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Redis to Claude Code

Let Claude set keys, manage queues, and clear cache against your Redis instance. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Redis to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Redis, you add a Redis MCP server: a small hosted service that exposes Redis's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Redis account. No API keys pasted into config files.

claude mcp add --transport http redis https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Redis once connected?

Full read-write Redis access lets Claude set and update keys, apply TTLs and expirations, push to or pop from lists, manage hashes and sorted sets, and clear stale cache entries against a live instance. The cache and queue work that used to mean a redis-cli session happens through Claude, with approval on destructive commands.

  • Set or update a key with a chosen value and TTL
  • Expire or delete a stale cache key after you approve it
  • Push to or pop from a list to manage a job queue
  • Update fields in a hash or members in a sorted set
  • Increment a counter and read back the new value
  • Inspect a key's type and TTL before changing it

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Redis access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Redis API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Redis changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Redis connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Redis connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Redis account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Redis's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Redis?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Redis account it signs in with. Revoking access is one click in Redis.

More on the Redis connector

Redis connector for claude.aiAmazon Redshift + Claude CodeLooker + Claude CodeMetabase + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us