IONOS CLOUD MCP Server

IONOS CLOUD MCP server exists for a simple reason — assistants are far more useful when they can act on IONOS CLOUD directly instead of describing what you should do. Inspect IONOS CLOUD infrastructure via MCP.

What you get

Built and maintained by the IONOS Cloud team. The server runs as a local binary on your workstation, a CI runner, or inside a container. IONOS CLOUD API calls go directly to IONOS over HTTPS; no third-party AI provider sits in the data path.

• Local binary, no proxy — — IONOS CLOUD API calls go directly from your machine to IONOS Cloud. No third-party AI vendor in the data path
• EU-sovereign option — — pair the server with the IONOS CLOUD AI Model Hub and both the API calls and the LLM inference terminate inside IONOS's German data centres. See the Fully Sovereign AI Workflow guide
• Open source — — Apache 2.0. Read the source, audit the behaviour, contribute, or fork

What the assistant can call

Once IONOS CLOUD is connected, these are the calls the assistant has available:

• Smithery — Supported --client values: claude-desktop, claude-code, cursor, vscode, windsurf, cline, continue, gemini-cli, kiro, and others. See the [Smithery

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need 4 environment variables: IONOS_TOKEN, IONOS_S3_ACCESS_KEY, IONOS_S3_SECRET_KEY, IONOS_MCP_TOOL_SCOPE. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

Among the cloud and infrastructure options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. IONOS CLOUD's toolset — Smithery — is a fair guide to whether it matches your workflow. It is maintained by ionos-cloud; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the ionos cloud mcp server does with a few real requests.