Claude Code Asset Generator MCP Server

Blueprint Studio

Blueprint Studio is a design and development studio. This plugin connects Claude Code and Codex to Blueprint Studio Asset Generator, so anyone can create on-brand images and visual assets with their own brand's Styles and logos. Studio clients also get the brand workspace our team maintains for them (official logos, brand guides and Styles) right inside their coding agent.

Your brand's Styles, official logos and guides, and asset library live in one place, shared with your team. Your agent uses them to make on-brand icons, social graphics, hero images and slides that match, and saves them to your project and your Asset Generator library. Workflow skills and agents are optional; tools can be used directly.

Using Claude on the web, desktop or mobile, ChatGPT, Cursor or VS Code instead? See Connect your AI.

This is the existing blueprint-studio plugin, upgraded in place. Its historical repository name remains claude-code-asset-generator to preserve installs. The public Blueprint marketplace remains the discovery source. No second plugin or private brand snapshot is required.

Install

Claude Code:

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

To connect, run /mcp, select plugin:blueprint-studio:asset-generator (Blueprint Studio) and choose Authenticate; if your browser can't connect after you approve, copy the link from the Blueprint Studio tab and paste it into Claude Code, or run /mcp → plugin:blueprint-studio:asset-generator → Authenticate again.

For a local branch preview, start Claude Code with --plugin-dir /absolute/path/to/this/repo. Avoid adding a second standalone MCP connection if the plugin already supplies asset-generator.

Codex uses the portable package with .codex-plugin/plugin.json retained for older clients. Install the same package through the existing marketplace:

codex plugin marketplace add https://github.com/Blueprint-Studio-AI/claude-code-marketplace.git
codex plugin add blueprint-studio@blueprint-studio-marketplace

Complete the host's MCP OAuth flow when prompted. Official ChatGPT/Codex and Claude directory reviews remain separate from direct installation.

First image

In Claude Code, run /blueprint-studio:start (or ask what Blueprint Studio Asset Generator can do). It reads the account, says what Asset Generator does and the real free allowance, offers three starters, then makes the image from one pick, saves it into the project and links it in Asset Generator. No brand or setup is needed.

Or ask for one directly, in any host:

Use Blueprint Studio Asset Generator to make a hero image for my website: a cozy neighborhood coffee shop at sunrise, warm light, 16:9

Then, so later images match your brand:

Set up my brand from mywebsite.com so my images match it

The server also offers these starters as MCP prompts: first_image, brand_from_website, app_icon and social_post. Claude Code lists them as slash commands, e.g. /mcp__plugin_blueprint-studio_asset-generator__first_image with this plugin. Claude Code passes only the first word of a prompt argument, so the image starters ask for one line instead of taking one; brand_from_website takes a website. Codex doesn't show MCP prompts; its plugin card offers the same starters (defaultPrompt).

Other skill-compatible hosts can use skills/ and connect their remote MCP client to https://tools.blueprintstudio.ai/api/mcp. plugin.json and mcp.json provide the portable Agent Plugins manifest. Host transport spellings differ; compatibility manifests are intentionally retained.

Sign in through the host's MCP OAuth flow for account-wide access. Start with get_workspace_context: it returns the plan, credits left, what a default image costs, accessible brands and, for new accounts, a getting-started plan. A new account needs no brand: null/omitted brandId creates in the personal library. To work in a brand, pass explicit brandId on every workspace call; null/omitted selects personal scope, not the last-used brand. Legacy scoped credentials cannot switch workspaces. A plugin install grants no membership. If an existing connection only lists one workspace despite broader account access, renew its OAuth authorization and start a fresh client/thread. Older workspace-only grants are not silently expanded; a new API key is not the repair. Service API keys remain available for scoped automation; inference provider keys are not needed and credentials never belong in checked-in files.

Tool contract

generate_asset already returns a durable jobId immediately. Use a fresh UUID requestId for each intended generation; reuse the same ID with identical arguments only for transport retries. Poll get_generation_status in the same brandId until completed or failed. Unknown outcomes and polling timeouts never establish failed generation or refunded credits. Preserve returned asset, receipt, and Style IDs. See the MCP contract for recovery and handoff details.

These capabilities require the current Blueprint server. Check live discovery for both tools and fields when connecting to an older deployment. Reference-set Style authoring, tracked forks, and Portal-backed tasks/approvals are not bundled features. There is no internal client list, private repository access, or automatic brand-site/database sync.

Optional skills and agents

• start: guided first run; three starters, then a first image saved into the project.
• asset-generator: browse, generate, inspect, refine, and deliver assets.
• brand-manager: requested workspace and Style administration.
• style-gym: optional repeatable Style experiments on diverse briefs.

Claude Code also discovers two agents from agents/: blueprint-studio:asset-creator for a bounded production brief and blueprint-studio:style-evaluator for requested Style comparisons. They inherit host tools and permissions, use the same asset-generator MCP connection, and add no mandatory routing. Other hosts can use the skills directly; agent auto-discovery is host-specific. See the Claude Code plugin agent format.

Suggested handoff to an existing project agent:

Use Blueprint Studio Asset Generator for this project's brand context and assets. Select the intended brand from list_brands and pass its brandId on each call. Inspect available Styles and any discovered brand guides/official assets. Continue the existing brief. Use tools directly or adapt the optional workflows; save selected asset/receipt/Style IDs and any unresolved job/request IDs with the work so another session can resume.

A project .blueprint.json may set local preferences. It is not an authorization mechanism. Do not duplicate live brand files into this plugin to personalize an installation.

One source for every platform

Edit shared content here once. Do not maintain copies of skills or generation logic for each host.

Run python3 scripts/sync_distribution.py after changing metadata. It generates .claude-plugin/plugin.json, .codex-plugin/plugin.json, .mcp.json, and server.json. Commit the generated files so hosts can install directly from Git. OpenAI and Cursor support the root Agent Plugins format; a separate Cursor source copy is unnecessary.

The historical marketplace repository is a stable discovery pointer, not another copy of the toolkit. Plugin releases take their version and metadata from this repository. See distribution and release instructions for local checks and official review boundaries.

Development

Backend and permission services live in the private monorepo; this public repository contains packaging and optional guidance only. Do not add tokens, production fixtures, client-private notes, or internal source links. Validate compatibility manifests and each skill before release. Public directory submission needs its own OAuth, metadata, and tool-annotation review.

Run the dependency-free checks locally:

python3 scripts/sync_distribution.py --check
python3 -m unittest discover -s scripts -p 'test_*.py'
claude plugin validate .

Also run the Codex plugin-creator validate_plugin.py and skill-creator quick_validate.py on each skills/* directory when available. Validation requires no generation calls or credentials. Installation, local cachebusting, and official directory release are distinct steps; bump the canonical release version rather than independently editing compatibility versions.

License

This public plugin package is MIT licensed. This does not license Blueprint Studio's separately hosted backend, private Style instructions, or client materials. Published MCP Registry metadata is separately dedicated to CC0 under the Registry terms.