Connect to an AI Client

The MCP server works with any AI client that supports the Model Context Protocol. Select your client for step-by-step setup instructions.

Claude Code

Anthropic's CLI. Supports project-scoped .mcp.json for team sharing.

Claude Desktop

Anthropic's desktop AI app. Standard mcpServers config.

Cline

Open-source VS Code AI agent with MCP marketplace. Uses a separate cline_mcp_settings.json.

Continue

Open-source extension for VS Code and JetBrains. Agent mode only.

Cursor

AI-native IDE. Config via ~/.cursor/mcp.json.

Gemini CLI

Google's open-source terminal agent. Standard mcpServers config.

JetBrains AI Assistant

Built into IntelliJ-platform IDEs since 2025.2. Configured via IDE settings UI.

Kiro

AWS AI IDE for spec-driven development. Config via .kiro/settings/mcp.json.

OpenCode

Open-source terminal AI agent supporting 75+ models. Uses opencode.json with type: local.

VS Code

GitHub Copilot agent mode. Config via .vscode/mcp.json.

Windsurf

AI-native IDE by Codeium. Note: 100-tool limit applies.

Zed

High-performance code editor. Uses context_servers key.

Other MCP-Compatible Clients

Generic stdio config, plus notes on ChatGPT, n8n, and OpenAI Codex CLI.

Configuration reference

Most clients use the same mcpServers JSON structure. Point the client at the ionoscloud-mcp binary and pass your credentials as environment variables:

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

Three clients differ from this pattern: Zed uses a context_servers key with a different JSON structure. OpenCode uses a "type": "local" entry with a command array and an environment key instead of env. JetBrains AI Assistant is configured entirely through the IDE settings UI; no JSON file to edit.

For Object Storage tools, also add IONOS_S3_ACCESS_KEY and IONOS_S3_SECRET_KEY. For more information, see Authentication.

Add the IONOS CLOUD Documentation MCP

The IONOS CLOUD documentation site exposes a free, public MCP server at https://docs.ionos.com/cloud/~gitbook/mcp. Add it alongside the infrastructure server to give your AI assistant access to both live account data and product documentation in the same session:

{
  "mcpServers": {
    "ionoscloud-docs": {
      "url": "https://docs.ionos.com/cloud/~gitbook/mcp"
    },
    "ionoscloud": {
      "command": "/path/to/ionoscloud-mcp",
      "env": {
        "IONOS_TOKEN": "your-api-token"
      }
    }
  }
}

No credentials are required for the documentation server. The two servers are completely independent; use either one alone or both together.

Mixing url (remote, HTTP) and command (local, stdio) entries in the same mcpServers block is valid. Each entry uses its own transport; the AI client merges their tool catalogs automatically.

For more information, see Composing Multiple MCP Servers for example prompts.