Ionoscloud MCP

What ionos-cloud/ionoscloud-mcp MCP server does

The ionos-cloud/ionoscloud-mcp MCP server exposes IONOS Cloud control-plane and Object Storage capabilities through the Model Context Protocol. It is intended for MCP-compatible clients and agent workflows that need to query infrastructure with natural-language prompts or programmatic tool calls.

The default behavior is read-only. The available read tools cover seven IONOS Cloud product areas:

• Compute Engine resources such as servers, volumes, networks, load balancers, firewalls, snapshots, images, and locations
• Managed Kubernetes clusters, node pools, nodes, and available versions
• Object Storage buckets, objects, policies, encryption, lifecycle settings, replication, versioning, and related configuration
• DNS zones, records, reverse records, DNSSEC, secondary zones, and quota
• Billing information including invoices, traffic, usage, utilization, and product pricing
• Certificate Manager certificates, auto-certificates, and providers
• Activity Log contracts and events

Write operations exist for Compute Engine, Kubernetes, and DNS, but they are not registered unless the tool scope is changed. Create and delete actions also use a preview and one-time-token confirmation process.

How it works

The ionos-cloud/ionoscloud-mcp MCP server runs locally on a workstation, CI runner, or container. Its API requests go directly to IONOS Cloud over HTTPS rather than through a third-party AI provider. It supports MCP stdio transport by default and can also be started with HTTP transport.

Three tool-loading approaches are documented. Eager mode registers all tools when the process starts. Lazy mode places Compute and Object Storage tools behind loader tools. Dynamic mode exposes search, describe, and call meta-tools, which can help clients with strict tool-count limits discover and invoke the underlying capabilities.

Setup and configuration

Install options include Homebrew, a pre-built release binary, Docker, Go, or a source build. The documented Go installation command is go install github.com/ionos-cloud/ionoscloud-mcp@latest. Docker images are published for Linux amd64 and arm64.

The required IONOS_TOKEN environment variable supplies the API token for Compute, DNS, Billing, Certificate Manager, and Object Storage management APIs. Object Storage data-plane operations additionally require IONOS_S3_ACCESS_KEY and IONOS_S3_SECRET_KEY. These credentials are created in the relevant IONOS Cloud account consoles.

Set IONOS_MCP_TOOL_SCOPE=write to enable create and update operations. A destructive scope also enables deletion and implies write access. Without this setting, the server remains read-only.

Tools and capabilities

The ionos-cloud/ionoscloud-mcp MCP server reports 118 read-only tools and 93 opt-in write tools in the documented product set. Tool names generally reflect their operation, including list_*, get_*, and head_* for inspection, plus create_*, update_*, and delete_* for enabled mutations. Domain-specific actions such as starting or attaching resources are also available among the opt-in tools.

The top-level MCP interface includes eager, lazy, and dynamic loading controls, along with search, description, and tool-call operations. Product-specific loader tools are provided for Compute and Object Storage in lazy mode.

Limitations and notes

An IONOS Cloud account and API credentials are required. Object Storage data-plane functionality needs separate S3-compatible access credentials. Write actions can create billable resources, so they should only be enabled when the client workflow is prepared to handle confirmations and the consequences of mutations.

The project targets MCP specification version 2024-11-05 and requires Go 1.25 or newer for builds. The repository is licensed under Apache 2.0.