Skip to main content
Glama
IONOS CLOUD MCP Server

IONOS CLOUD MCP Server

Official
by ionos-cloud

Official IONOS Cloud Apache 2.0 Go reference

Alt text

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):

brew install ionos-cloud/ionos-cloud/ionoscloud-mcp

For other install paths (Docker, pre-built binary, go install, source), see Installation.

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 set IONOS_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.

Related MCP server: incus-mcp

Registries & Directories

This server is published across multiple MCP registries and IDE marketplaces:

Registry

Link

Official MCP Registry

io.github.ionos-cloud/ionoscloud-mcp

mcp.so

ionos-cloud-mcp-server

Glama

ionoscloud-mcp

Cursor

ionoscloud-mcp

mcpservers.org

ionoscloud-mcp

PulseMCP

ionoscloud

MCPMarket

ionos-cloud

punkpeye/awesome-mcp-servers

ionos-cloud/ionoscloud-mcp

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.

Product

Tools

Capabilities

Compute Engine

50 + 70 write

Data centers, servers, volumes, NICs, LANs, firewall rules, IP blocks, load balancers (basic / network / application), NAT gateways, security groups, private cross-connects, snapshots, images, templates, locations, requests, contract

Kubernetes

8 + 8 write

Clusters, node pools, nodes, available versions

Object Storage

23

Buckets, bucket configuration (CORS, encryption, lifecycle, policy, public access block, replication, tagging, versioning, Object Lock), objects, access keys, regions

DNS

14 + 16 write

Zones, zone files (+ BIND import), records, reverse records, secondary zones (+ zone transfer), DNSSEC, quota

Billing

15

Profile, invoices, EVN (provisioning intervals), traffic, usage, utilization, product pricing catalog, FOCUS v1.3 spec

Certificate Manager

6 + 8 write

Certificates, auto-certificates, providers

Activity Log

2

Contracts, events

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.

brew install ionos-cloud/ionos-cloud/ionoscloud-mcp

Docker (linux/amd64, linux/arm64)

docker pull ghcr.io/ionos-cloud/ionoscloud-mcp:latest

Run with the MCP stdio transport (default):

docker run -i --rm \
  -e IONOS_TOKEN="$IONOS_TOKEN" \
  ghcr.io/ionos-cloud/ionoscloud-mcp

Or over HTTP (see Wire transport):

docker run --rm -p 8080:8080 \
  -e IONOS_TOKEN="$IONOS_TOKEN" \
  ghcr.io/ionos-cloud/ionoscloud-mcp --transport http --http-addr :8080

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

go install github.com/ionos-cloud/ionoscloud-mcp@latest

From source

git clone https://github.com/ionos-cloud/ionoscloud-mcp.git
cd ionoscloud-mcp
make build

Configuration

You need an IONOS CLOUD account with API credentials.

# Required: API token for control-plane APIs (Compute, DNS, Billing, Certificate Manager, Object Storage management)
export IONOS_TOKEN="your-api-token"

# Optional: only required if you use Object Storage data-plane tools
# (listing objects, reading bucket configuration, checking access keys).
export IONOS_S3_ACCESS_KEY="your-s3-access-key"
export IONOS_S3_SECRET_KEY="your-s3-secret-key"

# Optional: opt in to write operations (default: read-only). Values are hierarchical,
# so a single level suffices: "write" allows create/update; "destructive" also allows
# delete (it implies "write"). See "Write operations".
# export IONOS_MCP_TOOL_SCOPE="write"

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:

{
  "mcpServers": {
    "ionoscloud": {
      "command": "/path/to/ionoscloud-mcp",
      "env": {
        "IONOS_TOKEN": "your-api-token",
        "IONOS_S3_ACCESS_KEY": "your-s3-access-key",
        "IONOS_S3_SECRET_KEY": "your-s3-secret-key"
      }
    }
  }
}

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 ignore notifications/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 emits notifications/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_tools and ionos_call_tool — and the model discovers and invokes the full catalogue through them at runtime. The real tool list never changes, so unlike lazy this needs no notifications/tools/list_changed support. 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 must search → describe → call rather than seeing tools directly, costing extra round-trips, so prefer eager on 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).

