Remote MCP

The Clumio MCP server lets an AI client read and manage your Clumio data protection in plain language. MCP (Model Context Protocol) is the standard way AI clients such as Claude, Codex, Kiro, Cursor, Gemini CLI, and Antigravity call outside tools.

Each control plane has its own Clumio MCP server. Your AI client connects to the endpoint of your control plane and sends a Clumio API token with every request. The server acts as the user who owns that token, so it can see and do only what that user's role allows.

With the Clumio MCP server, you can ask your AI client to do the following:

Area What you can do
Documentation Answer questions about Clumio product behavior and troubleshooting from the Clumio documentation.
Inventory and protection Find assets by ARN, ID, or name, see which assets have a policy, check whether backups succeeded, and list alerts.
AWS connections List connected AWS accounts, connect a new account, and update a connection to the latest Clumio template.
Backups and restores List an asset's backups, preview records in a DynamoDB backup, see what S3 continuous backup recorded, start an on-demand backup, and restore an asset.
Policies and protection rules Create, update, assign, unassign, and delete policies. Create, update, and delete protection rules.
S3 protection groups Create, update, and delete protection groups, and see which buckets they back up.
Reports Generate activity, audit, and consumption reports, create and run compliance report configurations, and list the results.
Terraform Generate the Clumio Terraform provider configuration that connects an AWS account or protects an application, for you to review and apply.
Tasks Follow a long-running task, such as a restore, until it finishes.

Supported asset types are EC2, EBS, RDS, DocumentDB, Neptune, DynamoDB, Apache Iceberg tables, and S3 buckets through protection groups.

Getting started

To start using the Clumio MCP server, turn it on for your organization, create a Clumio API token, and add the server to your AI client.

Requirements

  • A Clumio user whose role includes the Security Settings permission, to turn on the Clumio MCP server.

  • A Clumio API token. The MCP server acts as the token's user, so the role of that user decides what your AI client can see and do.

  • An AI client that can connect to a remote MCP server over Streamable HTTP and send a custom request header.

Step 1: Turn on the Clumio MCP server

  1. Go to Administration > Security.

  2. Turn on the Clumio MCP server switch.

The Clumio MCP server is off by default. The change can take up to 10 minutes to apply.

Step 2: Create an API token

Create a personal or service token on the Administration > Access management > API Tokens page. For more information, see API tokens.

Caution

Never paste the API token into a chat with your AI client. Add it to the client's MCP configuration or to an environment variable as the following steps show.

Step 3: Find the endpoint of your control plane

Use the MCP endpoint of the control plane that issued your API token. A token sent to another control plane's endpoint fails with a 401 error.

Clumio portal Control plane MCP endpoint
https://portal.clumio.com US West https://us1.mcp.clumio.com/v1/mcp
https://us2.portal.clumio.com US East https://us2.mcp.clumio.com/v1/mcp
https://canada.portal.clumio.com Canada https://ca1.mcp.clumio.com/v1/mcp
https://eu1.portal.clumio.com Europe https://eu1.mcp.clumio.com/v1/mcp
https://au.portal.clumio.com Australia https://au.mcp.clumio.com/v1/mcp
https://jp.portal.clumio.com Japan https://jp.mcp.clumio.com/v1/mcp
https://ap3.portal.clumio.com Singapore https://ap3.mcp.clumio.com/v1/mcp

The examples on this page use the US West endpoint. Replace it with the endpoint of your control plane.

Step 4: Connect your AI client

Your AI client sends the API token in the X-Clumio-API-Token request header. The Authorization: Bearer <token> header also works.

Add Clumio as a custom connector in claude.ai. The connector also works in Claude Desktop.

  1. Go to Customize > Connectors, select + Add, and then select Add custom connector.

  2. Enter Clumio as the name and the MCP endpoint of your control plane as the URL, and then select Continue.

  3. Under Authentication, select No sign in. Leave the OAuth client fields empty.

  4. Under Request headers, add X-Clumio-API-Token with your API token as the value, and then select Add.

  5. In a chat, turn on the connector under + > Connectors.

