Skip to main content
Glama
aquaminh

brandpilot-mcp

by aquaminh

Related Servers

Alternatives to brandpilot-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides resources, tools, and prompts for a Design System via MCP protocol, enabling component search, reading, and related component discovery.
      221 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      Enables any MCP client to search, read, and install free Aura components, agent skills, images/clips, and DESIGN.md systems straight from the public catalogue over stdio, with no account, OAuth, or API key needed. It also returns install plans, token starters, starter kits, and trending/category data so agents can assemble landing pages and UI sections in a few calls.
      15
      0
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP-capable coding agents to access SkeletIQ architecture releases, including reading designs and build orders, generating and critiquing architectures, and reporting build progress and drift.
      6
      431 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables access to agent instruction files and prompts for AI development workflows. Provides tools to retrieve and list development rules, security checks, and common prompts from an agents library through MCP protocol.
      3
      Apache 2.0
    • A
      license
      A
      quality
      A
      maintenance
      Enables agents to search a lightweight catalog, inspect permissions, lazily start trusted MCP servers, and call child tools without keeping all schemas in context. It also loads approved skills on demand and routes third-party additions through a human approval queue.
      1
      1
      MIT

    TDQS

    A3.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    The tools are mostly distinct, but get_design_prompt_pack and get_design_handoff both return design-related documentation, and get_system_adoption and get_system_tokens both retrieve system data. Descriptions clarify formats and content, so an agent should be able to tell them apart with careful reading.

    Naming Consistency5/5

    All tools follow a consistent verb_noun snake_case pattern: get, list, import, finish. The nouns are descriptive compounds, and no mixing of conventions or vague verbs appears.

    Tool Count5/5

    With 8 tools, the server is well-scoped for its design-system purpose. Each tool serves a clear role—retrieval for various system artifacts, plus import and completion actions—without redundancy or bloat.

    Completeness4/5

    The set covers the external design import workflow well, from listing and retrieving system data to importing artifacts and finishing the pipeline. Minor gaps exist (e.g., no explicit project listing or system creation), but they don't block the core intended flow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues