Zed

Zed talks stdio MCP natively. For remote HTTPS servers like Creatorland, the `mcp-remote` npm bridge handles the HTTP transport from inside `settings.json`.

Setup

Zed

Zed, Zed natively supports stdio MCP servers. For streaming HTTP servers like Creatorland’s, use the mcp-remote npm bridge as a local stdio shim. Add a context_servers entry to your settings.json (Command Palette → zed: open settings):

{
  "context_servers": {
    "creatorland": {
      "source": "custom",
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.creatorland.com/mcp"]
    }
  }
}

mcp-remote handles the HTTPS round-trips and the OAuth flow so Zed sees a normal stdio MCP server. Watch the Agent Panel for the active indicator next to “creatorland”, green means the bridge is connected and authenticated.

Recent Zed builds also accept a direct "url" field for some servers. If you’re on a bleeding-edge build and prefer no bridge, replace the entry with { "url": "https://mcp.creatorland.com/mcp" } and remove the command / args keys.

Loading setup…

Who it’s for: Developers using Zed’s Agent Panel for AI-assisted editing.
Compatibility: Zed’s native MCP transport is stdio. For streaming HTTP servers, Zed’s docs recommend the [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) npm bridge, it runs `npx -y mcp-remote {url}` as a local subprocess that handles the HTTPS round-trips and OAuth. Recent Zed builds also accept a direct `"url"` field on `context_servers` entries; both paths work, the bridge is the more broadly compatible default.
Verify the connection: After you sign in with your Creatorland account, your tools appear in the client, scoped to your account. If the list comes back empty, that signals the email you signed in with has no Creatorland account yet, create one (or sign in with the right one) at creatorland.com and reconnect. An empty list still confirms the OAuth handshake succeeded and you’re pointed at the right server.

Troubleshooting

Zed reloads MCP servers automatically after `settings.json` saves, watch the Agent Panel for a green active indicator next to “creatorland.”
If `mcp-remote` isn’t found, ensure `npx` is on your PATH (it ships with Node.js, a recent Node install satisfies this).
A red indicator usually means the OAuth flow failed; check Zed’s log panel for the `mcp-remote` subprocess output.

Other clients

OpenClaw Other clients

Claude