claude mcp add --scope user --transport http clumio-mcp \
  https://us1.mcp.clumio.com/v1/mcp \
  --header "X-Clumio-API-Token: $CLUMIO_API_TOKEN"

This command stores the token in ~/.claude.json. Run claude mcp list and check that clumio-mcp shows Connected. Restart any Claude Code session that was already open.

codex mcp add clumio-mcp \
  --url https://us1.mcp.clumio.com/v1/mcp \
  --bearer-token-env-var CLUMIO_API_TOKEN

Codex reads the token from the CLUMIO_API_TOKEN environment variable when it starts. Export the variable in your shell profile, for example ~/.zshrc. Run codex mcp list and check that clumio-mcp shows Bearer token as its authentication.

The Codex CLI, IDE extension, and app share this entry in ~/.codex/config.toml:

[mcp_servers.clumio-mcp]
url = "https://us1.mcp.clumio.com/v1/mcp"
bearer_token_env_var = "CLUMIO_API_TOKEN"

Add the server to ~/.kiro/settings/mcp.json:

{
  "mcpServers": {
    "clumio-mcp": {
      "url": "https://us1.mcp.clumio.com/v1/mcp",
      "headers": {
        "X-Clumio-API-Token": "${CLUMIO_API_TOKEN}"
      }
    }
  }
}

Export CLUMIO_API_TOKEN in the environment that Kiro starts from. Kiro IDE fills in approved variables only. In the Kiro IDE settings, search for Mcp Approved Env Vars and add CLUMIO_API_TOKEN. The Kiro panel lists clumio-mcp under MCP Servers after it connects.

Add the server to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "clumio-mcp": {
      "url": "https://us1.mcp.clumio.com/v1/mcp",
      "headers": {
        "X-Clumio-API-Token": "${env:CLUMIO_API_TOKEN}"
      }
    }
  }
}

Cursor fills in ${env:CLUMIO_API_TOKEN} from the environment, so the token stays out of the file. Export the variable in your shell profile, for example ~/.zshrc, and then restart Cursor. The Cursor editor and the Cursor CLI share this file. Run agent mcp list and check that clumio-mcp shows as connected. In the editor, the server shows under Customize in the sidebar. If it doesn't connect, open the Output panel and select MCP Logs to see why.

gemini mcp add --scope user --transport http \
  --header 'X-Clumio-API-Token: ${CLUMIO_API_TOKEN}' \
  clumio-mcp https://us1.mcp.clumio.com/v1/mcp

The single quotes keep ${CLUMIO_API_TOKEN} as written, so the token stays out of ~/.gemini/settings.json. Gemini CLI reads the token from the environment when it starts, so export the variable in your shell profile. Run gemini mcp list and check that clumio-mcp is listed.

Add the server to ~/.gemini/config/mcp_config.json:

{
  "mcpServers": {
    "clumio-mcp": {
      "serverUrl": "https://us1.mcp.clumio.com/v1/mcp",
      "headers": {
        "X-Clumio-API-Token": "<Clumio API token>"
      }
    }
  }
}

To open the file:

  • In the Antigravity IDE, select … at the top of the agent panel, and then select MCP Servers > Manage MCP Servers > View raw config.

  • In the Antigravity app, go to Customizations > Installed > MCP Servers and select Copy Config File Path to get the file's path.

Replace <Clumio API token> with your API token. Antigravity keeps the token in plain text in this file, so keep the entry in this file only. Don't add it to a project's .agents/mcp_config.json, which can be committed to a repository with the token in it. Restart Antigravity after you save the file. The app and the IDE then list clumio-mcp under MCP Servers. In the Antigravity CLI, run /mcp to see its status.

Clumio hasn't tested other AI clients. To try a client that can add a remote MCP server over Streamable HTTP with a custom request header, such as Visual Studio Code, enter the MCP endpoint of your control plane and add the X-Clumio-API-Token header with your API token.

