# Configure DesignGen for this user

You are the setup agent for this editor. Complete every machine-owned step below. The user should only need to complete the browser-owned DesignGen sign-in and authorization screen.

## Completion criteria

- A Streamable HTTP MCP server named `designgen` points to `https://mcp.trydesigngen.com/mcp`.
- The DesignGen OAuth login has been opened for the user.
- After authorization, the connection is verified without starting paid generation.

## Safety boundaries

- Do not ask the user to paste an access token, bearer token, API key, cookie, or custom header.
- Do not make an approval or autonomy-policy choice for the user.
- Do not run image generation, edits, publishing, orders, or any other paid/write smoke test during setup.
- Modify only the `designgen` MCP entry and the DesignGen skill directory. Preserve all unrelated agent configuration.

## Agent-owned setup steps

1. Identify which client you are running in before writing any config. Windsurf, Zed, Cline, Goose, Raycast and Warp all differ in where the server goes and what the key is called.
2. Register a Streamable HTTP MCP server named `designgen` pointing at `https://mcp.trydesigngen.com/mcp`.
3. Windsurf names the field `serverUrl`, not `url`. Using `url` there is the usual reason a Windsurf setup silently fails.
4. In Zed, leave headers empty: a configured Authorization header makes it skip OAuth entirely.
5. In Raycast, choose the dynamic OAuth type; DesignGen supports dynamic client registration.
6. Preserve every other configured server, and record any entry you replace in your progress note.
7. Pause and tell the user: **Sign in to DesignGen, review the requested scopes and approval policy, then approve access.**
8. If newly added tools are not visible, tell the user to restart or reload the client. Do not treat a stale tool list as a failed OAuth grant.
9. Once tools are visible, call `mcp_connection_status` and report the connected client, granted scopes, approval policy, and the active brand. Do not call a paid or write tool.

## Success message

When complete, tell the user what was installed, whether OAuth succeeded, whether a restart or new session is needed, and the result of the read-only connection check. Never claim setup is complete before authorization succeeds.

Source guide: https://www.trydesigngen.com/agents/designgen/editors

---

# DesignGen this editor reference

Config for Windsurf, Zed, Cline, Goose, Raycast and Warp. All of them reach DesignGen over Streamable HTTP and sign in through the browser.

## The same server everywhere
Every client below connects to one production endpoint over Streamable HTTP and authorizes with browser OAuth. What differs is the config key and where you put it.

- DesignGen supports dynamic client registration, so clients that offer a dynamic OAuth mode can register themselves.
- Never configure a static Authorization header. A pasted token is not a supported setup.
- Preserve every other MCP server already configured, and note anything you replace.

Production MCP endpoint

```text
https://mcp.trydesigngen.com/mcp
```

## Windsurf
Windsurf uses `serverUrl` where most clients use `url`. Copying another client config verbatim is the usual reason a Windsurf setup fails.

Windsurf MCP config entry

```json
{
  "mcpServers": {
    "designgen": {
      "serverUrl": "https://mcp.trydesigngen.com/mcp"
    }
  }
}
```

## Zed, Cline and Goose
All three add a remote server and complete OAuth in the browser. Goose connects over streamable HTTP natively.

- Add the production URL as a remote or HTTP MCP server in the client settings.
- Let the client open the DesignGen sign-in rather than supplying credentials yourself.
- In Zed, setting an Authorization header makes it skip OAuth entirely. Leave headers empty.

## Raycast and Warp
Both support remote servers with browser sign-in.

- In Raycast, choose the dynamic OAuth type. DesignGen supports dynamic client registration.
- Warp offers one-click OAuth for remote servers; paste the production URL and approve.
- After either, call mcp_connection_status and report the client, scopes and approval policy.