Blueprint Studio
MCP Setup
API DocsLaunch App
Getting Started
  • Overview
  • Setup
  • Authentication
Configuration
  • Project Config
Tools
  • Asset Generation
  • Brand Management
  • Team Management
  • Styles
  • Generation Helpers
  • API Keys
Reference
  • Usage Examples
  • Troubleshooting

MCP Server for Claude Code

Connect Claude Code to Blueprint Studio via the Model Context Protocol (MCP). Generate assets, manage brands, invite team members, and more — all through natural conversation.

27
Tools Available
6
Categories
OAuth
Authentication

Setup

1. Add the MCP server to Claude Code

Add the following to your Claude Code MCP settings (.claude/settings.json or via the Claude Code settings UI):

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

2. Authenticate

When Claude Code connects, your browser will open automatically to sign in with your Blueprint Studio account. Once authorized, the connection persists — no API keys to manage.

3. Start using it

Ask Claude naturally — it has access to all 27 tools:

> "Generate a settings icon in my brand style"
> "Invite alice@example.com to my brand"
> "Create a new brand called Acme Design"
> "List my styles and suggest some prompts"

Authentication

The MCP server uses OAuth 2.1 with PKCE for secure browser-based authentication. This is the same flow used by Figma, Linear, and other MCP servers.

How it works

  1. Claude Code discovers auth is required via /.well-known/oauth-authorization-server
  2. Your browser opens to sign in with your Blueprint Studio account
  3. You choose which brand to authorize (or “Personal” for no brand)
  4. A secure token is issued — Claude Code stores it automatically
  5. Token refreshes automatically, no re-authentication needed

API keys still work. If you have existing API keys (bp_live_...), they continue to work alongside OAuth. You can also create and manage API keys through the MCP tools for CI/CD and automation.

Project Configuration

Create an optional .blueprint.json file in your project root to set defaults. This is safe to commit to git — it contains no auth information.

{
  "outputDir": "./public/assets",
  "defaultStyleId": "your-style-id",
  "defaultAspectRatio": "1:1",
  "defaultImageSize": "2K"
}
FieldTypeDescription
outputDirstringWhere to save downloaded assets default: ./public/assets
defaultStyleIdstringStyle to use when none is specified
defaultAspectRatiostringDefault aspect ratio default: 1:1
defaultImageSizestringOutput resolution default: 2K

Available Tools

Asset Generation

8 tools
generate_assetGenerate an image from a prompt with style, aspect ratio, and resolution options
list_assetsBrowse generated assets with filtering and pagination
get_assetGet full details for a specific asset
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

5 tools
create_brandCreate a new brand/organization
list_brandsList brands you belong to
get_brandGet brand details, settings, and member count
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

5 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

Generation Helpers

2 tools
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

Try “Reconnect” in the MCP status panel. If that fails, remove and re-add the server URL in your settings.

Tools return “Access denied”

Your OAuth token is scoped to the brand you selected during authentication. To switch brands, disconnect and re-authenticate.

Using an API key instead of OAuth

You can use an API key by adding a headers field to your MCP config:

{
  "mcpServers": {
    "blueprint-studio": {
      "url": "https://tools.blueprintstudio.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer bp_live_your_key_here"
      }
    }
  }
}
REST API DocsLaunch AppPlugin Source