{
  "mcpServers": {
    "ionoscloud": {
      "command": "/path/to/ionoscloud-mcp",
      "args": ["--load-mode", "dynamic"],
      "env": {
        "IONOS_TOKEN": "your-api-token"
      }
    }
  }
}

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.

./ionoscloud-mcp --transport http --http-addr :8080
  • --transport <stdio|http> (or IONOS_MCP_TRANSPORT) — selects the transport. Unrecognised values fall back to stdio with a warning.

  • --http-addr <addr> (or IONOS_MCP_HTTP_ADDR) — listen address for the HTTP transport. Default 127.0.0.1:8080 (local-only); use :8080 to 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):

IONOS_MCP_TOOL_SCOPE

Enables

unset / read (default)

read-only (list_*, get_*, head_*)

write

the above + create_*, update_*, and the non-disruptive actions start_, resume_, attach_, assign_

destructive

the above + delete_* and the disruptive actions stop_, reboot_, suspend_, upgrade_, restore_, detach_, recreate_, import_ (implies write)

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

Area

Resources

Compute

data centers, servers (+ start/stop/reboot/suspend/resume/upgrade), volumes (+ snapshot & restore, attach/detach), NICs, LANs

Networking

IP blocks (reserve, rename and release), security groups + rules, firewall rules, private cross connects

Load balancing

classic, network and application load balancers + forwarding rules, target groups, NAT gateways + rules

Images

snapshot and image update/delete

Kubernetes

clusters, node pools (scale, upgrade, autoscaling, LANs, labels, annotations, taints), single nodes (recreate, delete)

DNS

primary zones (+ BIND zone-file import), records, secondary zones (+ zone transfer), reverse records, DNSSEC enable/disable

Certificate Manager

auto-certificates, ACME providers, certificate rename/delete — renames only change the name, the rest is immutable. Uploading certificate material is deliberately not offered: it would require passing a private key as a tool argument.

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_SCOPE lets 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 write rather than destructive when 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:

{
  "mcpServers": {
    "ionoscloud": {
      "command": "/path/to/ionoscloud-mcp",
      "env": {
        "IONOS_TOKEN": "your-api-token",
        "IONOS_MCP_TOOL_SCOPE": "destructive"
      }
    }
  }
}

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:

Development

Testing the MCP protocol locally

You can test the server's MCP protocol implementation using stdin/stdout:

# Initialize and list tools
{
  echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.1.0"}}}'
  echo '{"jsonrpc":"2.0","method":"notifications/initialized"}'
  echo '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'
  sleep 1
} | ./ionoscloud-mcp

# Call a tool (requires a valid IONOS_TOKEN)
{
  echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.1.0"}}}'
  echo '{"jsonrpc":"2.0","method":"notifications/initialized"}'
  echo '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"list_datacenters","arguments":{}}}'
  sleep 1
} | ./ionoscloud-mcp

Building from source

make build
# or
go build -o ionoscloud-mcp .

Run make with no arguments to see the available targets.

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 sdk-tooling@ionos.com. 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.

Available Tools

118 tools
get_application_loadbalancerA
Read-only

Get details of a specific application load balancer (ALB)

Inputs: datacenter_id (required), application_loadbalancer_id (required), depth.

get_billing_focus_specA

Returns the FOCUS v1.3 column specification and IONOS tool → FOCUS field mappings. Call before mapping IONOS invoice/usage/traffic data to FOCUS format, or when user asks for FOCUS-compliant cost output.

get_billing_invoiceA

Get the detailed line-item breakdown for a specific invoice by ID. Use list_billing_invoices first to find available invoice IDs. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.

Inputs: contract (required), invoice_id (required).

get_billing_profileA

Get the billing profile for your IONOS CLOUD account. Call this first before any other billing tool — the contract number in the response is required by all other billing tools.

get_billing_usage_by_datacenterA

