IONOS CLOUD MCP Server — Claude Code MCP server
Connects IONOS CLOUD to an AI assistant for infrastructure inspection and resource management, with write actions disabled until you opt in.
claude mcp add --env IONOS_TOKEN=<IONOS_TOKEN> --env IONOS_S3_ACCESS_KEY=<IONOS_S3_ACCESS_KEY> --env IONOS_S3_SECRET_KEY=<IONOS_S3_SECRET_KEY> --env IONOS_MCP_LOAD_MODE=<IONOS_MCP_LOAD_MODE> --env IONOS_MCP_TOOL_SCOPE=<IONOS_MCP_TOOL_SCOPE> --transport stdio ionos-cloud-mcp-server -- docker run -i --rm -e IONOS_TOKEN -e IONOS_S3_ACCESS_KEY -e IONOS_S3_SECRET_KEY -e IONOS_MCP_LOAD_MODE -e IONOS_MCP_TOOL_SCOPE ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.2What IONOS CLOUD MCP Server does
IONOS CLOUD MCP Server exposes IONOS CLOUD account data to an MCP-compatible assistant. It can inspect Compute Engine, Kubernetes, Object Storage, DNS, Billing, Certificate Manager and Activity Log resources, including servers, clusters, buckets, records, invoices and events. The default setup keeps write tools off.
It runs as a local process or container, while API requests travel directly to IONOS over HTTPS. The Docker setup passes IONOS_TOKEN, IONOS_S3_ACCESS_KEY, IONOS_S3_SECRET_KEY, IONOS_MCP_LOAD_MODE and IONOS_MCP_TOOL_SCOPE. Create, update and delete actions require an explicit scope and confirmation flow. Without IONOS_TOKEN, the server cannot connect to the IONOS CLOUD account.
What it helps with
- inspect IONOS CLOUD servers and network resources
- check Kubernetes clusters and node pools
- review DNS zones and records
- trace billing, traffic and resource usage
- manage certificates after enabling writes
Example prompts for the agent
- Show the servers in my IONOS CLOUD account with their details.
- Review the DNS zones and records for this account.
- Summarize IONOS CLOUD invoices, traffic, and resource usage.
How to install IONOS CLOUD MCP Server
Platform CLI
claude mcp add --env IONOS_TOKEN=<IONOS_TOKEN> --env IONOS_S3_ACCESS_KEY=<IONOS_S3_ACCESS_KEY> --env IONOS_S3_SECRET_KEY=<IONOS_S3_SECRET_KEY> --env IONOS_MCP_LOAD_MODE=<IONOS_MCP_LOAD_MODE> --env IONOS_MCP_TOOL_SCOPE=<IONOS_MCP_TOOL_SCOPE> --transport stdio ionos-cloud-mcp-server -- docker run -i --rm -e IONOS_TOKEN -e IONOS_S3_ACCESS_KEY -e IONOS_S3_SECRET_KEY -e IONOS_MCP_LOAD_MODE -e IONOS_MCP_TOOL_SCOPE ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.2Replace <…> with your own values
Platform CLI
codex mcp add ionos-cloud-mcp-server --env IONOS_TOKEN=<IONOS_TOKEN> --env IONOS_S3_ACCESS_KEY=<IONOS_S3_ACCESS_KEY> --env IONOS_S3_SECRET_KEY=<IONOS_S3_SECRET_KEY> --env IONOS_MCP_LOAD_MODE=<IONOS_MCP_LOAD_MODE> --env IONOS_MCP_TOOL_SCOPE=<IONOS_MCP_TOOL_SCOPE> -- docker run -i --rm -e IONOS_TOKEN -e IONOS_S3_ACCESS_KEY -e IONOS_S3_SECRET_KEY -e IONOS_MCP_LOAD_MODE -e IONOS_MCP_TOOL_SCOPE ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.2Replace <…> with your own values
Config file
{
"mcpServers": {
"ionos-cloud-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"IONOS_TOKEN",
"-e",
"IONOS_S3_ACCESS_KEY",
"-e",
"IONOS_S3_SECRET_KEY",
"-e",
"IONOS_MCP_LOAD_MODE",
"-e",
"IONOS_MCP_TOOL_SCOPE",
"ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.2"
],
"env": {
"IONOS_TOKEN": "<IONOS_TOKEN>",
"IONOS_S3_ACCESS_KEY": "<IONOS_S3_ACCESS_KEY>",
"IONOS_S3_SECRET_KEY": "<IONOS_S3_SECRET_KEY>",
"IONOS_MCP_LOAD_MODE": "<IONOS_MCP_LOAD_MODE>",
"IONOS_MCP_TOOL_SCOPE": "<IONOS_MCP_TOOL_SCOPE>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"ionos-cloud-mcp-server": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"IONOS_TOKEN",
"-e",
"IONOS_S3_ACCESS_KEY",
"-e",
"IONOS_S3_SECRET_KEY",
"-e",
"IONOS_MCP_LOAD_MODE",
"-e",
"IONOS_MCP_TOOL_SCOPE",
"ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.2"
],
"env": {
"IONOS_TOKEN": "<IONOS_TOKEN>",
"IONOS_S3_ACCESS_KEY": "<IONOS_S3_ACCESS_KEY>",
"IONOS_S3_SECRET_KEY": "<IONOS_S3_SECRET_KEY>",
"IONOS_MCP_LOAD_MODE": "<IONOS_MCP_LOAD_MODE>",
"IONOS_MCP_TOOL_SCOPE": "<IONOS_MCP_TOOL_SCOPE>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e IONOS_TOKEN=<IONOS_TOKEN> -e IONOS_S3_ACCESS_KEY=<IONOS_S3_ACCESS_KEY> -e IONOS_S3_SECRET_KEY=<IONOS_S3_SECRET_KEY> -e IONOS_MCP_LOAD_MODE=<IONOS_MCP_LOAD_MODE> -e IONOS_MCP_TOOL_SCOPE=<IONOS_MCP_TOOL_SCOPE> ionos-cloud-mcp-server docker run -i --rm -e IONOS_TOKEN -e IONOS_S3_ACCESS_KEY -e IONOS_S3_SECRET_KEY -e IONOS_MCP_LOAD_MODE -e IONOS_MCP_TOOL_SCOPE ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.2Replace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about IONOS CLOUD MCP Server
How do I install IONOS CLOUD MCP Server in Claude Code?
Run `claude mcp add --env IONOS_TOKEN=<IONOS_TOKEN> --env IONOS_S3_ACCESS_KEY=<IONOS_S3_ACCESS_KEY> --env IONOS_S3_SECRET_KEY=<IONOS_S3_SECRET_KEY> --env IONOS_MCP_LOAD_MODE=<IONOS_MCP_LOAD_MODE> --env IONOS_MCP_TOOL_SCOPE=<IONOS_MCP_TOOL_SCOPE> --transport stdio ionos-cloud-mcp-server -- docker run -i --rm -e IONOS_TOKEN -e IONOS_S3_ACCESS_KEY -e IONOS_S3_SECRET_KEY -e IONOS_MCP_LOAD_MODE -e IONOS_MCP_TOOL_SCOPE ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.2`.
What does IONOS CLOUD MCP Server do?
It gives an AI assistant tools for inspecting IONOS CLOUD account resources and usage. Write actions stay disabled in the default setup.
Can it create or delete IONOS CLOUD resources?
Yes, after you set IONOS_MCP_TOOL_SCOPE. Create and delete actions use a preview, a one-time token, and an execution step.
