Your coding agent can already write code against Redis. Managing the Redis Cloud account behind that code still means leaving the chat for the console or the API.
The Redis Cloud remote Model Context Protocol (MCP) server closes that gap. From the same chat, your AI agent manages your Redis Cloud resources (such as subscriptions, databases, and Agent Memory stores) through a single entry point that Redis hosts at https://cloud.mcp.redis.io/mcp. New Redis Cloud capabilities arrive through the same entry point, with no change on your side.
No local server. No API client to write. No tool list filling up your agent's context.
Here's what it does and how to connect.
How it works
Redis runs the Redis Cloud remote MCP server for you and your agent just connects over standard MCP. The server speaks the protocol over Streamable HTTP at one endpoint, so there's no SDK or plugin. Any MCP client that can send custom request headers works.
Each request goes through three steps:
- Your client calls the endpoint. It sends your API account key and API user key as headers on every request. With API keys, there's no OAuth flow to script and no token to refresh.
- The server checks the keys and routes the call. Each Redis Cloud product area, such as databases or Agent Memory, has its own tools. The server puts them behind one endpoint, one set of keys, and one tool catalog, then passes each call to the tool that owns it.
- The tool calls Redis Cloud with your own credentials. The server has no Redis Cloud credentials of its own, so every call runs with your keys and your permissions.
The server uses standard MCP features: tools for actions, elicitation for confirmations, and MCP Apps for interactive views in clients that support them. Tools return structured results with fixed fields, so your agent reads values instead of parsing free text.
The server manages the resources in your Redis Cloud account. To read or write the data inside a database, use Redis MCP, which connects to a database directly.
It also works with the Redis Docs MCP server at redis.io/mcp. The Redis Docs server tells your agent how Redis works and the Redis Cloud remote server acts on your Redis Cloud account.
If you'd rather run a server yourself, Redis also publishes a local Redis Cloud MCP server.
Connect your client
The quickest way to set up is from the agents page in the Redis Cloud console. Pick your agent, and the page shows the configuration to copy and links to where you create your API keys.
To set it up by hand, you need a Redis Cloud API account key and an API user key. Every client uses the same three settings:
In Claude Code, add the server with one command:
In Codex, set the REDIS_CLOUD_API_KEY and REDIS_CLOUD_SECRET_KEY environment variables to your API account key and API user key, then add the server to ~/.codex/config.toml:
Any other client works if it supports Streamable HTTP and custom request headers. The docs have set up steps for more clients. To check the connection, ask your agent to list your Redis Cloud subscriptions.
What you can ask
You ask in your own words, and your agent finds the right Redis Cloud tool. For example:
- "List my subscriptions and their databases."
- "Create a free database on AWS in us-east-1."
- "Which regions can I use on Google Cloud?"
- "Show the metrics for my Agent Memory store."
Keep your agent’s context small
The server uses progressive disclosure, so it doesn't fill up your agent's context. Your agent sees only a small, fixed set of entry tools. When it needs to do something, it searches for the matching Redis Cloud tool, gets that tool's full definition, and then calls it. The definitions of every other tool don’t load into your agent’s context, no matter how many tools the server has.
The same design means new tools show up without any change to your client setup. The docs list what the server can do today.
Safe by default
The server can do only what your API user key can do in Redis Cloud. A key for a read-only user can only read, the key's CIDR allow list still applies, and payment card details are masked.
Changes that cost money or are hard to undo ask for your confirmation in your client, through MCP elicitation. To delete a resource, you type its name.
If you decline or cancel, nothing changes, and the server never retries a change by itself. If a change times out, check the resource before you try again.
Get started
Open the agents page in the Redis Cloud console. It walks you through every step: creating an API key, saving it in your environment, adding the server to your agent, and trying your first request.
The full setup, limits, and troubleshooting are in the Redis Cloud remote MCP server docs.