Get aggregated resource usage for a specific datacenter (VDC UUID) in the current billing period. Use list_billing_usage first to find datacenter IDs. Defaults exclude zero-quantity meters (set include_zero=true to keep them). For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.

Inputs: contract (required), datacenter_id (required), include_zero.

get_billing_utilization_dailyA

Get per-resource utilization for a specific date (YYYY-MM-DD). Use this for day-level analysis within a month. Same compaction flags as list_billing_utilization. For contracts with many datacenters, scope with regions, datacenter_id, or meter_types — or set top_n=10 for a flat global top-N list — before group_by=datacenter to keep the response under 25 KB. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.

Inputs: date (required), contract (required), top_n, regions, +4 more.

get_cert_auto_certificateA
Read-only

Get details of a specific auto-certificate by ID

Inputs: auto_certificate_id (required).

get_cert_certificateA
Read-only

Get details of a specific SSL/TLS certificate by ID. Returns certificate metadata and public key material but not the private key.

Inputs: certificate_id (required).

get_cert_providerA
Read-only

Get details of a specific certificate provider by ID. Returns provider configuration but not the external account binding secret.

Inputs: provider_id (required).

get_contractA
Read-only

Get contract and resource limit information for your IONOS CLOUD account

Inputs: depth.

get_datacenterA
Read-only

Get details of a specific virtual data center

Inputs: datacenter_id (required), depth.

get_dns_quotaA
Read-only

Get DNS quota usage and limits for your IONOS CLOUD account

get_dns_recordA
Read-only

Get details of a specific DNS record in a zone

Inputs: zone_id (required), record_id (required).

get_dns_reverse_recordA
Read-only

Get details of a specific reverse DNS record

Inputs: reverse_record_id (required).

get_dns_secondary_zoneB
Read-only

Get details of a specific secondary DNS zone

Inputs: secondary_zone_id (required).

get_dns_secondary_zone_axfrA
Read-only

Get the zone transfer (AXFR) status of a specific secondary DNS zone

Inputs: secondary_zone_id (required).

get_dns_zoneA
Read-only

Get details of a specific DNS zone

Inputs: zone_id (required).

get_dns_zone_fileA
Read-only

Get the zone file (BIND format) for a specific DNS zone

Inputs: zone_id (required).

get_firewall_ruleB
Read-only

Get details of a specific firewall rule

Inputs: nic_id (required), server_id (required), datacenter_id (required), firewallrule_id (required), +1 more.

get_ip_blockA
Read-only

Get details of a specific reserved IP block

Inputs: ipblock_id (required), depth.

get_k8s_clusterA
Read-only

Get details of a specific Kubernetes cluster: state, version, maintenance window, API server allow list and whether it is public or private. Read this before an upgrade — availableUpgradeVersions lists the versions update_k8s_cluster accepts, and viableNodePoolVersions the ones its node pools may run.

Inputs: k8s_cluster_id (required), depth.

get_k8s_default_versionA
Read-only

Get the current default Kubernetes version used by new clusters and node pools in IONOS CLOUD. This is the version create_k8s_cluster picks when k8s_version is omitted.

get_k8s_nodeA
Read-only

Get details of a specific worker node in a Kubernetes node pool: its name, state, Kubernetes version and IP addresses.

Inputs: node_id (required), nodepool_id (required), k8s_cluster_id (required), depth.

get_k8s_nodepoolA
Read-only

Get details of a specific Kubernetes node pool: node count, node hardware, autoscaling bounds, attached LANs, labels and annotations. Read this before calling update_k8s_nodepool with lans, labels, annotations or public_ips, since each of those replaces the whole list. availableUpgradeVersions lists the versions the pool can move to.

Inputs: nodepool_id (required), k8s_cluster_id (required), depth.

get_lanC
Read-only

Get details of a specific LAN

Inputs: lan_id (required), datacenter_id (required), depth.

get_loadbalancerB
Read-only

Get details of a specific load balancer

Inputs: datacenter_id (required), loadbalancer_id (required), depth.

get_nat_gatewayB
Read-only

Get details of a specific NAT gateway

Inputs: datacenter_id (required), nat_gateway_id (required), depth.

