Skip to main content
Glama
Shopify Checkout Branding MCP Tool

Shopify Checkout Branding MCP Tool

by shandut

Shopify Checkout Branding MCP Tool

A Model Context Protocol (MCP) server for comprehensive Shopify checkout branding management through AI-powered tools. This production-ready server enables AI assistants like Claude and Cursor to programmatically customize every aspect of your Shopify Plus checkout - from colors and typography to sections, form controls, and complete design systems.

πŸš€ Production-Ready: Full API compatibility, intelligent value mapping, enhanced tool descriptions, and safety-first defaults for accurate AI-driven checkout customization.

βœ… Cursor MCP Support Fixed!

The MCP server now works correctly with Cursor. The JSON communication issue has been resolved. See CURSOR-MCP-SETUP.md for details.

Related MCP server: Figma Copilot

🎯 Quick Start

For Claude Desktop Users

  1. Install and configure:

# Clone and setup
git clone https://github.com/shandut/Shopify-Checkout-Branding-MCP-Tool.git
cd shopify-checkout-mcp-tool
npm install
npm run build

# Create .env file with your credentials
cp env.template .env
# Edit .env with your Shopify store details
  1. Configure Claude Desktop (see Configuration section below)

  2. Use natural language in Claude:

  • "Show me all checkout profiles"

  • "Center the logo and make it 150px wide"

  • "Change the primary color to #5A31F4"

For Cursor/HTTP API Users

  1. Start the HTTP server:

npm run start:http
  1. Test the API:

node test-http.js

πŸš€ Features

Core Tools

  • List Checkout Profiles: Retrieve all checkout profiles with TEST/PUBLISHED status

  • Read Current Branding: Get complete branding configuration and design system

  • Update Branding: Comprehensive customization with intelligent defaults

    • πŸ”’ Safety Feature: Automatically targets TEST/draft profile by default

    • Use useProductionProfile: true to explicitly update live checkout

  • Upload Logos: Stream images from URLs directly to Shopify CDN

  • Upload Custom Fonts: Upload WOFF/WOFF2/TTF/OTF fonts for unique typography

Styling Capabilities

  • Colors: Background, text, primary (buttons), surface colors with hex validation

  • Typography: Font families (Shopify or custom), weights (100-900), base size (12-16), ratios (1.0-1.5)

    • Custom font support for primary (body text) and secondary (headings) surfaces

    • Configurable font loading strategies (BLOCK, SWAP, FALLBACK, OPTIONAL)

  • Corner Radius: NONE, SMALL, BASE, LARGE for all elements

  • Shadows: 5 levels (SMALL_100, SMALL_200, BASE, LARGE_100, LARGE_200)

  • Padding: 14 variants (NONE through LARGE_500)

  • Sections: Independent main area and order summary styling with dividers

  • Form Controls: Borders, labels (INSIDE/OUTSIDE), corner radius

  • Color Schemes: 4 schemes for different section contexts

  • Header: Logo visibility, banner images, cart links, alignment, dividers

  • Background Images: Support for header banner, main area, order summary

  • Container Dividers: Configurable style (BASE/DASHED/DOTTED), width, visibility

  • Cart Link: Custom content type (ICON/IMAGE/TEXT) with image support

API Intelligence

  • Multi-version Support: Compatible with API versions 2024-10 through 2026-01

  • Value Mapping: Automatic conversion for API compatibility

  • Enhanced Descriptions: Detailed tool documentation for better AI understanding

  • Error Recovery: Intelligent handling of validation errors

πŸ“‹ Prerequisites

  • Node.js 18+ with TypeScript support

  • Shopify store with Admin API access

  • Shopify Admin API token with appropriate scopes:

    • read_checkout_branding_settings

    • write_checkout_branding_settings

    • write_files (for logo uploads)

πŸ› οΈ Installation

⚠️ Security Note

Never commit your actual API credentials to version control!

  • Copy env.template to .env for your credentials

  • .env is already in .gitignore to prevent accidental commits

  • All example configurations use placeholder values

Setup Steps

  1. Clone the repository:

git clone https://github.com/shandut/Shopify-Checkout-Branding-MCP-Tool.git
cd shopify-checkout-mcp-tool
  1. Install dependencies:

npm install
  1. Build the project:

npm run build
  1. Configure environment variables:

cp env.template .env

Edit .env with your Shopify credentials:

