DesignGen

Agent-assisted setup

Connect DesignGen to other editors and terminals

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

View raw MarkdownOpen Account CenterReview MCP plan access

The copied brief contains the MCP command, a self-contained DesignGen skill, OAuth handoff instructions, and a read-only verification checklist. It never includes a token or authorizes paid work.

Secure handoff

Let your agent configure everything it safely can.

Paste the copied Markdown into this editor. It will inspect existing configuration, add DesignGen MCP, install the workflow skill where supported, and open OAuth. Your account and approval choices stay with you.

  1. 01

    Copy the setup

    One button copies the complete agent-readable brief.

  2. 02

    Agent configures

    this editor adds MCP and installs the DesignGen skill where supported.

  3. 03

    You authorize

    Sign in, review scopes and policy, then approve access.

Your agent handles

  • Checks existing MCP configuration before changing it.
  • Adds the production Streamable HTTP endpoint.
  • Installs the self-contained DesignGen workflow skill.
  • Verifies OAuth and connection status without spending credits.

Only you handle

  • Signing in to your DesignGen account.
  • Reviewing the scopes requested by this editor.
  • Choosing the approval policy you are comfortable with.
  • Approving or denying the OAuth connection.

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

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

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