brandsystem-mcp

Export brand guide

brand_export

Idempotent

Export the compiled brand system into a portable artifact for AI chat, code, team guidelines, email, Claude skill, or PDF, enabling consistent brand sharing across tools and teams.

Instructions

Bundle the compiled brand system into a portable artifact for a specific destination. Use when asked 'share my brand', 'export for ChatGPT/Cursor/team', 'generate brand guidelines', 'make a one-pager', or 'create a brand PDF'. Target 'chat': self-contained markdown for upload to any AI conversation (Claude, ChatGPT, Gemini). Target 'code': MCP server config + CLAUDE.md/.cursorrules snippet. Target 'team': human-readable brand guidelines for designers/writers/marketers. Target 'email': ~500-word summary for Slack or email. Target 'claude-skill': SKILL.md with embedded logo + rules for persistent Claude artifacts. Target 'pdf': branded PDF with swatches, type, anti-patterns, and voice. Set include_logo=false to drop the embedded SVG/data URI when size matters. Writes to .brand/exports/ and returns the full content (markdown targets) or a generation summary (pdf). Requires brand_compile to have run first. NOT for previewing one section — use brand_preview.

Input Schema

Name	Required	Description	Default
`target`	Yes	Where this export will be used. 'chat': upload to AI conversation (Claude/ChatGPT/Gemini). 'code': paste into CLAUDE.md or .cursorrules. 'team': share with designers/writers. 'email': send via Slack or email. 'claude-skill': persistent Claude skill file with embedded logo + brand rules. 'pdf': brand guide PDF with color swatches, typography, visual rules, and voice summary — no browser needed.
`include_logo`	No	Embed logo SVG/data URI in the export. Set false to reduce file size. Default: true.

Output Schema

Name	Required	Description	Default
`_metadata`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.17.0Oct 25, 2026
Removedv0.13.4Jul 18, 2026

Changed1 schema field changedv0.11.0Jul 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "_metadata": {
+      "additionalProperties": true,
+      "properties": {
+        "next_steps": {
+          "items": {
+            "type": "string"
+          },
+          "type": "array"
+        },
+        "what_happened": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "what_happened",
+        "next_steps"
+      ],
+      "type": "object"
+    }
+  },
+  "required": [
+    "_metadata"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedv0.9.2May 5, 2026

changedInput schema / properties / target / description

Previous value: -"Where this export will be used. 'chat': upload to AI conversation (Claude/ChatGPT/Gemini). 'code': paste into CLAUDE.md or .cursorrules. 'team': share with designers/writers. 'email': send via Slack or email. 'claude-skill': persistent Claude skill file with embedded logo + brand rules — the gold standard for automatic brand application in every artifact."New value: +"Where this export will be used. 'chat': upload to AI conversation (Claude/ChatGPT/Gemini). 'code': paste into CLAUDE.md or .cursorrules. 'team': share with designers/writers. 'email': send via Slack or email. 'claude-skill': persistent Claude skill file with embedded logo + brand rules. 'pdf': brand guide PDF with color swatches, typography, visual rules, and voice summary — no browser needed."

changedInput schema / properties / target / enum

Previous value: -[
-  "chat",
-  "code",
-  "team",
-  "email",
-  "claude-skill"
-]New value: +[
+  "chat",
+  "code",
+  "team",
+  "email",
+  "claude-skill",
+  "pdf"
+]

First observedv0.5.0Apr 14, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations mark this non-readOnly but idempotent and non-destructive; the description adds valuable context beyond that: it writes files to .brand/exports/<file>, returns full content for markdown targets versus a generation summary for pdf, and has a prerequisite compile step. It doesn't state overwrite behavior for existing files at the same path, which is the one remaining ambiguity.

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

Conciseness4/5

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

Front-loaded with purpose, then triggers, then per-target semantics — a sensible order. The target enumeration is long and partly redundant with the enum, but each clause is information-dense rather than filler.

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

Completeness4/5

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

With an output schema present, the description needn't explain return shapes, yet it helpfully notes that markdown targets return full content while pdf returns a summary. Prerequisite, write location, and sibling exclusion are all covered; only overwrite/collision behavior on repeated exports is unaddressed.

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 coverage is 100% and the enum already documents every target value, so the target enumeration mostly repeats structured data. The include_logo guidance ('set false to drop the embedded SVG/data URI when size matters') does add a decision rationale beyond the schema's terser 'reduce file size.' Baseline 3 is appropriate.

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

Purpose5/5

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

Opens with a specific verb+resource ('Bundle the compiled brand system into a portable artifact') and enumerates each target destination with what each produces. This makes the export capability fully distinguishable from siblings like brand_compile and brand_preview.

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

Usage Guidelines5/5

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

Gives concrete trigger phrases ('share my brand', 'export for ChatGPT/Cursor/team'), states a prerequisite (brand_compile must have run), and explicitly excludes the sibling case: 'NOT for previewing one section — use brand_preview.' Both when-to-use and when-not are covered.

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

Deploy Server