Agent-assisted setup

Connect DesignGen to OpenCode

Add DesignGen as a remote MCP server in your OpenCode config, authorize in the browser, and use print-prep tools from the terminal.

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 OpenCode. 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

    OpenCode 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 OpenCode.
  • Choosing the approval policy you are comfortable with.
  • Approving or denying the OAuth connection.

Fastest setup: hand this page to your agent

OpenCode can edit its own config. Use Copy setup for your agent at the top of this page; the brief covers both config schemas.

  • OpenCode handles OAuth for remote MCP servers automatically.
  • Prefer HTTP streamable transport. OpenCode has known issues with SSE-based servers.
  • Leave every other server in the config untouched.

Check your config schema first

The schema changed between major versions, so confirm which one you are running before pasting a block.

  • v1 puts servers directly under `mcp` and uses an `enabled` field.
  • v2 puts them under `mcp.servers` and replaces `enabled` with `disabled`.
  • Do not configure an Authorization header. DesignGen signs in through OAuth.

v1 config

{
  "mcp": {
    "designgen": {
      "type": "remote",
      "url": "https://mcp.trydesigngen.com/mcp"
    }
  }
}

v2 config

{
  "mcp": {
    "servers": {
      "designgen": {
        "type": "remote",
        "url": "https://mcp.trydesigngen.com/mcp"
      }
    }
  }
}

Authorize and verify

OpenCode opens the DesignGen sign-in the first time it connects.

  • Review the requested scopes and the approval policy before approving.
  • Then call mcp_connection_status and report the client, scopes and active brand.

Check and debug the connection

opencode mcp auth list
opencode mcp debug designgen