get_network_loadbalancerA
Read-only

Get details of a specific network load balancer (NLB)

Inputs: datacenter_id (required), network_loadbalancer_id (required), depth.

get_nicB
Read-only

Get details of a specific network interface (NIC)

Inputs: nic_id (required), server_id (required), datacenter_id (required), depth.

get_object_storage_access_keyA

Get details of a specific Object Storage access key by its ID. Returns key metadata but not the secret key.

Inputs: access_key_id (required).

get_object_storage_bucket_corsA

Get the CORS configuration for an Object Storage bucket.

Inputs: bucket (required).

get_object_storage_bucket_encryptionA

Get the server-side encryption configuration for an Object Storage bucket.

Inputs: bucket (required).

get_object_storage_bucket_lifecycleB

Get the lifecycle configuration for an Object Storage bucket.

Inputs: bucket (required).

get_object_storage_bucket_locationB

Get the region/location of an Object Storage bucket.

Inputs: bucket (required).

get_object_storage_bucket_lock_configurationB

Get the Object Lock configuration for an Object Storage bucket.

Inputs: bucket (required).

get_object_storage_bucket_policyB

Get the bucket policy for an Object Storage bucket.

Inputs: bucket (required).

get_object_storage_bucket_policy_statusB

Get the policy status for an Object Storage bucket, indicating whether the bucket is public.

Inputs: bucket (required).

get_object_storage_bucket_public_access_blockB

Get the public access block configuration for an Object Storage bucket.

Inputs: bucket (required).

get_object_storage_bucket_replicationB

Get the replication configuration for an Object Storage bucket.

Inputs: bucket (required).

get_object_storage_bucket_taggingB

Get the tags for an Object Storage bucket.

Inputs: bucket (required).

get_object_storage_bucket_versioningB

Get the versioning configuration for an Object Storage bucket.

Inputs: bucket (required).

get_object_storage_object_retentionA

Get the Object Lock retention configuration for an object in an Object Storage bucket.

Inputs: key (required), bucket (required).

get_object_storage_object_taggingB

Get the tags for an object in an Object Storage bucket.

Inputs: key (required), bucket (required).

get_object_storage_regionA

Get details of a specific Object Storage region by name (e.g. eu-central-3).

Inputs: region (required).

get_private_cross_connectA
Read-only

Get details of a specific private cross-connect

Inputs: pcc_id (required), depth.

get_requestA
Read-only

Get details of a specific API request

Inputs: request_id (required), depth.

get_request_statusB
Read-only

Get the status of a specific API request

Inputs: request_id (required), depth.

get_security_groupA
Read-only

Get details of a specific security group

Inputs: datacenter_id (required), security_group_id (required), depth.

get_security_group_ruleA
Read-only

Get details of a specific security group rule

Inputs: rule_id (required), datacenter_id (required), security_group_id (required), depth.

get_serverB
Read-only

Get details of a specific server

Inputs: server_id (required), datacenter_id (required), depth.

get_server_gpuA
Read-only

Get details of a specific GPU attached to a server

Inputs: gpu_id (required), server_id (required), datacenter_id (required), depth.

get_server_remote_consoleA
Read-only

Get the remote console URL for a specific server

Inputs: server_id (required), datacenter_id (required), depth.

get_snapshotA
Read-only

Get details of a specific snapshot

Inputs: snapshot_id (required), depth.

get_target_groupA
Read-only

Get details of a specific target group

Inputs: target_group_id (required), depth.

get_templateA
Read-only

Get details of a specific server template

Inputs: template_id (required), depth.

get_volumeA
Read-only

Get details of a specific volume

Inputs: volume_id (required), datacenter_id (required), depth.

head_object_storage_bucketB

Check whether an Object Storage bucket exists and is accessible with the current credentials.

Inputs: bucket (required).

head_object_storage_objectA

Check whether an object exists in an Object Storage bucket and retrieve its user-defined metadata (x-amz-meta-* headers). Returns an error if the object does not exist or is not accessible.

Inputs: key (required), bucket (required).

list_activitylog_contractsA

