For the complete documentation index, see llms.txt. This page is also available as Markdown.

Zed

Zed is a high-performance code editor with built-in MCP support. Zed uses a context_servers configuration key rather than mcpServers.

Prerequisites

  • Zed installed. For more information, see zed.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

Open or create ~/.config/zed/settings.json and add a context_servers block:

{
  "context_servers": {
    "ionoscloud": {
      "source": "custom",
      "command": {
        "path": "/usr/local/bin/ionoscloud-mcp",
        "args": [],
        "env": {
          "IONOS_TOKEN": "your-api-token"
        }
      }
    }
  }
}

To also enable Object Storage tools:

Note: Zed uses context_servers (not mcpServers) and wraps the command in a command object with path, args, and env fields. The structure differs from other MCP clients.

Verify the connection

1

Reload Zed

Save the settings file. Zed picks up context server changes automatically; reload the window if the server does not appear.

2

Test in Assistant panel

Open the Zed Assistant panel and type: List my IONOS CLOUD 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 Zed MCP documentation, see zed.dev/docs/ai/mcp.

Last updated

Was this helpful?