Kiro

Kiro is a GA AI IDE from AWS built for spec-driven development. It supports MCP natively with standard mcpServers JSON configuration.

Prerequisites

• Kiro installed. For more information, see kiro.dev
• The ionoscloud-mcp binary built and available. For more information, see Quick Start
• An IONOS CLOUD API token. For least-privilege access, see Authentication to scope the token to only the tools you need.

Add the MCP server

Create or edit .kiro/settings/mcp.json in your workspace:

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

To also enable Object Storage tools:

{
  "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"
      }
    }
  }
}

For a user-wide configuration that applies to all projects, use ~/.kiro/settings/mcp.json instead. Workspace config takes precedence when both exist.

Kiro supports environment variable interpolation using ${VARIABLE_NAME} syntax. This is the recommended approach for team configs where each developer supplies their own credentials:

"env": {
  "IONOS_TOKEN": "${IONOS_TOKEN}"
}

Kiro also supports per-tool settings within the server entry:

"ionoscloud": {
  "command": "/usr/local/bin/ionoscloud-mcp",
  "env": { "IONOS_TOKEN": "your-api-token" },
  "autoApprove": ["list_datacenters", "list_servers"],
  "disabledTools": []
}

autoApprove lists tools Kiro runs without asking for confirmation. disabledTools hides specific tools from the AI's catalog.

Kiro-specific feature: autoApprove and disabledTools are Kiro IDE settings; they are not features of the MCP server itself. Other AI clients (Claude Desktop, Cursor, VS Code, etc.) do not support per-tool approval or disabling at the config level. The MCP server exposes all registered tools to whichever client connects.

Verify the connection

1

Open Kiro and start a chat

Open the Kiro Agent panel.

2

Test the connection

Type: List my IONOS CLOUD data centers.

Result: Kiro calls list_datacenters and returns your data centers.

Note: All tools are registered at startup by default, so Compute Engine and Object Storage tools appear immediately. To reduce the startup tool count (for example, on clients with a tool-count cap), set IONOS_MCP_LOAD_MODE=lazy in the env block and call the ionos_load_compute_tools or ionos_load_objectstorage_tools sentinels on demand. For more information, see Selective Tool Loading.

For full Kiro MCP documentation including security settings, see kiro.dev/docs/mcp.