
IONOS CLOUD MCP Server
io.github.ionos-cloud由 GitHub 帳號 ionos-cloud 發布v1.1.2更新於 Oct 24, 2026
Inspect and manage IONOS CLOUD infrastructure via MCP. Writes are opt-in and off by default.
概覽
預設唯讀的 MCP 伺服器,讓助理檢視 IONOS CLOUD 基礎設施(運算、Kubernetes、物件儲存、DNS、帳務),並可在明確開啟後執行管理操作。
- 可以做什麼
- 列出並檢視運算資源:資料中心、伺服器、磁碟區、網路卡、LAN、防火牆規則、IP 區塊、負載平衡器、NAT 閘道、快照與映像
- 檢視 Kubernetes 叢集、節點集區、節點及可用版本
- 瀏覽物件儲存的桶、桶設定、物件、存取金鑰與區域
- 檢視 DNS 區域、記錄、反向記錄、DNSSEC 與配額
- 讀取帳務資料:帳戶資料、發票、流量、用量、價格目錄與活動日誌事件
- 開啟寫入範圍後,可對運算、Kubernetes、DNS 與憑證管理員執行建立、更新或刪除
- 適用情境
- 適合讓助理以自然語言稽核、盤點或說明 IONOS CLOUD 帳戶,例如成本檢視、桶的公開存取安全檢查、找出閒置資源、DNS 與憑證檢查;在刻意開啟寫入時也可用來建立資源。
- 執行需求
- 以本機執行檔或容器執行(Homebrew、Docker 映像、預先編譯執行檔、go install 或原始碼)。需要 IONOS CLOUD 帳戶,並在 IONOS_TOKEN 提供 API 權杖;物件儲存資料面工具另需 IONOS_S3_ACCESS_KEY 與 IONOS_S3_SECRET_KEY。可選 IONOS_MCP_LOAD_MODE 與 IONOS_MCP_TOOL_SCOPE 控制工具載入與寫入權限。需透過 HTTPS 存取 IONOS API。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 IONOS CLOUD MCP Server,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
[Official IONOS Cloud] [Apache 2.0] [Go reference]
IONOS CLOUD MCP Server
A read-only-by-default Model Context Protocol (MCP) server that connects your IONOS CLOUD account to any MCP-compatible AI assistant or autonomous AI agent: Claude Desktop, Cursor, VS Code (GitHub Copilot), Windsurf, Cline, Continue, OpenCode, and 5+ others. 118 read-only tools across 7 IONOS CLOUD products — list, inspect, and audit your infrastructure through natural-language prompts or programmatic agentic loops. Write operations across Compute (servers, volumes, networking, load balancing), Managed Kubernetes (clusters, node pools, nodes), DNS (zones, records, reverse records, DNSSEC) and Certificate Manager (certificates, auto-certificates, providers) are strictly opt-in and create real, billable resources — see Write operations.
Built and maintained by the IONOS Cloud team. The server runs as a local binary on your workstation, a CI runner, or inside a container. IONOS CLOUD API calls go directly to IONOS over HTTPS; no third-party AI provider sits in the data path.
Compatibility: MCP spec 2024-11-05 · Go 1.25+ for builds · OCI images for linux/amd64 and linux/arm64.
📚 Full product documentation, per-client setup guides, FAQ, and tutorials: docs.ionos.com/cloud/ai/mcp-server
Get started in 60 seconds (macOS or Linux, via Homebrew):
For other install paths (Docker, pre-built binary, go install, source), see Installation.
Why • Registries • Products • Install • Config • Tool loading • Transport • Write ops • Demo • Dev • Related • Changelog
Why
- Read-only by default, writes strictly opt-in — out of the box every tool is an inspection operation (
list_*,get_*,head_*), so it's safe to connect to production accounts and to deploy inside unattended agent loops on CI runners. Write tools (create_*,update_*,delete_*) register only when you setIONOS_MCP_TOOL_SCOPE, and even then every create and delete requires a two-phase confirmation (preview → one-time token → execute). See Write operations. - Local binary, no proxy — IONOS CLOUD API calls go directly from your machine to IONOS Cloud. No third-party AI vendor in the data path.
- EU-sovereign option — pair the server with the IONOS CLOUD AI Model Hub and both the API calls and the LLM inference terminate inside IONOS's German data centres. See the Fully Sovereign AI Workflow guide.
- Open source — Apache 2.0. Read the source, audit the behaviour, contribute, or fork.
Registries & Directories
This server is published across multiple MCP registries and IDE marketplaces:
Supported products
Read tools are named list_*, get_* and head_*; the opt-in write tools are create_*, update_*, delete_* plus domain verbs such as start_* and attach_*. In the default eager mode all tools register at startup; lazy mode defers Compute and Object Storage behind loader tools; dynamic mode exposes only three search/describe/call meta-tools for clients with hard tool caps. See Tool loading mode.
118 read-only tools, plus 102 opt-in write tools on Compute Engine, Kubernetes, DNS and Certificate Manager — see Write operations. For per-tool input/output schemas, see the per-product docs or the full Tool Reference at docs.ionos.com.
Installation
Pick whichever fits your workflow.
Homebrew (macOS, Linux) — recommended
Docker (linux/amd64, linux/arm64)
Run with the MCP stdio transport (default):
Or over HTTP (see Wire transport):
Pre-built binary
Download the archive for your OS/arch from the latest release. Available for Linux, macOS, and Windows on both amd64 and arm64.
go install
From source
Configuration
You need an IONOS CLOUD account with API credentials.
Generate a token in the IONOS CLOUD DCD under Management → Token Management. Object Storage credentials are created under Storage & Backup → IONOS CLOUD Object Storage → Key management.
For least-privilege token scoping, see Authentication at docs.ionos.com.
Integrating with an MCP client (manual)
Add the server to your AI client's MCP config:
The Object Storage credentials are only needed if you plan to use Object Storage tools.
Per-client setup guides for the 12 supported AI clients: Connect to an AI Client at docs.ionos.com.
Tool loading mode
The load mode selects how tools are exposed. Set it with either the --load-mode flag or the IONOS_MCP_LOAD_MODE environment variable; the flag wins if both are set, and otherwise the default is eager. Parsing is case-insensitive.
-
eager(default): all tools register at startup. Recommended for Claude Code (which defers full schemas client-side via ToolSearch, paying ~1–3k tokens for names only) and the only working mode for clients that ignorenotifications/tools/list_changed(Claude Desktop, claude.ai connectors, Claude in Chrome). -
lazy: Compute and Object Storage register only on demand. Two sentinel tools (ionos_load_compute_tools,ionos_load_objectstorage_tools) appear at startup; calling either registers the full product set and emitsnotifications/tools/list_changed. Use only if your MCP client honours that notification AND lacks client-side schema deferral — otherwise eager mode is cheaper. -
dynamic(alias:search): the server exposes only three meta-tools —ionos_search_tools,ionos_describe_toolsandionos_call_tool— and the model discovers and invokes the full catalogue through them at runtime. The real tool list never changes, so unlikelazythis needs nonotifications/tools/list_changedsupport. Intended for clients with hard tool caps and no tool search of their own (e.g. Cursor's ~40-tool cap, Windsurf's 100). Trade-off: the model mustsearch→describe→callrather than seeing tools directly, costing extra round-trips, so prefereageron Claude Code.
The server logs the effective mode and its source (flag / env / default) to stderr at startup, e.g. load mode: dynamic (source: --load-mode flag).
Tool-count limits: Windsurf caps connected MCP servers at 100 tools combined; Cursor caps at ~40 across all servers. With the default eager mode the server exceeds both. On Windsurf, lazy keeps the startup surface small enough; on Cursor (or any cap-limited client without its own tool search), use dynamic to present just three tools. For more information, see Selective Tool Loading.
Wire transport
The server speaks stdio by default — the mode every subprocess-spawning MCP client expects (Claude Desktop, Claude Code, Cursor, Windsurf, etc.). For remote or networked deployments (e.g. running the server centrally and pointing multiple clients at it), switch to the Streamable HTTP transport with --transport http or IONOS_MCP_TRANSPORT=http; the flag wins if both are set.
--transport <stdio|http>(orIONOS_MCP_TRANSPORT) — selects the transport. Unrecognised values fall back tostdiowith a warning.--http-addr <addr>(orIONOS_MCP_HTTP_ADDR) — listen address for the HTTP transport. Default127.0.0.1:8080(local-only); use:8080to listen on all interfaces. Ignored for stdio.
The server logs the effective transport and its source to stderr at startup, e.g. transport: http (source: --transport flag).
In HTTP mode, point your MCP client at http://<host>:<port>/ as a Streamable HTTP server. There is no built-in TLS or authentication for the HTTP endpoint itself — put it behind a reverse proxy (e.g. nginx, Caddy) if it needs to be reachable outside a trusted network. IONOS_TOKEN and the other IONOS CLOUD credentials still authenticate the server's own calls to the IONOS API regardless of transport.
Write operations
The server is read-only until you opt in. Write tools are never registered and never appear in tools/list unless you set the IONOS_MCP_TOOL_SCOPE environment variable. The gate applies in every load mode, including the dynamic dispatcher — there is no bypass.
Scope is a comma-separated, hierarchical set of capabilities (read is always on):
Unrecognised values fall back to read-only, and the effective scope is logged to stderr at startup. Because the levels are hierarchical, a single value is enough — destructive alone already grants write and read; you don't need to list them all (though a comma-separated list like read,write is also accepted).
What can be written
102 tools in total. The server exposes 118 at the default read-only scope, 181 with write, and 220 with destructive. Reads are unaffected and always available.
Two-phase confirmation. Every create_* and delete_*, plus the disruptive actions (stop_, reboot_, suspend_, upgrade_, restore_, detach_, recreate_), is confirmation-gated, along with the DNS zone-file import. The first call performs no mutation: it returns a preview — for a delete, a blast-radius summary of what will be destroyed — plus a single-use confirmation_token (5-minute TTL, bound to that exact target and operation). Only a second call carrying that token executes. This keeps a human in the loop and limits the agent to one resource per call. Reversible single-field changes (update_*, start_, attach_, assign_) are a single call.
Annotations. Write tools carry MCP annotations (readOnlyHint, destructiveHint, idempotentHint) so clients can build their own approval UX — but enforcement is always server-side. Note that the class comes from the operation, not the HTTP verb: stop_server is a POST that is destructive, and import_dns_zone_file is a PUT that replaces every record in a zone.
⚠️ Write operations create real resources and real charges
Enabling
IONOS_MCP_TOOL_SCOPElets an AI model provision billable infrastructure in your live IONOS CLOUD account. Every create is a real resource on a real invoice, effective immediately.Some resources cost money even when nothing is using them — a reserved IP block, a snapshot, or a volume left behind after its server was deleted. Deletions are equally real: destroyed data is not recoverable without a snapshot, and a released IP address cannot be asked for again.
An AI model decides when and how often to call these tools. It can misread your intent, retry more than you expected, or pick a larger resource than you had in mind. The two-phase confirmation exists to put a human in that loop, but it cannot stop a client configured to approve tool calls automatically — in that setup the model can complete both phases on its own.
You are responsible for everything created, modified or deleted in your account through these tools, and for the resulting charges. IONOS does not control and is not responsible for how a model chooses to call them, or for any cost, data loss or outage arising from those calls.
Reduce the risk: leave the server read-only unless you need writes; grant
writerather thandestructivewhen deletion isn't required; require manual approval of tool calls in your client; read the preview before returning a confirmation token; and prefer a non-production account when experimenting.
Enable writes in your MCP client config, for example:
Demo
In Claude Desktop or any other supported client, after configuring the server, try one of these prompts. They cover the kinds of multi-step inspection workflows that are tedious to write as scripts but easy in natural language:
- Cost audit: "Audit my IONOS CLOUD account, find the top 5 cost-inducing resources this month, and suggest cost-efficiency tips."
- Security sweep: "List every bucket whose public access block is off or whose policy is public — flag anything that looks unintentional."
- Audit trail: "Show me every failed API request on my contract in the last 30 days, grouped by user."
- Forgotten resources: "Find unattached volumes, unused IP blocks, and stopped servers across all my data centers."
- DNS sanity check: "List all zones on my account and flag any without DNSSEC enabled or with records pointing to IPs I no longer own."
- Certificate expiry: "Which certificates on my account expire in the next 60 days?"
- Traffic spike investigation: "My last invoice was higher than usual — show me daily traffic and utilization for the previous billing period and tell me what changed."
- Onboarding tour: "Walk me through what I have running on IONOS CLOUD — datacenters, servers, storage, DNS — like you're explaining it to a new teammate."
Each prompt chains multiple list_* and get_* calls and produces a summary you can paste into a ticket, dashboard, or doc. For end-to-end walkthroughs:
- Run a security posture audit on your IONOS CLOUD Object Storage buckets
- Generate a FOCUS-compliant cost report
Development
Testing the MCP protocol locally
You can test the server's MCP protocol implementation using stdin/stdout:
Building from source
Run make with no arguments to see the available targets.
Related projects
- IONOS CLOUD MCP Server product docs — full product documentation
- IONOS CLOUD AI Model Hub — open-weight LLMs hosted in Germany; pair with this server for a fully EU-sovereign AI loop
- IONOS CLOUD Documentation MCP — a free public MCP server exposing the IONOS docs site for AI assistants
Contributing
Issues and pull requests are welcome. For development setup, code style, and testing instructions, see CONTRIBUTING.md. For questions and discussion, use GitHub Discussions.
Security
If you believe you have found a security vulnerability, please do not open a public issue. Report it privately via GitHub's private vulnerability reporting or by email to [email protected]. Full policy: SECURITY.md.
Changelog
Notable changes per release are tracked in CHANGELOG.md. For the artefacts published with each tag (Linux/macOS/Windows binaries, multi-arch OCI images), see the GitHub Releases page.
API documentation
For more information about the IONOS CLOUD API:
License
Apache License 2.0 — see LICENSE.
來源:README.md,提交 8579e7e
工具
0版本歷史
3- v1.1.2最新Oct 22, 2026
- v1.1.1Sep 17, 2026
- v1.1.0Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分