Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@brand-asset-mcp show me the brand color palette"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
brand-asset-mcp)A shareable, lightweight Model Context Protocol (MCP) server for managing corporate brand assets, logos, color design tokens, social media templates, and image watermarking across multiple locations and platforms.
Brand Design Tokens: Exposes official HSL / Hex color palettes, typography rules, and theme variables via MCP resources (brand://tokens).
Logo & Badge Asset Library: Serves vector SVGs and PNG logo assets for Cape Fear Intel and Simpson Strong-Tie MCP platforms (brand://logos/{logo_id}).
Social Media Templates: Standardized layout schemas for LinkedIn, Instagram, X (Twitter), and YouTube OpenGraph cards (brand://templates/{template_id}).
Watermarking Tool: Fast image watermarking tool (watermark_image) that embeds official corporate branding and metadata badges into any generated image or render.
100% Rebuildable: Shareable via GitHub repository ChrisTansey007/brand-asset-mcp.
Related MCP server: OnBrand by SlideSpeak
git clone https://github.com/ChrisTansey007/brand-asset-mcp.git
cd brand-asset-mcp
uv sync
uv run python -m brand_asset_mcp.serverbrand://tokens: Get complete JSON design tokens (colors, fonts, radii, shadows).
brand://templates: List all social media post templates.
watermark_image: Apply brand logo watermark and metadata badge to an image file.
get_brand_palette: Tool returning specific color themes (dark mode, coastal marine, engineering accent).
Retrieve absolute file paths to all Tropical Tides logos, banners, watermarks, and social media icons.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses it returns absolute file paths for specific asset types, but does not describe output format, authentication needs, or error handling. Basic disclosure but missing details.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, under 20 words, front-loaded with purpose. No redundant information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 0 parameters and presence of output schema, description is complete. It specifies what the tool retrieves and the type of output (file paths). No gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has 0 parameters with 100% schema description coverage. Schema already covers everything, so no added value needed from description. Baseline 4 for 0 parameters.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'retrieve' and the resource 'absolute file paths to all Tropical Tides logos, banners, watermarks, and social media icons.' It distinguishes from siblings: get_brand_palette (palette colors) and watermark_image (applying watermark).
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when file paths to brand assets are needed, but lacks explicit guidance on when to use this tool versus siblings or alternatives. No exclusions or conditions are mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Retrieve color palette for themes: 'paper_and_ink', 'navy_band', 'coastal_marine', or 'engineering'.
| Name | Required | Description | Default |
|---|---|---|---|
| theme | No | paper_and_ink |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description bears full responsibility for behavioral disclosure. It only states the retrieval action and theme options, omitting any details about output format, error conditions, or side effects. This is insufficient for an agent to fully understand the tool's behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, front-loaded with the action 'Retrieve color palette'. It uses no unnecessary words and is highly efficient. Every part earns its place.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The tool is simple with one parameter, and the description covers its core purpose and allowed values. The presence of an output schema (though not shown) reduces the need for return-value details. The description is adequately complete for this low-complexity tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 0% description coverage, so the description must compensate for the 'theme' parameter. It lists four explicit string examples (paper_and_ink, navy_band, coastal_marine, engineering), effectively defining the allowed values. This adds significant meaning beyond the bare schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves a color palette for specific themes. It lists four named themes, making the purpose unambiguous. It distinguishes from siblings like get_brand_asset_paths and watermark_image, which have different functions.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for fetching a color palette for the listed themes, but does not provide explicit guidance on when to use this tool versus its siblings. No exclusions or when-not-to-use context is given, leaving the agent to infer utility from the theme list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Overlay an official Tropical Tides brand banner and watermark onto any generated graphic or photo.
| Name | Required | Description | Default |
|---|---|---|---|
| theme | No | navy_band | |
| image_path | Yes | ||
| output_path | Yes | ||
| watermark_text | No | TROPICAL TIDES • CAPE FEAR INTEL • SIMPSON MCP |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits. It only states the action but does not mention whether the original image is modified or a new file created, requirements for input, or side effects. Critical information is missing.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence, which is concise but overly brief given the tool's complexity. Important information is omitted, so brevity is not a virtue here.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given 4 parameters, no annotations, and an output schema (whose content is unavailable but the description doesn't mention returns), the description is inadequate. It does not explain the output format, edge cases, or parameter constraints.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema has 4 parameters with 0% description coverage, yet the description adds nothing about parameter meaning beyond their names. For example, 'theme' and 'watermark_text' have defaults but no explanation of valid values or format. The description fails to compensate for the schema's lack of documentation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's function: overlaying a brand banner and watermark onto an image. It uses a specific verb ('overlay') and resource ('graphic or photo'), distinguishing it from sibling tools that retrieve assets or palettes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance on when to use this tool versus alternatives (e.g., get_brand_asset_paths) or prerequisites such as input image format or permissions. An agent would have no context for appropriate invocation.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
v0.1.0get_brand_asset_pathsget_brand_palettewatermark_imageEach tool has a clearly distinct purpose: retrieving file paths, retrieving color palettes, and watermarking images. No overlap or ambiguity exists.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_brand_asset_paths), making them predictable and easy to understand.
With only 3 tools, the server covers a narrow range of operations. While not excessive, it feels thin for a brand asset server, bordering on insufficient for broader needs.
Obvious gaps exist: the server lacks tools for uploading, updating, or deleting assets, and returns only file paths rather than actual asset data. Core lifecycle operations are missing.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Brand-safe MCP for AI agents to create editable, on-brand graphics and automate variants.
Jinn gateway MCP — brand DNA, brand kits, design systems, and agency tools behind one bearer token.
Personal MCP server for humans who create. Proof of authorship, license control.
A hosted MCP server for planning, scheduling, media, analytics, and social publishing.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ChrisTansey007/brand-asset-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
