Skip to main content
Glama

Related Servers

Alternatives to brandsystem-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Deterministically generates brand and design artefacts (logo SVG, colour palette, type system, design tokens) with signed, 0G-anchored provenance receipts, plus paid tools for social kits, revisions, and verification.
      1
      -
    • A
      license
      Not graded
      quality
      F
      maintenance
      Generates complete brand identity systems including colors, typography, logos, and design tokens with 58 MCP tools. Supports multi-format export and AI-assisted refinement.
      87 npm
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to retrieve and compare current brand data, inspect colors and fonts, enrich transaction descriptors, and access approved private assets using fourteen shared tools across isolated named profiles.
      14
      20 npm
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Serves an editable folder of plain brand files—identity, colours, fonts, rules, formats and examples—to any AI tool over MCP, so generated designs and copy come out on-brand. It also checks HTML, CSS, SVG and text against those rules, and can read a public site's CSS to extract its real palette, fonts and spacing.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Extract design tokens, colors, typography, spacing and components from any live website, and compute design drift against an approved baseline. Exports DESIGN.md, DTCG, Tailwind and shadcn.
      10,569 npm
      3,998
      MIT

    TDQS

    A4.1/5.0

    Scored across 12 tools

    Disambiguation3/5

    Descriptions are unusually detailed and include explicit 'NOT for X — use Y' guidance, which helps. But real overlap remains: brand_check vs brand_preflight both flag CSS anti-patterns, brand_runtime vs brand_context vs brand_report all surface brand data, and brand_start (mode='auto') vs brand_compile perform overlapping pipelines. Worse, the descriptions route agents to tools that don't exist in this set (brand_audit, brand_audit_content, brand_check_compliance, brand_brandcode_live), muddying the boundaries.

    Naming Consistency4/5

    Every tool uses a consistent brand_ snake_case prefix, which is crisp and predictable. Minor deviation: the brandcode pair uses a doubled prefix (brand_brandcode_auth/connect) and the suffix mixes verbs (compile, check, export) with nouns (context, runtime, report, status), but the scheme is still readable and coherent.

    Tool Count5/5

    12 tools sits squarely in the well-scoped 3-15 range. Each maps to a discrete stage of the brand lifecycle (start, compile, clarify, check/preflight, context/runtime, export, report, share, status), so the count feels earned rather than padded.

    Completeness3/5

    The core extract→compile→check→export→share loop is covered via brand_start and friends. However, multiple tools referenced as prerequisites/alternatives are absent — brand_audit_content (0-100 scoring), brand_check_compliance (publish gate), brand_preview, and brand_brandcode_live — creating documented dead ends, and there is no reset/delete path for a compiled brand.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues