IONOS CLOUD MCP Server MCP Server
io.github.ionos-cloud/ionoscloud-mcp
What this kind of tool is for
- Automate a build, test, or deployment step you repeat by hand.
- Review or refactor code in an existing repository without leaving your agent.
- Bridge an internal service or CLI into the agent toolset.
How to compare servers like this
- Scope of control:
- Repos and CI are hard to undo; prefer tools that ask before anything irreversible.
- Environment fit:
- Match the runtime it expects (Node, Python, a container) to what you actually run.
- Maintenance signal:
- Check the last-commit date — dev tooling that lags upstream breaks first.
- Config surface:
- Prefer tools whose environment-variable or config keys are documented plainly.
This page carries your copy-paste config: pick your MCP client in the install section on this page and use the copy button.
What is the IONOS CLOUD MCP Server MCP server?
Inspect and manage IONOS CLOUD infrastructure via MCP. Writes are opt-in and off by default.
How to install IONOS CLOUD MCP Server
Copy-paste configuration for popular MCP clients.
IONOS_TOKENrequiredsecretIONOS CLOUD API token (required for all products except Object Storage)
IONOS_S3_ACCESS_KEYsecretS3 access key for IONOS Object Storage
IONOS_S3_SECRET_KEYsecretS3 secret key for IONOS Object Storage
IONOS_MCP_LOAD_MODETool 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_SCOPEOpt 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.
{
"mcpServers": {
"ionoscloud-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/ionos-cloud/ionoscloud-mcp:1.1.1"
],
"env": {
"IONOS_TOKEN": "<YOUR_IONOS_TOKEN>",
"IONOS_S3_ACCESS_KEY": "<YOUR_IONOS_S3_ACCESS_KEY>",
"IONOS_S3_SECRET_KEY": "<YOUR_IONOS_S3_SECRET_KEY>",
"IONOS_MCP_LOAD_MODE": "<YOUR_IONOS_MCP_LOAD_MODE>",
"IONOS_MCP_TOOL_SCOPE": "<YOUR_IONOS_MCP_TOOL_SCOPE>"
}
}
}
}Related MCP servers

CLIO Chronolog
22 MCP servers for scientific computing, HPC, and research data analysis.

CLIO Compression
AI-powered compression utilities for scientific computing workflows via Model Context Protocol

CLIO Darshan
Darshan I/O profiler MCP server for analyzing I/O trace files and performance metrics

CLIO Jarvis
22 MCP servers for scientific computing, HPC, and research data analysis—unified AI interface for HDF5, Slurm, ArXiv, and more.

CLIO Adios
Access and analyze BP5 scientific data files using ADIOS2 with AI agents.

CLIO Arxiv
AI-powered ArXiv research paper discovery and analysis through Model Context Protocol