SHOPIFY_STORE_DOMAIN=your-store.myshopify.com
SHOPIFY_ADMIN_TOKEN=shpat_your_admin_api_token_here
SHOPIFY_API_VERSION=2026-01
PORT=8787  # Only if using HTTP wrapper

πŸ”§ Configuration

For Claude Desktop

Add to your Claude Desktop configuration file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "shopify-checkout": {
      "command": "node",
      "args": ["/path/to/shopify-checkout-mcp-tool/dist/index.js"],
      "env": {
        "SHOPIFY_STORE_DOMAIN": "your-store.myshopify.com",
        "SHOPIFY_ADMIN_TOKEN": "shpat_your_admin_api_token_here",
        "SHOPIFY_API_VERSION": "2026-01"
      }
    }
  }
}

For Cursor or Other Tools (HTTP Mode)

Run with HTTP wrapper enabled:

npm run start:http

The server will be available at http://localhost:8787

πŸ“š Available MCP Tools

1. shopify_list_checkout_profiles

Lists all checkout profiles in your store.

Input: None required Output: Array of profiles with id, name, and status

2. shopify_get_checkout_branding

Retrieves current branding settings for a specific profile.

Input:

  • profileId (string): Shopify GID of the checkout profile

Output: Current logo configuration and color scheme

3. shopify_update_checkout_branding

Updates branding settings for a checkout profile. πŸ”’ Defaults to TEST profile for safety.

Input:

  • profileId (string, optional): Shopify GID - if not provided, auto-selects TEST profile

  • useProductionProfile (boolean, optional): Set to true to update live checkout (default: false)

  • logoWidth (number, optional): Width in pixels (1-1000)

  • logoPosition (enum, optional): "LEFT", "CENTER", or "RIGHT"

  • colors (object, optional):

    • background: Hex color (e.g., "#FFFFFF")

    • surface: Hex color

    • text: Hex color

    • primary: Hex color for buttons

    • primaryText: Hex color for button text

  • control (object, optional): Form control styling

    • color: "TRANSPARENT"

    • border: "NONE" or "FULL"

    • cornerRadius: Corner style

    • labelPosition: "INSIDE" or "OUTSIDE"

  • imageId (string, optional): ID of uploaded logo

4. shopify_upload_logo_from_url

Uploads an image from a URL to Shopify Files.

Input:

  • url (string, required): Public HTTPS URL of the image

  • filename (string, optional): Desired filename

  • mimeType (string, optional): Image MIME type

Output: Image ID and CDN URL for use in branding updates

5. shopify_upload_custom_font_from_url

Uploads a custom font file from a URL to Shopify Files for use in checkout typography.

Input:

  • url (string, required): Public HTTPS URL of the font file (WOFF, WOFF2, TTF, or OTF)

  • filename (string, optional): Desired filename for the font

  • mimeType (string, optional): Font MIME type (auto-detected if not provided)

  • fontWeight (number, optional): Font weight (100-900, default 400 for regular, 700 for bold)

  • isBold (boolean, optional): Mark as bold variant (sets weight to 700)

Output:

  • genericFileId: File ID to use in checkout branding configuration

  • url: CDN URL of the uploaded font

  • weight: Font weight value

  • filename: The filename of the uploaded font

πŸ’‘ Usage Examples

Via MCP (in Claude Desktop)

After configuring Claude Desktop, you can use natural language:

"Can you reduce my checkout logo width by half and center it?"

Claude will:

  1. Call shopify_get_checkout_branding to get current width

  2. Calculate new width (50% of current)

  3. Call shopify_update_checkout_branding with new settings

  4. Verify changes with another shopify_get_checkout_branding call

Via HTTP API (for Cursor)

# List all checkout profiles
curl http://localhost:8787/profiles

# Get current branding
curl http://localhost:8787/profiles/gid://shopify/CheckoutProfile/123/branding

# Update branding (safer - auto-targets TEST profile)
curl -X POST http://localhost:8787/branding \
  -H "Content-Type: application/json" \
  -d '{
    "logoWidth": 150,
    "logoPosition": "CENTER",
    "colors": {
      "primary": "#5A31F4",
      "background": "#FFFFFF"
    }
  }'

# Update production checkout (explicit)
curl -X POST http://localhost:8787/branding \
  -H "Content-Type: application/json" \
  -d '{
    "useProductionProfile": true,
    "logoWidth": 150,
    "colors": {
      "primary": "#5A31F4"
    }
  }'