List contracts accessible for IONOS CLOUD activity log queries. Primarily useful for reseller and partner users with multiple contracts. Single-contract users can skip this — their contract number is embedded in the JWT token returned by get_billing_profile or visible in the IONOS DCD console.

list_activitylog_eventsA

Query the IONOS CLOUD activity log: full audit trail of API requests made against a contract (who did what, when, on which resource). Requires ACCESS_ACTIVITY_LOG privilege on the token. Defaults: last 7 days, limit 25, RequestStatusUpdate events excluded. Use user filter to narrow to a specific account. Use event_types to restrict to e.g. ['Error','RequestAccepted']. Maximum date range is 90 days — paginate or narrow the window for longer spans. Use list_activitylog_contracts first to look up the contract number if needed.

Inputs: contract (required), user, limit, offset, +4 more.

list_alb_forwarding_rulesB
Read-only

List all forwarding rules of an application load balancer

Inputs: datacenter_id (required), application_loadbalancer_id (required), depth, filters.

list_application_loadbalancersA
Read-only

List all application load balancers (ALB) in a data center

Inputs: datacenter_id (required), depth, filters.

list_billing_evnA

Get provisioning itemized data (EVN) for your contract for the current billing month. Shows per-resource usage intervals grouped by datacenter. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.

Inputs: contract (required).

list_billing_evn_by_periodA

Get provisioning itemized data (EVN) for a specific billing period (YYYY-MM). One month per call. If the user requests a range longer than one month, calculate the number of monthly calls required, inform the user, and ask for permission before proceeding. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.

Inputs: period (required), contract (required).

list_billing_invoicesA

List all invoices for your IONOS CLOUD contract. Returns invoice IDs, dates, and amounts. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.

Inputs: contract (required).

list_billing_invoices_by_periodA

List invoices for a specific billing period (YYYY-MM). One month per call. If the user requests a range longer than one month, calculate the number of monthly calls required, inform the user, and ask for permission before proceeding. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.

Inputs: period (required).

list_billing_productsA

Search the IONOS CLOUD product/pricing catalog by keyword. The filter is applied client-side as a case-insensitive partial match on each product's description — it is not an API-level parameter. Returns non-deprecated products whose description contains the filter string. IMPORTANT: Only call this tool when the user has explicitly specified a product or category they want to see pricing for. If the user asks a broad question like 'what are the prices' or 'show me all products', do NOT guess keywords or call this tool multiple times — instead ask the user which specific product or category they are interested in. Examples of valid filters: 'RAM', 'core', 'storage', 'Kubernetes', 'Postgres', 'network', 'Windows'.

Inputs: filter (required), contract (required).

list_billing_trafficA

Get network traffic data for your contract for the current billing month. Returns per-datacenter and per-NIC inbound/outbound traffic in bytes. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.

Inputs: contract (required).

list_billing_traffic_by_periodA

Get network traffic data for a specific billing period (YYYY-MM). One month per call. If the user requests a range longer than one month, calculate the number of monthly calls required, inform the user, and ask for permission before proceeding. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.

Inputs: period (required), contract (required).

list_billing_usageA

Get aggregated resource usage for your contract for the current billing period. Shows metered quantities (CPU hours, GB-hours, etc.) grouped by datacenter. Defaults exclude zero-quantity meters (set include_zero=true to keep them). Filter by datacenter_id to narrow scope. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.

Inputs: contract (required), include_zero, datacenter_id.

list_billing_utilizationA

Get per-resource utilization for the current billing period, grouped by datacenter. Defaults exclude zero-quantity meters (set include_zero=true to find idle resources). Use group_by='meter' or 'datacenter' to aggregate further, or top_n=N for a flat global ranking of the largest meters. Filter by datacenter_id, meter_types, or regions to narrow scope. For contracts with many datacenters, scope with regions, datacenter_id, or meter_types — or set top_n=10 for a flat global top-N list — before group_by=datacenter to keep the response under 25 KB. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.

Inputs: contract (required), top_n, regions, group_by, +3 more.

list_billing_utilization_by_periodA

