Turning on `IONOS_MCP_TOOL_SCOPE` lets a model provision billable infrastructure in a live account, and every create, delete and disruptive action then needs two calls — the first returns a preview and a single-use token with a 5-minute TTL, only the second executes. The project says plainly that this cannot stop a client set to auto-approve tool calls. Read-only is the honest default here, and grant `write` rather than `destructive` when deletion is not part of the job.
A local binary, built and maintained by the IONOS Cloud team, that connects your IONOS account to an MCP client. API calls go straight from your machine to IONOS over HTTPS, with no third-party AI vendor in the data path. Every tool registered by default is an inspection operation, which is what makes it safe to point at a production account.
- Compute Engine — data centers, servers, volumes, NICs, LANs, firewall rules, IP blocks, load balancers (basic, network and application), NAT gateways, security groups, private cross-connects, snapshots, images, templates, locations, requests and contract
- Managed Kubernetes — clusters, node pools, nodes and available versions
- Object Storage — buckets and their configuration for CORS, encryption, lifecycle, policy, public access block, replication, tagging, versioning and Object Lock, plus objects, access keys and regions
- DNS — zones, zone files, records, reverse records, secondary zones, DNSSEC and quota
- Billing — profile, invoices, provisioning intervals, traffic, usage, utilization and the product pricing catalog
- Certificate Manager and Activity Log — certificates, auto-certificates and providers; contracts and events
- 118 read-only tools plus 2 loader tools; opting in raises the surface to 165 tools with `write` and 195 with `destructive`
- Three loading modes for clients with tool caps: `eager` registers everything, `lazy` hides Compute and Object Storage behind loader tools, `dynamic` exposes only search, describe and call meta-tools
An IONOS Cloud account and an API token, generated in the DCD under Management → Token Management, passed as `IONOS_TOKEN`. Object Storage data-plane tools additionally need `IONOS_S3_ACCESS_KEY` and `IONOS_S3_SECRET_KEY`, created under Key management. Install with `brew install ionos-cloud/ionos-cloud/ionoscloud-mcp`, `go install`, a pre-built release binary for Linux, macOS or Windows on amd64 and arm64, or the `ghcr.io/ionos-cloud/ionoscloud-mcp` image. Write tools stay unregistered unless `IONOS_MCP_TOOL_SCOPE` is set to `write` or `destructive`. Go 1.25+ to build from source. Apache 2.0.
One command plus a key — brew install ionos-cloud/ionos-cloud/ionoscloud-mcp, then supply credentials