# Upload new logo
curl -X POST http://localhost:8787/files \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/new-logo.png",
    "filename": "checkout-logo.png"
  }'

# Upload custom fonts
curl -X POST http://localhost:8787/fonts \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://example.com/myfont-regular.woff2",
    "fontWeight": 400
  }'

# Apply custom font to checkout
curl -X POST http://localhost:8787/branding \
  -H "Content-Type: application/json" \
  -d '{
    "designSystem": {
      "typography": {
        "primary": {
          "customFontGroup": {
            "base": {
              "genericFileId": "gid://shopify/GenericFile/123456",
              "weight": 400
            },
            "bold": {
              "genericFileId": "gid://shopify/GenericFile/789012",
              "weight": 700
            },
            "loadingStrategy": "SWAP"
          }
        }
      }
    }
  }'

πŸ—οΈ Architecture

src/
β”œβ”€β”€ index.ts           # Application entry point
β”œβ”€β”€ mcpServer.ts       # MCP server implementation
β”œβ”€β”€ httpServer.ts      # Optional Fastify HTTP wrapper
β”œβ”€β”€ shopify.ts         # GraphQL client for Shopify API
β”œβ”€β”€ branding.ts        # Business logic for branding operations
β”œβ”€β”€ schemas.ts         # Zod schemas for validation
└── logging.ts         # Pino logger with security redaction

πŸ” Security

  • Token Protection: API tokens are never logged or exposed in responses

  • Input Validation: All inputs validated using Zod schemas

  • Rate Limiting: Automatic retry with exponential backoff for Shopify API limits

  • HTTPS Only: Only accepts HTTPS URLs for image uploads

  • Scoped Permissions: Limited to checkout branding and file operations

πŸ§ͺ Testing

Run tests:

npm test

Test against a development store:

npm run test:integration

πŸ“ Development

Start development server with hot reload:

npm run dev

Build for production:

npm run build

Start production server:

npm start

🚦 Error Handling

The server handles various error scenarios:

  • 400: Invalid input or validation errors

  • 403: Missing required Shopify API scopes

  • 429: Rate limited (automatic retry with backoff)

  • 500: Unexpected server errors

🀝 Contributing

  1. Fork the repository

  2. Create a feature branch (git checkout -b feature/amazing-feature)

  3. Commit your changes (git commit -m 'Add amazing feature')

  4. Push to the branch (git push origin feature/amazing-feature)

  5. Open a Pull Request

πŸ“„ License

This project is licensed under the MIT License - see the LICENSE file for details.

⚠️ Known Limitations & Important Notes

Typography Field Restrictions

The customizations.global.typography field has strict limitations:

  • βœ… Allowed: kerning (BASE, LOOSE, EXTRA_LOOSE), letterCase (NONE, LOWER, TITLE, UPPER)

  • ❌ NOT Allowed: font, size, weight (use designSystem.typography for these)

Other API Limitations

  • Global Corner Radius: Only accepts NONE value

  • Control Color: Only accepts TRANSPARENT value

  • Logo Format: SVG files cannot be used for checkout logos

  • Enum Values: Some enum values differ between API versions (e.g., UPPER vs UPPERCASE)

πŸ†˜ Support

For issues, questions, or suggestions:

  • Open an issue on GitHub

  • Check existing issues for solutions

  • Review Shopify Admin API documentation

πŸ—ΊοΈ Roadmap

  • Support for multiple store configurations

  • Bulk profile updates

  • Preview generation before applying changes

  • Backup and restore functionality

  • WebSocket support for real-time updates

  • Integration with Shopify webhooks

  • Support for theme-based branding

  • A/B testing capabilities

Available Tools

5 tools
shopify_get_checkout_brandingA

Retrieve complete checkout branding configuration including design system and customizations.

  Returns two main sections:
  1. DESIGN SYSTEM: Foundation settings for colors, typography, corner radius
     - colors.global.brand: The PRIMARY BUTTON COLOR
     - colors.schemes: Detailed color schemes with primaryButton, secondaryButton, control colors
     - typography: Font families and sizes
  
  2. CUSTOMIZATIONS: Specific UI element settings
     - HEADER: Logo (visibility, maxWidth), banner image, cartLink (contentType, image), divided, alignment, padding
     - FOOTER: Content visibility, color scheme, padding
     - MAIN: Background image, section styling, divider settings
     - ORDER SUMMARY: Background image, section styling, divider settings
     - primaryButton, secondaryButton, control, textField, select elements
  
  The profileId is optional - defaults to TEST profile for safety.