Step 5: Check the connection

Start a new session in your AI client and ask:

List the Clumio AWS accounts connected to my organization.

A list of your AWS accounts means that the connection and the API token work. You can then try requests like these:

  • Which of my EC2 instances have no Clumio policy?

  • When did the DynamoDB table orders last back up successfully?

  • Restore EBS volume vol-0123456789abcdef0 from its latest backup.

Every change is previewed first, and your AI client is instructed to ask for your approval before running it. Keep your client's approval prompt turned on for tools that change things, such as restore_asset and delete_policy.

Your AI client reads the list of tools once per session. When Clumio adds tools, reconnect or start a new session to see them.

How write tools work

Read tools only look up information. Write tools can change your Clumio configuration or start work such as a backup or a restore. Your AI client picks the tools that answer your request, so you don't need to name a tool yourself.

  • A write tool changes nothing until your AI client confirms the change. Until then, the tool returns a preview of what it would do.

  • For create_policy, update_policy, create_protection_rule, and update_protection_rule, Clumio validates the request during the preview.

  • A confirmed write that runs in the background, such as a restore, returns a task ID. Your AI client follows the task with list_tasks until it finishes.

  • The two Terraform tools, generate_connection_terraform and generate_protection_terraform, are read tools. They generate configuration for you to review and apply, and apply nothing themselves.

Keep your AI client's approval prompt turned on for write tools.

Audit log

Actions that your AI client takes through the Clumio MCP server appear in the Clumio audit log under the API token's user, with the interface Clumio MCP. For more information, see Audit log report.

Troubleshooting

Error Cause and fix
The client fails to connect with 401 CLUMIO_API_TOKEN_INVALID. Claude Code might show Dynamic Client Registration rejected instead. The API token is expired or revoked, or another control plane issued it. Create a new token, or use the endpoint of the control plane that issued the token.
The client fails to connect with 401 CLUMIO_API_TOKEN_REQUIRED. The client sent no token, for example because CLUMIO_API_TOKEN is not set in the environment that the client starts from. Export the variable and restart the client.
Claude Code shows the server as Needs authentication, or Couldn't start sign-in, after you fix the cause. After a failed connection, Claude Code records the server in ~/.claude/mcp-needs-auth-cache.json and tries an OAuth sign-in, which Clumio doesn't offer. Remove the clumio-mcp entry from that file and start a new Claude Code session.
The client fails to connect with 403 and the message "Remote MCP is disabled for this organization." The Clumio MCP server is turned off for your organization. Turn on the switch as Step 1 describes, wait up to 10 minutes, and reconnect.
The client fails to connect with the message "The configured Clumio API token is valid, but Clumio denied the request." Clumio denied the request because of the organization's IP allow list, an inactive license, or the role of the token's user. Check each of these.
A tool call reports a permission error. The role of the token's user doesn't allow that action. Use a token of a user whose role allows it.
A report download link from the chat fails with 401. The link opens only in a browser that is signed in to the Clumio portal. Download the file from the Clumio portal instead.
A request is refused with MCP_RATE_LIMITED. Your AI client sent too many requests in a short time. Wait and try again.

Limitations

  • search_clumio_docs is available in the US West control plane only. In other control planes, your AI client doesn't list the tool.

  • The Clumio MCP server doesn't support GCS or Microsoft SQL Server on EC2, and it doesn't return threat detection results.

  • preview_backup_records supports DynamoDB only. get_continuous_backup_stats supports S3 buckets in protection groups only.

  • No tool supports the following actions. Use the Clumio portal or the Clumio REST API instead.

    • File-level restore from an EC2 backup, and Instant Access endpoints.

    • Updating or deleting a compliance report configuration, and reading a report's contents. The tools return a download link only.

    • Previewing which assets a protection rule change affects.

    • Acknowledging or clearing alerts, and canceling or retrying tasks.

    • Deleting an AWS connection.

    • Managing users, roles, organizational units, API tokens, and alert notification settings.

×

Loading...