No user-submitted related servers found.
Scored across 12 tools
Descriptions work hard to draw boundaries ("NOT for X — use Y"), and the core pipeline stages (start, compile, runtime, context, check) are mostly distinguishable. However, brand_report and brand_export ('team'/'pdf' targets) both produce brand guideline documents, and brand_check's 'css' mode overlaps directly with brand_preflight's anti-pattern checks. Worse, several descriptions redirect to tools that do not exist (brand_check_compliance, brand_audit, brand_audit_content, brand_preview), so an agent following the signposting hits dead ends.
All names are snake_case under a consistent 'brand_' prefix, with the related pair brand_brandcode_auth/connect grouped sensibly. The only deviation is a mix of verb-first (brand_start, brand_compile, brand_clarify) and noun-only (brand_status, brand_report, brand_runtime, brand_context, brand_preflight) forms, which is slightly inconsistent since brand_report and brand_preflight are actions despite being noun-shaped.
Twelve tools is well within a reasonable range for a brand-system lifecycle spanning ingest, compile, validate, and distribute. A couple of pairs (brand_report vs brand_export, brand_check vs brand_preflight) could plausibly be merged, but no tool is obviously redundant enough to feel padded.
The main lifecycle — adopt source, status, extract/compile, clarify, report, lint, export, share — is covered end to end. But the surface has real dead ends: brand_check_compliance, brand_audit, brand_audit_content, and brand_preview are explicitly referenced as the correct tool for certain tasks yet are absent, and there is no token-level edit/update or delete/reset operation beyond interactive clarification.
