Skip to main content
Glama
automatikstudio

BrandSnap MCP

by automatikstudio
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

BrandSnap MCP Server

An MCP (Model Context Protocol) server that wraps BrandSnap's brand identity generation API. Generate complete brand identity kits including colors, fonts, brand voice, logo direction, and social media guidelines.

Installation

npm install
npm run build

Configuration

Set your Anthropic API key:

export ANTHROPIC_API_KEY=your-api-key-here

Usage

As an MCP Server

Add to your MCP client configuration:

{
  "mcpServers": {
    "brandsnap": {
      "command": "node",
      "args": ["/path/to/brandsnap-mcp/dist/index.js"],
      "env": {
        "ANTHROPIC_API_KEY": "your-api-key"
      }
    }
  }
}

Development

# Run in development mode
npm run dev

# Run tests
npm test

Tool: generate_brand_identity

Generate a complete brand identity kit for a business.

Parameters

Parameter

Type

Required

Description

business_name

string

✅

The name of the business

industry

string

❌

Industry/sector (e.g., "Technology", "Healthcare")

values

string

✅

Business description, values, mission

tone

string

❌

Desired brand style (e.g., "Modern", "Playful")

Example

{
  "business_name": "TechFlow",
  "industry": "Software Development",
  "values": "We build elegant developer tools that make coding enjoyable. We value simplicity and beautiful design.",
  "tone": "Modern and Professional"
}

Response

Returns a comprehensive brand kit with:

  • colors - 5 harmonious colors with hex codes and usage guidelines

  • fonts - Heading and body font recommendations from Google Fonts

  • brandVoice - Tone, taglines, and voice description

  • logoDirection - Concept, style, and key visual elements

  • socialMedia - Platform-specific guidelines and sizing

Output Example

{
  "colors": [
    {
      "name": "Deep Ocean",
      "hex": "#0A2463",
      "usage": "Primary brand color for headers and CTAs"
    }
  ],
  "fonts": {
    "heading": {
      "name": "Inter",
      "weight": "Bold (700)",
      "style": "Sans-serif, modern and clean"
    },
    "body": {
      "name": "Inter",
      "weight": "Regular (400)",
      "style": "Sans-serif, highly readable"
    },
    "reasoning": "Inter provides a modern, technical feel..."
  },
  "brandVoice": {
    "tone": "Professional, Innovative, Approachable",
    "taglines": ["Code with clarity", "Developer joy, delivered"],
    "description": "Speak with confidence and technical expertise..."
  },
  "logoDirection": {
    "concept": "Abstract flow symbol representing code...",
    "style": "Geometric, minimal, modern",
    "elements": ["Flow lines", "Brackets", "Gradient accents"]
  },
  "socialMedia": {
    "profileGuidelines": "Use primary color as background...",
    "coverGuidelines": "Feature gradient with tagline...",
    "colorApplications": ["Use Deep Ocean for headers..."],
    "platforms": [
      { "name": "Instagram", "profileSize": "320x320px", "coverSize": "1080x1080px" }
    ]
  }
}

License

MIT

Available Tools

1 tool
generate_brand_identityC

Generate a complete brand identity kit including colors, fonts, brand voice, logo direction, and social media guidelines for a business.

ParametersJSON Schema
NameRequiredDescriptionDefault
business_nameYesThe name of the business
industryNoThe industry or sector the business operates in (e.g., 'Technology', 'Healthcare', 'Food & Beverage')
valuesYesA description of the business, its values, mission, and what makes it unique
toneNoThe desired style/tone for the brand (e.g., 'Modern', 'Classic', 'Playful', 'Professional', 'Minimalist')

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. While it implies a generative/creative operation, it lacks details on permissions, rate limits, output format, or whether the generation is deterministic or AI-based. For a tool with no annotations, this is a significant gap in transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the core purpose and lists key output components without unnecessary words. Every element earns its place by clarifying the tool's scope, making it appropriately sized and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of generating a brand identity kit, no annotations, and no output schema, the description is incomplete. It doesn't address behavioral aspects, output format, or limitations, leaving the agent with insufficient context for effective tool invocation beyond basic parameter usage.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four parameters thoroughly. The description does not add any meaning beyond what the schema provides—it mentions the output components but doesn't explain how inputs relate to them. Baseline 3 is appropriate when the schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Generate a complete brand identity kit' with specific components listed (colors, fonts, brand voice, logo direction, social media guidelines). It uses a specific verb ('generate') and resource ('brand identity kit'), but since there are no sibling tools, it cannot demonstrate differentiation from alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or exclusions. It simply states what the tool does without context about appropriate scenarios or limitations, leaving the agent to infer usage from the purpose alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedgenerate_brand_identity
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap with other tools. The tool's purpose is clearly defined and distinct by default.

Naming Consistency5/5

A single tool inherently has consistent naming, as there are no other tools to compare it against. The name 'generate_brand_identity' follows a clear verb_noun pattern.

Tool Count2/5

One tool is too few for a server named 'BrandSnap MCP', which suggests a broader brand-related domain. A single tool cannot adequately cover operations like editing, retrieving, or managing brand identities, making it feel thin and incomplete.

Completeness1/5

The server is severely incomplete for brand identity management. It only offers generation with no tools for retrieval, update, deletion, or other lifecycle operations, leaving significant gaps that will cause agent failures in practical workflows.

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/automatikstudio/brandsnap-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server