> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/ai/mcp-server/connect-to-an-ai-client/claude-desktop.md).

# Claude Desktop

## Prerequisites

* [<mark style="color:blue;">Claude Desktop</mark>](https://claude.ai/download) installed on your machine
* The `ionoscloud-mcp` binary built and available. For more information, see [<mark style="color:blue;">Quick Start</mark>](/cloud/ai/mcp-server/quick-start.md)
* An <code class="expression">space.vars.ionos\_cloud\_api</code> token. For least-privilege access, see [<mark style="color:blue;">Authentication</mark>](/cloud/ai/mcp-server/configuration/authentication.md#token-scope-by-product-area) to scope the token to only the tools you need.

## Add the MCP server

Open the Claude Desktop configuration file:

* **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json` (`~` is shorthand for your home folder, for example `/Users/yourname`)
* **Windows:** `%APPDATA%\Claude\claude_desktop_config.json` (paste `%APPDATA%\Claude` into the File Explorer address bar to open the folder)

If the file does not exist, create it with your text editor (TextEdit on macOS, Notepad on Windows) at the path above. Paste the JSON below as the entire file contents:

```json
{
  "mcpServers": {
    "ionoscloud": {
      "command": "/usr/local/bin/ionoscloud-mcp",
      "env": {
        "IONOS_TOKEN": "your-api-token"
      }
    }
  }
}
```

To also enable Object Storage tools, add your Object Storage credentials:

```json
{
  "mcpServers": {
    "ionoscloud": {
      "command": "/usr/local/bin/ionoscloud-mcp",
      "env": {
        "IONOS_TOKEN": "your-api-token",
        "IONOS_S3_ACCESS_KEY": "your-access-key",
        "IONOS_S3_SECRET_KEY": "your-secret-key"
      }
    }
  }
}
```

## Restart and verify

{% stepper %}
{% step %}

### Restart Claude Desktop

Quit and reopen Claude Desktop.
{% endstep %}

{% step %}

### Open a new conversation

A hammer icon (🔨) appears in the input bar when MCP tools are available.
{% endstep %}

{% step %}

### Test the connection

Type a prompt such as: *List my* <code class="expression">space.vars.ionos\_cloud</code> *data centers.*

{% hint style="success" %}
**Result:** Claude responds with a list of your data centers: names, locations, and IDs.
{% endhint %}

If Claude responds with "I don't have access to tools for that" instead, Claude cannot reach the server. Check the [<mark style="color:blue;">Troubleshooting</mark>](/cloud/ai/mcp-server/troubleshooting.md) page.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Note:** All tools are registered at startup by default, so Claude Desktop sees Compute Engine and Object Storage tools immediately. To reduce the startup tool count, set `IONOS_MCP_LOAD_MODE=lazy` in your configuration and restart Claude Desktop; then ask Claude to load the Compute or Object Storage tools as needed. For more information, see [<mark style="color:blue;">Selective Tool Loading</mark>](/cloud/ai/mcp-server/configuration/selective-tool-loading.md).
{% endhint %}

For more on MCP support in Claude Desktop, see [<mark style="color:blue;">Getting started with local MCP servers</mark>](https://support.claude.com/en/articles/10949351-getting-started-with-local-mcp-servers-on-claude-desktop) in the Claude Help Center.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ionos.com/cloud/ai/mcp-server/connect-to-an-ai-client/claude-desktop.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.