Inputs: profileId.

shopify_list_checkout_profilesA

List all checkout profiles in a Shopify Plus store. Returns both TEST/draft and PUBLISHED/live profiles with their IDs, names, and publication status.

  Use this to:
  - Identify available checkout profiles before making updates
  - Find the TEST profile ID for safe testing (isPublished: false)
  - Find the PRODUCTION profile ID for live updates (isPublished: true)
  
  Note: Most stores have 2 profiles - one TEST and one PUBLISHED. Always prefer updating TEST profile first.

Inputs: no named parameters.

shopify_update_checkout_brandingA

Update checkout branding using Shopify's CheckoutBrandingUpsert API.

  πŸ”’ SAFETY: Defaults to TEST/draft profile unless useProductionProfile:true or explicit profileId provided.
  
  🎨 PRIMARY BUTTON COLOR:
  The primary button (Pay Now) color is controlled by:
  β€’ globalBrand: Sets the brand color (EASIEST - just pass hex color)
  β€’ OR designSystem.colors.global.brand: Same as above but in full structure
  β€’ OR designSystem.colors.schemes.scheme1.primaryButton: For detailed control including hover states
  β€’ NOT colors.primary - this field is deprecated, use globalBrand instead
  
  πŸ“š COMPREHENSIVE CAPABILITIES:
  
  DESIGN SYSTEM (Foundation):
  β€’ GLOBAL COLORS:
    - brand: Primary buttons and brand elements (#FF6B00 for orange)
    - accent: Links and focus states
    - success, warning, critical, info: Semantic colors
    - decorative: Highlight colors
  β€’ COLOR SCHEMES (scheme1-4): Each can have:
    - base: Background, text, border, icon, accent colors
    - primaryButton: Background, text, hover state colors
    - secondaryButton: Secondary action button colors
    - control: Form field colors with selected state
  β€’ TYPOGRAPHY:
    - primary/secondary fonts (e.g., "Assistant", "Roboto", "Montserrat")
    - Font weights, sizes, letter spacing
    - Size base (12-18px) and ratio (1.0-1.5)
  β€’ CORNER RADIUS: Variables for small, base, large radii
  
  CUSTOMIZATIONS (Specific Elements):
  β€’ HEADER:
    - Logo: position, width (50-500px), visibility (VISIBLE/HIDDEN)
    - Banner: background image via mediaImageId
    - CartLink: contentType (ICON/IMAGE/TEXT), custom image
    - Alignment, divided (true/false), padding, color scheme
    - Position mapping: LEFT→START, CENTER→INLINE, RIGHT→INLINE_SECONDARY
  β€’ FOOTER: 
    - Content visibility, color scheme
    - padding: NONE|BASE|BASE_500|SMALL|SMALL_100-500|LARGE|LARGE_100-500 (section values)
  β€’ MAIN AREA:
    - Section: 
      * background: BASE|SUBDUED|TRANSPARENT (accepts SOLID→BASE, NONE→TRANSPARENT)
      * shadow: SMALL_100|SMALL_200|BASE|LARGE_100|LARGE_200 (NO 'NONE' or 'BASE_200'!)
      * cornerRadius: NONE|SMALL|BASE|LARGE
      * padding: NONE|BASE|BASE_500|SMALL|SMALL_100-500|LARGE|LARGE_100-500 (NOT button values!)
      * border: NONE|FULL
      * borderWidth: BASE|LARGE|LARGE_100|LARGE_200 (NOT 'NONE' or 'MEDIUM'!)
    - Background image via mediaImageId
    - Divider: borderStyle (BASE/DASHED/DOTTED), borderWidth (BASE|LARGE|LARGE_100|LARGE_200), visibility
    - Color scheme: COLOR_SCHEME1|COLOR_SCHEME2|COLOR_SCHEME3|COLOR_SCHEME4
  β€’ ORDER SUMMARY:
    - Section: Same exact values as main area
    - Background image support
    - Independent divider settings with visibility
    - Separate color scheme
  β€’ CONTENT:
    - Divider: borderStyle, borderWidth, visibility (container divider)
  β€’ GLOBAL DIVIDER:
    - borderStyle (BASE/DASHED/DOTTED), borderWidth (NONE/BASE/MEDIUM)
    - Note: NO visibility on global divider (customizations.divider)
  β€’ BUTTONS:
    - primaryButton/secondaryButton:
      * background: NONE|SOLID
      * border: NONE|FULL
      * cornerRadius: NONE|SMALL|BASE|LARGE
      * blockPadding/inlinePadding: NONE|EXTRA_TIGHT|TIGHT|BASE|LOOSE|EXTRA_LOOSE
      * typography: font, size, weight (BASE|BOLD), kerning, letterCase (NONE|LOWER|TITLE|UPPER)
  β€’ FORM CONTROLS:
    - border: NONE|FULL (exactly these two)
    - color: TRANSPARENT (ONLY this value accepted!)
    - cornerRadius: NONE|SMALL|BASE|LARGE
    - labelPosition: INSIDE|OUTSIDE
  β€’ TEXT FIELDS & SELECTS: Border, typography styling
  β€’ CHECKBOXES: Corner radius
  β€’ HEADINGS: Typography for 3 levels
  β€’ MERCHANDISE THUMBNAILS: Corner radius, border
  β€’ EXPRESS CHECKOUT: Button corner radius
  β€’ OTHER: Choice lists, buyer journey, cart link, dividers, content borders
  
  SIMPLIFIED OPTIONS (for convenience):
  ‒ colors: {background, text, primary→brand, surface} - Legacy support
  β€’ globalBrand: Direct way to set primary button color
  β€’ primaryButtonColor: Override primary button background
  β€’ typography: Simplified font settings
  β€’ logoPosition, logoWidth, imageId: Direct logo control
  
  USAGE EXAMPLES:
  1. Set orange primary button: globalBrand: "#FF6B00"
  2. Full brand colors: designSystem.colors.global.brand: "#FF6B00"
  3. Detailed button control: designSystem.colors.schemes.scheme1.primaryButton.background: "#FF6B00"
  
  API NOTES & CRITICAL ENUM VALUES:
  - SHADOW: ONLY 5 valid values: SMALL_100, SMALL_200, BASE, LARGE_100, LARGE_200
    * NO 'NONE' (use SMALL_100), NO 'BASE_200' (use LARGE_100)
  - BACKGROUND: BASE, SUBDUED, TRANSPARENT (NOT 'SOLID' or 'NONE')
    * Tool maps SOLID→BASE, NONE→TRANSPARENT automatically
  - PADDING: Sections use different values than buttons!
    * Sections: NONE|BASE|BASE_500|SMALL|SMALL_100-500|LARGE|LARGE_100-500
    * Buttons: NONE|EXTRA_TIGHT|TIGHT|BASE|LOOSE|EXTRA_LOOSE
  - BORDERWIDTH: Different for sections vs global divider!
    * Sections/container dividers: BASE|LARGE|LARGE_100|LARGE_200 (NO 'MEDIUM')
    * Global divider: NONE|BASE|MEDIUM
  - DIVIDERS: Global (customizations.divider) has NO visibility field
    * Container dividers (main.divider, orderSummary.divider) DO have visibility
  - letterCase: UPPER not UPPERCASE
  - globalCornerRadius: ONLY accepts NONE (API limitation)
  - control.color: ONLY accepts TRANSPARENT (API limitation)
  - Position: LEFT→START, CENTER→INLINE, RIGHT→INLINE_SECONDARY
  - Changes to TEST profile can be previewed
  - PUBLISHED profile changes are immediately live

Inputs: useProductionProfile (required), profileId, colors, logoPosition, +7 more.

shopify_upload_custom_font_from_urlA

Upload a custom font from a public HTTPS URL to Shopify Files for use in checkout branding.

  🎨 CUSTOM FONTS ENABLE UNIQUE TYPOGRAPHY:
  Custom fonts allow merchants to use their brand's specific typeface in checkout, creating a cohesive brand experience.
  
  πŸ“‹ REQUIREMENTS:
  - Font must be in WOFF, WOFF2, TTF, or OTF format (WOFF2 recommended for best performance)
  - URL must be publicly accessible (no authentication)
  - URL must use HTTPS protocol
  - Store must have appropriate webfont license for commercial use
  
  πŸ”„ PROCESS:
  1. Downloads font from provided URL
  2. Uploads to Shopify's CDN as a generic file
  3. Returns genericFileId to use with checkout branding
  
  βš™οΈ PARAMETERS:
  - url: HTTPS URL of the font file (required)
  - filename: Optional custom filename (auto-extracted from URL if not provided)
  - mimeType: Optional MIME type (auto-detected from extension: woff2, woff, ttf, otf)
  - fontWeight: Optional weight value 100-900 (default: 400 for regular, 700 for bold)
  - isBold: Optional boolean to mark as bold variant (sets weight to 700)
  
  πŸ’‘ USAGE WITH CHECKOUT BRANDING:
  After uploading, use the returned genericFileId in shopify_update_checkout_branding:
  
  Example for primary font (body text):
  {
    "designSystem": {
      "typography": {
        "primary": {
          "customFontGroup": {
            "base": {
              "genericFileId": "returned_id",
              "weight": 400
            },
            "bold": {
              "genericFileId": "returned_bold_id",
              "weight": 700
            },
            "loadingStrategy": "SWAP"
          }
        }
      }
    }
  }
  
  Example for secondary font (headings):
  {
    "designSystem": {
      "typography": {
        "secondary": {
          "customFontGroup": {
            "base": {
              "genericFileId": "returned_id",
              "weight": 400
            },
            "bold": {
              "genericFileId": "returned_bold_id",
              "weight": 700
            }
          }
        }
      }
    }
  }
  
  πŸš€ LOADING STRATEGIES:
  - BLOCK: Block text rendering until font loads (not recommended)
  - SWAP: Show fallback font immediately, swap when custom font loads (recommended)
  - FALLBACK: Short block period, then fallback if not loaded
  - OPTIONAL: Very short block period, may not swap if slow to load
  
  πŸ“ COMPLETE WORKFLOW:
  1. Upload regular font: shopify_upload_custom_font_from_url(url: "https://example.com/myfont-regular.woff2")
  2. Upload bold font: shopify_upload_custom_font_from_url(url: "https://example.com/myfont-bold.woff2", isBold: true)
  3. Apply to checkout: shopify_update_checkout_branding with customFontGroup configuration

Inputs: url (required), filename, mimeType, fontWeight, +1 more.

shopify_upload_logo_from_urlA

Upload a logo image from a public HTTPS URL to Shopify Files for use in checkout branding.

  Process:
  1. Downloads image from provided URL
  2. Uploads to Shopify's CDN via staged upload
  3. Returns imageId to use with shopify_update_checkout_branding
  
  Requirements:
  - URL must be publicly accessible (no authentication)
  - URL must use HTTPS protocol
  - Supported formats: PNG, JPG, WEBP (not SVG for checkout logos)
  - Recommended dimensions: 200-600px width, maintain aspect ratio
  
  Use the returned imageId with shopify_update_checkout_branding to apply the logo.
  
  Example workflow:
  1. Upload logo: shopify_upload_logo_from_url(url: "https://example.com/logo.png")
  2. Apply to checkout: shopify_update_checkout_branding(imageId: returned_id, logoWidth: 150)

Inputs: url (required), filename, mimeType.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.3/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: getting branding, listing profiles, updating branding, uploading fonts, and uploading logos. No overlapping functionality.

    Naming Consistency5/5

    All tools follow a consistent 'shopify_verb_noun' pattern (e.g., get_checkout_branding, list_checkout_profiles, update_checkout_branding, upload_custom_font_from_url, upload_logo_from_url).

    Tool Count5/5

    With 5 tools, the set is well-scoped for a checkout branding server: profile listing, branding retrieval/update, and asset uploads. Neither too few nor too many.

    Completeness4/5

    Covers core workflows: get/list profiles, get/update branding, and upload fonts/logos. Minor gap: no delete functionality for branding or profiles, but these are often available via other means.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to read and modify Figma designs programmatically, supporting design analysis, element creation, text replacement, annotations, auto-layout configuration, and prototype visualization through natural language commands.
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to interact with Figma designs programmatically, supporting comprehensive design automation including text manipulation with formatting preservation, batch operations, prototyping, auto-layout configuration, and component management.
      75
      23 npm
      5
      MIT
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI coding assistants to inspect frontend projects, search a curated design and motion recipe catalog, prepare and preview structured design plans, apply changes with backups and rollback, capture previews, audit UI accessibility and performance, and monitor activity via a web dashboard.
      -