概要
What is IONOS CLOUD MCP Server?
A read-only Model Context Protocol (MCP) server that connects your IONOS CLOUD account to any MCP‑compatible AI assistant or agent. It provides 112 tools across six IONOS CLOUD products for listing, inspecting, and auditing infrastructure through natural‑language prompts or programmatic loops. Built and maintained by the IONOS Cloud team, it runs as a local binary, in a CI runner, or inside a container.
How to use IONOS CLOUD MCP Server?
Install via Homebrew (brew install ionos-cloud/ionos-cloud/ionoscloud-mcp), Docker, pre‑built binary, go install, or from source. Set the IONOS_TOKEN environment variable (and optionally IONOS_S3_ACCESS_KEY and IONOS_S3_SECRET_KEY for Object Storage). Add the server to your MCP client’s config JSON, then ask natural‑language questions about your infrastructure.
Key features of IONOS CLOUD MCP Server
- Read‑only by design – never creates, modifies, or deletes resources
- 112 tools across Compute Engine, Kubernetes, Object Storage, DNS, Billing, Certificate Manager, and Activity Log
- Local binary with direct IONOS API calls – no third‑party AI in the data path
- Offers an EU‑sovereign option when paired with IONOS CLOUD AI Model Hub
- Open source under Apache 2.0 license
- Supports both eager and lazy tool loading modes
Use cases of IONOS CLOUD MCP Server
- Audit top cost‑inducing resources and get cost‑efficiency tips
- Perform a security sweep of Object Storage buckets for public access
- Investigate failed API requests grouped by user across the last 30 days
- Find unattached volumes, unused IP blocks, and stopped servers across data centers
- Check certificate expiry and DNS zone DNSSEC status
FAQ from IONOS CLOUD MCP Server
Is the server really read‑only?
Yes. Every tool is an inspection operation (list_*, get_*, head_*) and cannot create, modify, or delete any resource. This makes it safe for production accounts and unattended agent loops.
What are the runtime requirements?
The server runs as a Go binary (Go 1.25+ for builds) and is available as OCI images for linux/amd64 and linux/arm64. It requires an IONOS CLOUD account and an API token.
How does tool loading work?
By default all tools register at startup (“eager” mode). Setting IONOS_MCP_LOAD_MODE=lazy registers Compute and Object Storage tools only on demand via two sentinel tools, which is useful for clients like Windsurf that have tool‑count limits.
Where can I find full documentation and per‑client setup guides?
Complete documentation, including per‑client setup guides, FAQ, and tutorials, is available at docs.ionos.com/cloud/ai/mcp-server.
