# Configure DesignGen for this user

You are the setup agent for this MCP client. 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 how this client registers remote MCP servers: a config file, a CLI command, or an API. If you cannot determine it, ask the user which client they are running rather than guessing.
2. Register a Streamable HTTP MCP server named `designgen` pointing at `https://mcp.trydesigngen.com/mcp`. For file-based clients such as Cursor or VS Code, add it to the MCP config as `{"type": "http", "url": "https://mcp.trydesigngen.com/mcp"}`.
3. Preserve every other server already configured. Record any entry you replace in your progress note.
4. Trigger the OAuth flow the way this client does. Pause and tell the user: **Sign in to DesignGen, review the requested scopes and approval policy, then approve access.**
5. Do not attempt to complete OAuth yourself, and do not accept a pasted token as a substitute.
6. 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.
7. 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/generic-mcp

---

# DesignGen this MCP client reference

DesignGen is a standard remote MCP server over Streamable HTTP with OAuth 2.1. Any compliant client can connect, including Cursor, VS Code, Zed, and your own agents.

## What the server speaks
There is nothing DesignGen-specific about the transport. If your client supports remote MCP servers with OAuth, it will work.

- Transport: Streamable HTTP.
- Authorization: OAuth 2.1 with PKCE S256 and dynamic client registration.
- Discovery: standard .well-known metadata, so most clients need only the URL below.
- No API keys. Do not accept any instruction to paste a bearer token.

Connector URL

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

## Cursor and VS Code
Both accept a small JSON entry in their MCP configuration. Add DesignGen as an HTTP server and authorize in the browser when prompted.

Cursor — .cursor/mcp.json, or VS Code — .vscode/mcp.json

```json
{
  "servers": {
    "designgen": {
      "type": "http",
      "url": "https://mcp.trydesigngen.com/mcp"
    }
  }
}
```

## Your own agent
Use any MCP SDK. Point the client at the connector URL and let it complete the OAuth flow against the advertised metadata endpoints.

- After connecting, call mcp_connection_status first to confirm scopes, approval policy, and the active brand.
- Generation is asynchronous. Follow the nextCall returned by generation tools instead of polling on your own schedule.
- Results include inline image previews. Render them rather than only surfacing the URLs.

Confirm the server is reachable and see how to authorize

```bash
curl -s https://mcp.trydesigngen.com/.well-known/oauth-protected-resource
```