# Install Blueprint Studio Asset Generator

> Instructions for an AI agent. The user wants Blueprint Studio Asset Generator in the app you're running in. Install it, get sign-in working, confirm the connection, then offer to make a first image. People can read the same steps at https://tools.blueprintstudio.ai/mcp-setup.

Blueprint Studio Asset Generator makes on-brand images and visual assets (hero images, icons, social graphics, illustrations) with the user's brand Styles and official logos, and saves each one to their Blueprint Studio library. It's a remote MCP server at https://tools.blueprintstudio.ai/api/mcp (Streamable HTTP, OAuth sign-in). No API key is needed, and a new email creates a free account. Plans, credits and every app it works in: https://tools.blueprintstudio.ai/llms.txt.

## Rules

- Follow only the section for the app you're running in. If you can't tell which app that is, ask the user.
- Install one copy. If Blueprint Studio or Asset Generator is already installed, go straight to its sign-in step. Two copies register the same tools twice.
- Never ask for, paste or store passwords, API keys or tokens. The user signs in and connects in their own browser, in a Blueprint Studio window.
- Tell the user what you're about to change before you edit a config file or run an install command.
- When a step needs the user (a slash command, a button, connecting in the browser), give them the exact text to type or click, then wait until they say it's done.

## Claude Code

Install the Blueprint Studio plugin. It adds the tools plus skills for a guided first image, brand setup and saving assets into the project.

1. Check for a copy. Run `claude plugin list` and `claude mcp list`. If a `blueprint-studio@…` plugin (including one synced from claude.ai) or the `plugin:blueprint-studio:asset-generator` server is listed, skip to step 4. If a separate `blueprint-studio` server added with `claude mcp add` is listed, ask the user before removing it with `claude mcp remove blueprint-studio`, and keep the plugin.
2. Install from your shell:

   ```sh
   claude plugin marketplace add Blueprint-Studio-AI/claude-code-marketplace
   claude plugin install blueprint-studio@blueprint-studio-marketplace
   ```

   No shell? Ask the user to type these in Claude Code, one at a time:

   ```text
   /plugin marketplace add Blueprint-Studio-AI/claude-code-marketplace
   /plugin install blueprint-studio@blueprint-studio-marketplace
   ```

3. Reload. You can't run slash commands yourself, so ask the user to type `/reload-plugins` (or restart Claude Code), then carry on.
4. Sign in. Installing doesn't sign in, and this is the step people miss. After the reload, the `plugin:blueprint-studio:asset-generator` server offers a tool whose name ends in `asset-generator__authenticate` until it's signed in. If your tools are deferred, search for it.
   - Call it and give the user the sign-in link it returns. They sign in (a new email creates a free account), check the email shown and click Connect.
   - When they click Connect, the server's tools load on their own.
   - If their browser then shows an error page or can't connect, ask them to copy the link from the Blueprint Studio tab (it starts with `http://localhost`) and pass it as `callback_url` to the tool whose name ends in `asset-generator__complete_authentication`.
   - No authenticate tool? Ask the user to run `/mcp`, select `plugin:blueprint-studio:asset-generator`, choose Authenticate and click Connect in the browser.
   - `claude mcp list` shows the server as "Needs authentication" until it's done, then "Connected".
