


















Take advantage of the IONOS CLOUD MCP Server without any additional license or subscription fees. You only pay for the IONOS CLOUD resources actively used in your account. With the dynamic price calculator, you can quickly and easily create a customized cost estimate tailored to your specific requirements and production workloads.
Use Case
Use your AI client to systematically scan your IONOS CLOUD environment and identify faulty configurations before they lead to incidents.
Use Case
Give your finance and engineering teams a natural-language interface to IONOS CLOUD billing data—without writing a single line of code.
Use Case
Connect AI agents to IONOS CLOUD account data so they can operate based on the actual infrastructure status rather than static documentation.
Yes. The IONOS CLOUD MCP Server is a free MCP server: there are no license or subscription fees, and the source code is published under Apache 2.0 on GitHub. You are billed only for the IONOS CLOUD resources your account actually consumes. An IONOS CLOUD account and an API token are required
Via Homebrew, as a pre-built binary for Linux, macOS, and Windows, with go install, or as a Docker image. The container image is available on ghcr.io for linux/amd64 and linux/arm64, and runs locally, on a CI runner, or inside a container. The server is also listed on the major MCP registries and IDE marketplaces, including the official MCP Registry, Smithery, mcp.so, the Cursor Directory, and Glama. The full list is in the GitHub repository.
The MCP Server provides around 200 tools across seven products: Compute Engine, IONOS CLOUD Object Storage, Billing, Cloud DNS, Managed Kubernetes, Certificate Manager, and Activity Log. That includes inspecting your Kubernetes clusters, node pools, and available versions. Database as a Service with PostgreSQL, MongoDB, and MariaDB is not covered at present. You can request additional products via GitHub.
Not by default. Out of the box, every tool is an inspection or query operation: write tools are not registered and do not appear in your AI client at all. Using them requires you to enable them explicitly. Until you do, connecting the server to live production accounts remains completely safe.
Yes. Create a separate token and give it only the permissions you actually need. For analysis and audit work, read access to Compute Engine, Cloud DNS, billing, and Object Storage is enough. Write operations require broader permissions, so handle that token with more care and rotate it regularly.
Yes. The complete source code is available at github.com/ionos-cloud/ionoscloud-mcp under the Apache 2.0 license. You can see exactly what the server does, contribute, or report issues directly through GitHub.
The difference is crucial: API requests are sent directly from your device via HTTPS to @cloudBrand—with no third parties involved along the way. Your prompts and tool outputs are transmitted to your client’s AI model provider (e.g., Anthropic, Microsoft). For a fully EU-sovereign path, in which inference also remains within European infrastructure, combine the MCP Server with the IONOS CLOUD AI Model Hub.
Dedicated setup guides are available for Claude Desktop, Claude Code, Cursor, VS Code (GitHub Copilot), Gemini CLI, JetBrains AI Assistant, Windsurf, Kiro, Continue, Cline, Zed, and OpenCode. Any other MCP-compliant client will also work, including AI agent frameworks such as the OpenAI Agents SDK and LangGraph.