At a glance
- Availability: Experimental (how to enable).
- Auth: API key.
- Connection: The key from
IONOS_TOKENis sent as theBearerprefixedAuthorizationheader. - Docs: https://docs.ionos.com/cloud/reference/get-started
Credentials
Set these per environment. See Connect an integration.| Variable | Required | Description |
|---|---|---|
IONOS_TOKEN | Yes | IONOS Cloud bearer token, generated via the Token Manager in the DCD or GET https://api.ionos.com/auth/v1/tokens/generate; same env var used by ionosctl and the IONOS SDKs Docs. |
Setup
- Get an IONOS Cloud account: Sign up at https://cloud.ionos.com - new accounts typically include trial credit. Log into the Data Center Designer (DCD) at https://dcd.ionos.com.
- Generate a bearer token: In the DCD open Management > Token Manager and generate a token, or call GET https://api.ionos.com/auth/v1/tokens/generate with Basic auth (Base64 of username:password). Tokens are required if 2FA is enabled.
- Set the environment variable: Copy the token into your .env as IONOS_TOKEN.
- Verify access: Run List Data Centers (depth=1), then List Servers for one of the returned data center IDs.
- All Cloud API v6 paths live under https://api.ionos.com/cloudapi/v6
- The depth query parameter (0-10) controls how deeply nested resources are expanded; depth=0 returns only IDs
- Stopping a server is a forceful power-off; shut down the OS first for clean stops
- Write requests return 202 Accepted and complete asynchronously - check the server’s vmState afterwards
Tools
| Tool | Access | Description |
|---|---|---|
| List Data Centers | Read | List virtual data centers in the account; each data center contains servers, volumes, and networks |
| List Servers | Read | List servers inside a virtual data center |
| Get Server | Read | Get a server in a data center, including name, vmState, cores, RAM, and boot device |
| Start Server | Write | Start (power on) an Enterprise server; CUBE servers cannot be started with this endpoint (they use suspend/resume instead) |
| Stop Server | Write | Stop (power off) an Enterprise server; the server is forcefully powered off and billing for compute stops; public IPv4 addresses that are not reserved are returned to the IPv4 pool (reserved IPs are kept). CUBE servers cannot be stopped with this endpoint (they use suspend/resume instead) |
| Reboot Server | Write | Force a hard reboot of a server (equivalent to powering it down and back on) - recovers hung servers without a separate stop/start cycle; not a graceful OS reboot |
| Get Request Status | Read | Poll the status of an asynchronous write operation (202 Accepted responses) until it reports DONE or FAILED; the request ID comes from the Location response header of the write call |
Example prompts
- List my IONOS Cloud virtual data centers and the servers inside each, with their power state.
- Find the IONOS server I name and stop it after confirming with me.