IONOS CLOUD MCP Server
Inspect and reason about IONOS CLOUD resources—compute, storage, and related services—from your agent without juggling multiple consoles.
Overview
io.github.ionos-cloud/ionoscloud-mcp is a MCP server for the Operate phase that inspects IONOS CLOUD infrastructure via API token–authenticated MCP tools with eager or lazy load modes.
What is this MCP server?
- IONOS CLOUD MCP Server (v1.0.0) with OCI image ghcr.io/ionos-cloud/ionoscloud-mcp:1.0.0
- IONOS_TOKEN required for most products; separate IONOS_S3_ACCESS_KEY and IONOS_S3_SECRET_KEY for Object Storage
- IONOS_MCP_LOAD_MODE: eager (default), lazy (deferred Compute/Object Storage tools), router (reserved, not implemented)
- Lazy mode uses sentinel tools ionos_load_compute_tools and ionos_load_objectstorage_tools when clients support tools/lis
- Documented for clients with tool caps (Cursor, Windsurf) via load-mode strategies
- Server version 1.0.0; OCI identifier ghcr.io/ionos-cloud/ionoscloud-mcp:1.0.0
- Three documented IONOS_MCP_LOAD_MODE values: eager (default), lazy, router (reserved)
- Lazy mode exposes sentinel tools ionos_load_compute_tools and ionos_load_objectstorage_tools
Community signal: 4 GitHub stars.
What problem does it solve?
Solo operators lose time switching between IONOS consoles and chat when they need a grounded view of what cloud resources exist and how they relate.
Who is it for?
Indie devs and small teams already on IONOS CLOUD who want agent-assisted infra inspection and troubleshooting.
Skip if: Builders on AWS-only or Vercel-only stacks with no IONOS account, or anyone needing full Terraform apply/replace orchestration from this MCP alone.
What do I get? / Deliverables
After configuring IONOS_TOKEN (and S3 keys if needed), your agent can query IONOS CLOUD through MCP with a load mode that fits your client’s tool limits.
- MCP tools for inspecting IONOS CLOUD infrastructure aligned with your load mode
- Deferred Compute/Object Storage tool loading via lazy mode when supported by the client
Recommended MCP Servers
Journey fit
Day-two cloud ownership—what is running, misconfigured, or costing money—maps to Operate infra as the canonical shelf. The server is for infrastructure inspection and tool-gated access to IONOS APIs, not frontend or growth work.
How it compares
Read-oriented IONOS cloud MCP bridge, not a multi-cloud FinOps dashboard or generic DevOps skill.
Common Questions / FAQ
Who is io.github.ionos-cloud/ionoscloud-mcp for?
Solo builders and small teams running workloads on IONOS CLOUD who want their agent to inspect cloud resources with MCP instead of manual console digging.
When should I use io.github.ionos-cloud/ionoscloud-mcp?
During infra reviews, incident triage, launch checks, or backend planning when you need accurate IONOS resource context inside the agent session.
How do I add io.github.ionos-cloud/ionoscloud-mcp to my agent?
Run the OCI image ghcr.io/ionos-cloud/ionoscloud-mcp:1.0.0 as a stdio MCP server, set IONOS_TOKEN (and S3 keys for Object Storage), optionally set IONOS_MCP_LOAD_MODE to eager or lazy, then register it in your MCP client.