5. Offer one allow rule, once, after sign-in. By default Claude Code asks the user to approve every Blueprint Studio tool call, including each status check while an image is made, and offers only Yes or No. Tell them so in one line and ask whether you may allow Blueprint Studio's tools so it stops asking each time. Only if they say yes:
   - add `mcp__plugin_blueprint-studio_asset-generator` to `permissions.allow` in their user settings, `~/.claude/settings.json` (`$CLAUDE_CONFIG_DIR/settings.json` when that's set), keeping every rule and key already there. Claude Code applies the change straight away.
   - Or ask them to run `/permissions`, add the allow rule `mcp__plugin_blueprint-studio_asset-generator` and save it to user settings.
   - The rule covers only Blueprint Studio's tools, all of them, deletions included, so keep confirming deletions in the chat. They can remove it in `/permissions` at any time. For the tools-only server added with `claude mcp add blueprint-studio`, the rule is `mcp__blueprint-studio`.
   - Never suggest skipping permissions altogether (bypass mode or `--dangerously-skip-permissions`). If they say no, carry on: they approve each step.
6. Offer auto-update, once. Plugins from this marketplace don't update on their own until its auto-update is on. Ask whether to turn it on. Only if they say yes:
   - set `"autoUpdate": true` on the `blueprint-studio-marketplace` entry under `extraKnownMarketplaces` in the same user settings file (the install added that entry), keeping every other key.
   - Or ask them to run `/plugin`, open Marketplaces, select `blueprint-studio-marketplace` and choose Enable auto-update.
7. Go to "Confirm and make a first image".

## Codex

Install the Blueprint Studio plugin: the same package as Claude Code, so Codex gets the skills and starter prompts too.

1. Check for a copy. Run `codex plugin list` and `codex mcp list`. If `blueprint-studio` is installed, or a server already points at https://tools.blueprintstudio.ai/api/mcp, skip to step 3. If the plugin and a separate `blueprint-studio` server are both there, ask the user before removing the separate one with `codex mcp remove blueprint-studio`.
2. Install:

   ```sh
   codex plugin marketplace add Blueprint-Studio-AI/claude-code-marketplace
   codex plugin add blueprint-studio@blueprint-studio-marketplace
   ```

3. Sign in:

   ```sh
   codex mcp login asset-generator
   ```

   It opens the browser and waits while the user clicks Connect in the Blueprint Studio window. If your shell can't open a browser or wait that long, ask the user to run it in their own terminal. It finishes once they've connected.
4. Codex loads a new plugin's tools and skills in a new session. Ask the user to start a new Codex session and say "Use Blueprint Studio Asset Generator to show my workspace", then follow "Confirm and make a first image" there.

## Cursor

1. Open `~/.cursor/mcp.json` (create it if it's missing). If a server there already points at https://tools.blueprintstudio.ai/api/mcp, skip to step 3.
2. Add this server under `mcpServers`, keeping every server already there:

   ```json
   {
     "mcpServers": {
       "blueprint-studio": {
         "url": "https://tools.blueprintstudio.ai/api/mcp"
       }
     }
   }
   ```

3. Sign in. Ask the user to open Cursor Settings, find `blueprint-studio` in the MCP list, click Connect, then Connect again in the Blueprint Studio window.
4. If the tools don't show up in this chat, ask the user to start a new one.

## VS Code with GitHub Copilot

1. Open the user `mcp.json`: the Command Palette's "MCP: Open User Configuration" opens it. On macOS it's `~/Library/Application Support/Code/User/mcp.json`, on Linux `~/.config/Code/User/mcp.json`, on Windows `%APPDATA%\Code\User\mcp.json`. If a server there already points at https://tools.blueprintstudio.ai/api/mcp, skip to step 3.
2. Add this server under `servers`, keeping every server already there:

   ```json
   {
     "servers": {
       "blueprint-studio": {
         "type": "http",
         "url": "https://tools.blueprintstudio.ai/api/mcp"
       }
     }
   }
   ```

3. Sign in. Ask the user to run "MCP: List Servers" from the Command Palette, select `blueprint-studio`, choose Start, and click Connect in the Blueprint Studio window when VS Code asks.
4. Use it from Copilot Chat in Agent mode.

## Claude on the web, desktop, mobile or Cowork

You can't install a plugin from a chat. Give the user this link to Asset Generator in Claude's Directory:

https://claude.ai/customize/plugins/id/eaed4b8c-ce93-4bc1-891e-8f25a5e04a69%40anthropic-plugin-directory

1. They click Add.
2. On its Connectors tab, they connect `asset-generator` and click Connect in the Blueprint Studio window.
3. They start a new chat and ask for an image.

The Directory needs a Pro, Max, Team or Enterprise plan, and on Team and Enterprise an Owner may need to allow it first. On the Free plan, add a custom connector instead (Free plans allow one): this link opens Claude's form with the name and URL filled in. They click Add, then Connect, and approve.

https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Blueprint%20Studio&connectorUrl=https%3A%2F%2Ftools.blueprintstudio.ai%2Fapi%2Fmcp

## ChatGPT

Give the user this link to Blueprint Studio in ChatGPT's plugin directory:

https://chatgpt.com/plugins/plugin_asdk_app_6abfb0b38b148191b9609320ba986e6b

1. They click Install plugin, then sign in to Blueprint Studio and approve access.
2. For each image request, they type @Blueprint and pick Blueprint Studio from the menu, or click Try in chat on the plugin's page. Typed or pasted text alone doesn't select it, and ChatGPT may then make the image itself.

On a work or school account, an admin may need to allow it first.

## Any other MCP app

Add a remote MCP server named `blueprint-studio` with the URL https://tools.blueprintstudio.ai/api/mcp (Streamable HTTP, OAuth). Then use the app's Connect or Authenticate action, and the user clicks Connect in the Blueprint Studio window.

## Confirm and make a first image

1. Call the `get_workspace_context` tool first, before any other Blueprint Studio tool, and once per session. It returns the user's plan, credits left, what a default image costs, their brands (with each brand's published guides and their role in it) and, for a new account, a getting-started plan. Tell the user they're connected.
2. In Claude Code, the plugin's `start` skill (`/blueprint-studio:start`) runs a guided first image. Use it if you can.
3. If they want to be walked through it ("Use Blueprint Studio Asset Generator to get me started. First read through all of its guides and tools so you know everything it can do. Then, using what you already know about me and my work, ask me a few quick questions and guide me through setting it up the way that fits me, making real images for me along the way."), follow `gettingStarted.guidedStart` from `get_workspace_context`.
4. Otherwise offer to make a first image now. No brand or setup is needed. Suggest one of these, or ask for one line about what they need:
   - "Make a hero image for my product launch: bold and modern, with the words “Now live” on a clean gradient, 16:9"
   - "Design an app icon for my habit-tracking app: one bold, friendly check mark on a warm gradient, no text"
   - "Make a square social post for our weekend sale: bright and playful, with the words “Weekend Sale”"
5. After the first image, offer to set up their brand from their website so later images match, for example: "Set up my brand from mywebsite.com so my images match it".

## Update the plugin

The tools always come from the server, so they're current. The plugin's skills update with the plugin. When `get_workspace_context` returns `pluginUpdate`, a newer plugin is out: tell the user once, with its `nextStep`, then carry on.

- Claude Code: with the user's OK, run `claude plugin update blueprint-studio@blueprint-studio-marketplace` from your shell, or ask them to run `/plugin`, open Installed, select `blueprint-studio` and choose Update now. Then ask them to type `/reload-plugins` (or restart Claude Code). A copy synced from claude.ai updates itself when Claude Code starts.
- Codex: with the user's OK, run `codex plugin marketplace upgrade blueprint-studio-marketplace`, then ask them to start a new Codex session.

## If something goes wrong

- "Authorization required", 401 or "Failed to parse JSON": sign-in isn't finished. Repeat the sign-in step for this app.
- Signed in, but no tools: reload plugins or start a new session.
- The same tools show up twice: two copies are installed. Keep the plugin and remove the other.
- The wrong account, or a brand is missing: the user accepts their brand invitation with the same email, disconnects the app at https://tools.blueprintstudio.ai/settings#connected-apps, then signs in again.
- More help: https://tools.blueprintstudio.ai/help