Get per-resource utilization for a specific billing period (YYYY-MM). One month per call. If the user requests a range longer than one month, calculate the number of monthly calls required, inform the user, and ask for permission before proceeding. Same compaction flags as list_billing_utilization (include_zero, group_by, datacenter_id, meter_types, regions, top_n). For contracts with many datacenters, scope with regions, datacenter_id, or meter_types — or set top_n=10 for a flat global top-N list — before group_by=datacenter to keep the response under 25 KB. For FOCUS v1.3 compliant output, read resource ionos://billing/focus-v1.3.

Inputs: period (required), contract (required), top_n, regions, +4 more.

list_cert_auto_certificatesA
Read-only

List all auto-certificates in your IONOS Cloud Certificate Manager account

list_cert_certificatesA
Read-only

List all SSL/TLS certificates in your IONOS Cloud Certificate Manager account. Returns certificate metadata and public key material but not the private key.

list_cert_providersA
Read-only

List all certificate providers in your IONOS Cloud Certificate Manager account. Returns provider configuration but not the external account binding secret.

list_datacentersB
Read-only

List all virtual data centers. Returns names and basic properties by default (depth=1).

Inputs: depth, filters.

list_dns_recordsA
Read-only

List all DNS records across all zones

list_dns_reverse_recordsA
Read-only

List all reverse DNS records in your IONOS CLOUD account

list_dns_secondary_zone_recordsB
Read-only

List all DNS records in a specific secondary zone

Inputs: secondary_zone_id (required).

list_dns_secondary_zonesA
Read-only

List all secondary DNS zones in your IONOS CLOUD account

list_dns_zone_dnssec_keysA
Read-only

List DNSSEC keys for a specific DNS zone

Inputs: zone_id (required).

list_dns_zone_recordsB
Read-only

List all DNS records in a specific zone

Inputs: zone_id (required).

list_dns_zonesA
Read-only

List all DNS zones in your IONOS CLOUD account

list_firewall_rulesA
Read-only

List all firewall rules on a network interface

Inputs: nic_id (required), server_id (required), datacenter_id (required), depth, +1 more.

list_imagesA
Read-only

List all available images (OS templates) in IONOS CLOUD

Inputs: depth, filters.

list_ip_blocksA
Read-only

List all reserved IP blocks in your IONOS CLOUD account

Inputs: depth, filters.

list_k8s_clustersA
Read-only

List all Kubernetes clusters in your IONOS CLOUD account. Returns names and basic properties by default (depth=1).

Inputs: depth.

list_k8s_nodepool_nodesA
Read-only

List all worker nodes in a Kubernetes node pool, including each node's state and public/private IP addresses.

Inputs: nodepool_id (required), k8s_cluster_id (required), depth.

list_k8s_nodepoolsA
Read-only

List all node pools in a Kubernetes cluster. A cluster with no node pools runs no workloads.

Inputs: k8s_cluster_id (required), depth.

list_k8s_versionsA
Read-only

List all available Kubernetes versions in IONOS CLOUD. These are the versions a new cluster or node pool may be created with; to upgrade an existing one, use its availableUpgradeVersions instead (get_k8s_cluster / get_k8s_nodepool).

list_lan_nicsA
Read-only

List all NICs attached to a specific LAN

Inputs: lan_id (required), datacenter_id (required), depth, filters.

list_lansA
Read-only

List all LANs in a data center

Inputs: datacenter_id (required), depth, filters.

list_loadbalancer_nicsA
Read-only

List all NICs balanced by a specific load balancer

Inputs: datacenter_id (required), loadbalancer_id (required), depth, filters.

list_loadbalancersA
Read-only

List all load balancers in a data center

Inputs: datacenter_id (required), depth, filters.

list_locationsB
Read-only

List all available locations (regions) in IONOS CLOUD

Inputs: depth, filters.

list_nat_gateway_rulesA
Read-only

List all rules of a specific NAT gateway

Inputs: datacenter_id (required), nat_gateway_id (required), depth, filters.

list_nat_gatewaysA
Read-only

