Cloud
Beta

Configure the Redpanda Cloud Management MCP Server

After installing the Redpanda Cloud Management MCP Server, you can configure it for different AI clients, customize security settings, and troubleshoot common issues.

After reading this page, you will be able to:

  • Configure MCP clients

  • Enable delete operations safely

  • Troubleshoot common configuration issues

Prerequisites

  • At least version 25.2.3 of rpk installed on your local machine

  • Access to a Redpanda Cloud account

  • An MCP-compatible AI client such as Claude, Claude Code, or another tool that supports MCP

The MCP server exposes Redpanda Cloud API endpoints for both the Control Plane and the Data Plane. Available endpoints depend on your rpk version. Keep rpk updated to access new Redpanda Cloud features through the MCP server. New MCP endpoints are documented in Redpanda release notes.

Install the integration for Claude or Claude Code

For some supported clients, you can install and configure the MCP integration using the rpk cloud mcp install command. For Claude and Claude Code, run one of these commands:

# Choose one
rpk cloud mcp install --client claude
rpk cloud mcp install --client claude-code

If you need to update the integration, re-run the install command for your client.

Configure other MCP clients manually

If you’re using another MCP-compatible client, manually configure it to use the Redpanda Cloud Management MCP Server. Follow these steps:

Add an MCP server entry to your client’s configuration (example shown in JSON). Adjust paths for your system.

"mcpServers": {
  "redpandaCloud": {
    "command": "rpk",
    "args": [
      "--config",
      "<path-to-rpk.yaml>", (1)
      "cloud",
      "mcp",
      "stdio"
    ]
  }
}
1 Optional: The --config flag lets you target a specific rpk.yaml, which contains the configuration for connecting to your cluster. Always use the same configuration path as you used for rpk cloud login to ensure it has your token. Default paths vary by operating system. See the rpk cloud login reference for the default paths.

You can also start the server manually in a terminal to observe logs and troubleshoot.

Enable delete operations

The server disables destructive operations by default. To allow delete operations, add --allow-delete to the MCP server invocation.

Enabling delete operations permits actions like deleting topics or clusters. Restrict access to your AI client and double-check prompts.

  • Auto-configured clients

  • Manual configuration example

# Choose one
rpk cloud mcp install --client claude --allow-delete
rpk cloud mcp install --client claude-code --allow-delete
"mcpServers": {
  "redpandaCloud": {
    "command": "rpk",
    "args": [
      "cloud",
      "mcp",
      "stdio",
      "--allow-delete"
    ]
  }
}

Specify configuration file paths

All rpk commands accept a --config flag, which lets you specify the exact rpk.yaml configuration file to use for connecting to your Redpanda cluster. This flag overrides the default search path and ensures that the command uses the credentials and settings from the file you provide.

Always use the same configuration path for both rpk cloud login and any MCP server setup or install commands to avoid authentication issues. By default, rpk searches for config files in standard locations depending on your operating system. See the reference documentation for details. Use an absolute path and make sure your user has read and write permissions.

The rpk configuration file contains your Redpanda Cloud token. Keep the file secure and never share it.

For example, if you want to use a custom config path, specify it for both login and the MCP install command:

rpk cloud login --config /Users/<user>/my-rpk-config.yaml
rpk cloud mcp install --client claude --config /Users/<user>/my-rpk-config.yaml

Or for Claude Code:

rpk cloud login --config /Users/<user>/my-rpk-config.yaml
rpk cloud mcp install --client claude-code --config /Users/<user>/my-rpk-config.yaml

Remove the MCP server

To remove the MCP server, delete or disable the mcpServers.redpandaCloud entry in your client’s config (steps vary by client).

Security considerations

  • Avoid enabling --allow-delete unless required.

  • For most local use cases, such as with Claude or Claude Code, log in with your personal Redpanda Cloud user account for better security and easier management.

  • If you are deploying the MCP server as part of an application or shared environment, consider using a service account with tailored roles. To log in as a service account, use:

    rpk cloud login --client-id <service-account-client-id> --client-secret <service-account-client-secret> --save

  • Regularly review and rotate your credentials.

Troubleshooting

Verify your installation

  1. Make sure you are using at least version 25.2.3 of rpk.

  2. If you see authentication errors, run rpk cloud login again.

  3. Ensure you installed for the right client:

    rpk cloud mcp install --client claude
# or
rpk cloud mcp install --client claude-code

  4. If using another MCP client, verify your mcpServers.redpandaCloud entry (paths, JSON syntax, and args order).

  5. Start the server manually using the rpk cloud mcp stdio command (one-time login required) to verify connectivity to Redpanda Cloud endpoints:

    rpk cloud login
rpk cloud mcp stdio

    1. Send the following newline-delimited JSON-RPC messages (each on its own line):

      {"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{"roots":{},"sampling":{},"elicitation":{}},"clientInfo":{"name":"ManualTest","version":"0.1.0"}}}
{"jsonrpc":"2.0","method":"notifications/initialized"}
{"jsonrpc":"2.0","id":2,"method":"tools/list"}

      Expected response shapes (examples):

      {"jsonrpc":"2.0","id":1,"result":{"capabilities":{...}}}
{"jsonrpc":"2.0","id":2,"result":{"tools":[{"name":"...","description":"..."}, ...]}}

    2. Stop the server with Ctrl+C.

Client can’t find the MCP server

  • Re-run the install for your MCP client.

  • Confirm the path in --config /path/to/rpk.yaml exists and is readable.

  • Double-check your client’s configuration format and syntax.

Unauthorized errors or token errors

Your capabilities depend on your Redpanda Cloud account permissions. If an operation fails with a permissions error, contact your account admin.

  • Run rpk cloud login to refresh the token.

  • Ensure your account has the necessary permissions for the requested operation.

Deletes not working

  • The server disables delete operations by default. Add --allow-delete to the server invocation (auto or manual configuration) and restart the client.

  • For auto-configured clients, you may need to edit the generated config or re-run the install command and adjust the entry.