Blueprint Studio
Connect your AI
API DocsLaunch App
Getting Started
  • Overview
  • Setup
  • Your account
  • Try it
Configuration
  • Project Config
Tools
  • Asset Generation
  • Brand Management
  • Team Management
  • Styles
  • Generation Helpers
  • API Keys
Reference
  • Usage Examples
  • Troubleshooting

Connect Blueprint Studio

Bring your Styles, official logos, and asset library into your AI app. Sign in with your Blueprint account and create in your personal library or the brands you already use.

New to a team? Accept your Blueprint invitation first, using the same email you’ll connect with. Image generation uses your existing Blueprint credits. No provider API key is needed.

1. Connect your AI app

Run these commands separately inside Claude Code. Choose user scope to use Blueprint across your projects.

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

Follow any reload instructions, then open /mcp and authenticate the Blueprint connection it shows. The plugin includes the tools and optional skills for asset creation and Style experiments; no separate MCP setup is needed.

Claude Code setup reference

2. Authorize your Blueprint account

Follow the sign-in link opened by your AI app. Sign in or create your account, check the email shown, then choose Authorize. If you’re already signed in, you can go straight to authorization.

Sign in or create an account. A new email creates one automatically.

One connection covers your personal library and every Blueprint brand you can access. Your existing permissions still apply. Ask your AI to use the brand you want; you don’t need to reconnect to switch. You don’t need a brand to connect, and installing the tools does not grant team membership. Disconnect an app anytime in Settings.

3. Try the connection

Paste this into a conversation with Blueprint enabled. This checks access without generating an image.

Use Blueprint Studio to list my brands and personal Styles. Then show the Styles, official logos, and brand guides for the brand I choose. Don't generate or change anything yet.

Then give your AI a creative brief.

Project Configuration

Create an optional .blueprint.json file in your project root as guidance for your agent. It does not change server defaults or grant access. Keep credentials out of this file.

{
  "outputDir": "./public/assets",
  "defaultStyleId": "your-style-id",
  "defaultAspectRatio": "1:1",
  "defaultImageSize": "2K"
}
FieldTypeDescription
outputDirstringWhere to save downloaded assets default: ./public/assets
defaultStyleIdstringPreferred Style for your agent to select
defaultAspectRatiostringDefault aspect ratio default: 1:1
defaultImageSizestringOutput resolution default: 2K

Tool reference

Asset Generation

10 tools
generate_assetStart a durable generation or exact-parent edit; returns a job ID to track
list_assetsBrowse generated assets with filtering and pagination
get_assetGet full details for a specific asset
get_generation_statusCheck an existing generation job until it finishes
get_generation_detailsInspect saved generation settings and Style provenance
delete_assetDelete an asset
download_assetDownload an asset as base64-encoded image data
favorite_assetToggle favorite status on an asset
remove_backgroundRemove the background from an asset image
share_assetGenerate a public shareable URL for an asset

Brand Management

7 tools
create_brandCreate a new brand/organization
list_brandsList brands you belong to
get_brandGet brand details, settings, and member count
get_workspace_contextRead brand permissions and published brand guide links
list_brand_assetsFind official logos and versioned generation references
update_brand_settingsUpdate default style or prompt template
delete_brandDelete a brand (owner only)

Team Management

4 tools
invite_memberInvite a user by email with a role
list_membersList members and pending invites
update_member_roleChange a member's role (admin/member)
remove_memberRemove a member from a brand

Styles

6 tools
list_stylesList available generation styles (system + custom)
create_styleCreate a custom brand style
get_styleGet style details and reference images
update_styleUpdate a custom style
delete_styleDelete a custom style
set_style_thumbnailChoose a representative generation for a Style’s thumbnail

Generation Helpers

3 tools
list_modelsDiscover supported models, settings, and credit costs
suggest_promptsGet AI-powered prompt suggestions based on a style
generate_ideasBrainstorm asset concept ideas for a topic

API Keys

3 tools
create_api_keyCreate a new API key for automation and CI/CD
list_api_keysList active keys with usage metadata
revoke_api_keyPermanently revoke an API key

Usage Examples

Generate an asset with a specific style

> "Generate a minimalist coffee cup icon using my brand style,
   save it to public/icons/coffee.png"

Set up a new brand with team members

> "Create a brand called 'Acme Design', then invite
   alice@acme.com and bob@acme.com as members"

Create a custom style and generate assets

> "Create a style called 'Neon Retro' with a cyberpunk
   aesthetic, then generate 3 icon ideas using it"

Manage API keys for CI/CD

> "Create an API key called 'GitHub Actions' for my CI pipeline"
> "List my API keys and revoke any unused ones"

Troubleshooting

“Failed to parse JSON” or “Authorization required”

Click “Authenticate” in the MCP server status panel. Your browser will open to complete the OAuth flow.

Authentication succeeds but tools don't appear

Complete authentication, enable Blueprint in this conversation, then reload or start a fresh session as your app instructs. If the plugin already supplies the connection, do not add a duplicate server.

Tools return “Access denied”

Check your signed-in email and brand membership. New connections cover your account; your AI must select the intended brand. If an old connection only sees one brand, renew its authorization and start a fresh session. You do not need a separate API key.

Using an API key instead of OAuth

Existing scoped API keys still work for automation. Browser authorization is the usual connection method for your AI app. See the API documentation for service integrations; never commit a key to your project.

REST API DocsLaunch AppPlugin Source