List all NAT gateways in a data center

Inputs: datacenter_id (required), depth, filters.

list_network_loadbalancersA
Read-only

List all network load balancers (NLB) in a data center

Inputs: datacenter_id (required), depth, filters.

list_nicsA
Read-only

List all network interfaces (NICs) attached to a server

Inputs: server_id (required), datacenter_id (required), depth, filters.

list_nlb_forwarding_rulesA
Read-only

List all forwarding rules of a network load balancer

Inputs: datacenter_id (required), network_loadbalancer_id (required), depth, filters.

list_object_storage_access_keysA

List all Object Storage access keys for the contract. Returns key IDs and metadata but not the secret keys.

list_object_storage_bucketsA

List all Object Storage buckets owned by the contract.

list_object_storage_objectsA

List objects in an Object Storage bucket. Supports an optional prefix to filter by key path (e.g. 'images/' to list only objects under that prefix), an optional continuation_token to continue from a previous page, and an optional max_keys to control page size. Returns up to 1000 objects per call by default; use the next_continuation_token from the response as continuation_token in a subsequent call to page through larger result sets.

Inputs: bucket (required), prefix, max_keys, continuation_token.

list_object_storage_object_versionsA

List all versions of objects in an Object Storage bucket. Requires versioning to be enabled on the bucket. Supports an optional prefix filter.

Inputs: bucket (required), prefix.

list_object_storage_regionsA

List all available Object Storage regions.

list_private_cross_connectsA
Read-only

List all private cross-connects in your IONOS CLOUD account

Inputs: depth, filters.

list_requestsA
Read-only

List all API requests in your IONOS CLOUD account

Inputs: depth, filters.

list_security_group_rulesB
Read-only

List all rules in a specific security group

Inputs: datacenter_id (required), security_group_id (required), depth, filters.

list_security_groupsA
Read-only

List all security groups in a data center

Inputs: datacenter_id (required), depth, filters.

list_server_cdromsA
Read-only

List all CD-ROMs attached to a specific server

Inputs: server_id (required), datacenter_id (required), depth, filters.

list_server_gpusA
Read-only

List all GPUs attached to a specific server

Inputs: server_id (required), datacenter_id (required), depth, filters.

list_serversA
Read-only

List all servers in a data center

Inputs: datacenter_id (required), depth, filters.

list_server_volumesA
Read-only

List all volumes attached to a specific server

Inputs: server_id (required), datacenter_id (required), depth, filters.

list_snapshotsA
Read-only

List all snapshots in your IONOS CLOUD account

Inputs: depth, filters.

list_target_groupsA
Read-only

List all target groups in your IONOS CLOUD account

Inputs: depth, filters.

list_templatesA
Read-only

List all available server templates in IONOS CLOUD

Inputs: depth, filters.

list_volumesA
Read-only

List all volumes in a data center

Inputs: datacenter_id (required), depth, filters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 118 tools

    Disambiguation5/5

    Each tool maps to a distinct resource and action (list vs get vs head), with no overlapping purposes. Even the many billing and object storage tools are clearly differentiated by resource type and operation.

    Naming Consistency4/5

    The set overwhelmingly follows a consistent list_<resource>/get_<resource> snake_case patterncars with occasional head_ for existence checks. The head_ prefix is a minor deviation but still forms a predictable semantic pattern.

    Tool Count1/5

    118 tools is an extreme count, far beyond the typical MCP server scope. While the IONOS Cloud platform is broad, this surface is unwieldy and likely causes selection overload for agents.

    Completeness2/5

    The tool set is entirely read-only (list/get/head), with no create, update, or delete operations for any resource. This leaves obvious lifecycle management gaps for a cloud platform, forcing agents into a dead end for most operational tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      MCP server for managing Incus containers and VMs via the incus CLI. Supports operations on remotes, instances, images, networks, storage, profiles, projects, and snapshots.
      -
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for Oracle Cloud Infrastructure (OCI) that provides tools to manage Compute, Object Storage, Block Storage, Networking, Autonomous Database, and IAM via the official OCI SDK.
      23
      MIT