IONOS CLOUD MCP Server

by ionos-cloudio.github.ionos-cloud/ionoscloud-mcpv1.1.1

Inspect and manage IONOS CLOUD infrastructure via MCP. Writes are opt-in and off by default.

8Dockerstdioofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Active16d ago

Install IONOS CLOUD MCP server

claude mcp add ionoscloud -e IONOS_TOKEN='<ionos-token>' -e IONOS_S3_ACCESS_KEY='<ionos-s3-access-key>' -e IONOS_S3_SECRET_KEY='<ionos-s3-secret-key>' -- docker run -i --rm -e IONOS_TOKEN -e IONOS_S3_ACCESS_KEY -e IONOS_S3_SECRET_KEY ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.1

{
  "mcpServers": {
    "ionoscloud": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "IONOS_TOKEN",
        "-e",
        "IONOS_S3_ACCESS_KEY",
        "-e",
        "IONOS_S3_SECRET_KEY",
        "ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.1"
      ],
      "env": {
        "IONOS_TOKEN": "<ionos-token>",
        "IONOS_S3_ACCESS_KEY": "<ionos-s3-access-key>",
        "IONOS_S3_SECRET_KEY": "<ionos-s3-secret-key>"
      }
    }
  }
}

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project).

{
  "mcpServers": {
    "ionoscloud": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "IONOS_TOKEN",
        "-e",
        "IONOS_S3_ACCESS_KEY",
        "-e",
        "IONOS_S3_SECRET_KEY",
        "ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.1"
      ],
      "env": {
        "IONOS_TOKEN": "<ionos-token>",
        "IONOS_S3_ACCESS_KEY": "<ionos-s3-access-key>",
        "IONOS_S3_SECRET_KEY": "<ionos-s3-secret-key>"
      }
    }
  }
}

Settings → Developer → Edit Config (claude_desktop_config.json), then restart.

{
  "servers": {
    "ionoscloud": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "IONOS_TOKEN",
        "-e",
        "IONOS_S3_ACCESS_KEY",
        "-e",
        "IONOS_S3_SECRET_KEY",
        "ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.1"
      ],
      "env": {
        "IONOS_TOKEN": "<ionos-token>",
        "IONOS_S3_ACCESS_KEY": "<ionos-s3-access-key>",
        "IONOS_S3_SECRET_KEY": "<ionos-s3-secret-key>"
      }
    }
  }
}

Add to .vscode/mcp.json in your workspace.

{
  "mcpServers": {
    "ionoscloud": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "IONOS_TOKEN",
        "-e",
        "IONOS_S3_ACCESS_KEY",
        "-e",
        "IONOS_S3_SECRET_KEY",
        "ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.1"
      ],
      "env": {
        "IONOS_TOKEN": "<ionos-token>",
        "IONOS_S3_ACCESS_KEY": "<ionos-s3-access-key>",
        "IONOS_S3_SECRET_KEY": "<ionos-s3-secret-key>"
      }
    }
  }
}

Add to ~/.codeium/windsurf/mcp_config.json.

Configuration

Variable	Required	Secret	Description
IONOS_TOKEN	yes	yes	IONOS CLOUD API token (required for all products except Object Storage)
IONOS_S3_ACCESS_KEY	—	yes	S3 access key for IONOS Object Storage
IONOS_S3_SECRET_KEY	—	yes	S3 secret key for IONOS Object Storage
IONOS_MCP_LOAD_MODE	—	—	Tool registration strategy (the --load-mode flag overrides this). 'eager' (default): register all tools at startup. 'lazy': defer Compute and Object Storage behind 'ionos_load_compute_tools' / 'ionos_load_objectstorage_tools' sentinel tools (requires MCP client support for notifications/tools/list_changed). 'dynamic' (alias 'search'): expose only the ionos_search_tools / ionos_describe_tools / ionos_call_tool meta-tools and browse the full catalog through them — for clients with hard tool caps and no tool search of their own (Cursor, Windsurf).
IONOS_MCP_TOOL_SCOPE	—	—	Opt in to write operations. Unset (default) leaves the server read-only: only list_/get_/head_ tools are registered. 'write' additionally registers create_/update_ tools and the non-disruptive actions (start_, resume_, attach_, assign_); 'destructive' also registers delete_ and the disruptive actions (stop_, reboot_, suspend_, upgrade_, restore_, detach_, recreate_, import_) and implies 'write'. Comma-separated, case-insensitive, hierarchical; unrecognised values stay read-only. WARNING: enabling this lets an AI model provision, modify and delete billable resources in a live IONOS CLOUD account. Every create and delete requires a two-phase confirmation, but that cannot stop a client configured to approve tool calls automatically. Leave unset unless writes are needed.

Freshness

Active — last maintenance signal 16d ago. The newest of the signals below sets the band.

Last commit (default branch)
2026-09-23 · 16d ago · GitHub
Latest release
2026-09-17 · 22d ago · GitHub · v1.1.1
Package published
no data · npm/PyPI
Registry entry updated
2026-09-17 · 22d ago · official registry · v1.1.1

FAQ

›How do I install the IONOS CLOUD MCP server in Claude Code?

Run: claude mcp add ionoscloud -e IONOS_TOKEN='<ionos-token>' -e IONOS_S3_ACCESS_KEY='<ionos-s3-access-key>' -e IONOS_S3_SECRET_KEY='<ionos-s3-secret-key>' -- docker run -i --rm -e IONOS_TOKEN -e IONOS_S3_ACCESS_KEY -e IONOS_S3_SECRET_KEY ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.1. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does IONOS CLOUD require an API key?

Yes. It expects IONOS_TOKEN, IONOS_S3_ACCESS_KEY, IONOS_S3_SECRET_KEY, of which 3 are secrets.

›Can I use IONOS CLOUD as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is IONOS CLOUD in the official MCP registry?

Yes, as io.github.ionos-cloud/ionoscloud-mcp.