Skip to main content
Glama
patternfly

PatternFly MCP Server

Official
by patternfly

Related Servers

Alternatives to PatternFly MCP Server

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.
      284 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI assistants with comprehensive access to Taiga UI components, enabling retrieval of component documentation, code examples, and migration guides via four MCP tools.
      5,195 npm
      15
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to read ground truth about a React design system — components, props, cva variants, tokens and docs — over MCP so they write UI that matches it. It also exposes a check_ui linter agents run on their own output, returning rule ids, locations and concrete fixes before review.
      662 npm
      1
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Provides AI assistants with comprehensive access to Grafana's React component library, including TypeScript source code, MDX documentation, Storybook examples, test files, and design system tokens for building Grafana-compatible interfaces.
      1
      63 npm
      9
      MIT

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation4/5

    The pair follows a clean search-then-fetch split: searchPatternFlyDocs returns names/URIs/URLs, usePatternFlyDocs consumes them. The only slight fuzziness is that 'usePatternFlyDocs' alone doesn't signal 'fetch content' without reading the description, but the two tools are not confusable in practice.

    Naming Consistency5/5

    Both names use camelCase with a verb+PatternFly+Docs structure (searchPatternFlyDocs, usePatternFlyDocs), giving a predictable, parallel pattern. No mixed conventions or vague one-word verbs.

    Tool Count4/5

    Two tools is deliberately minimal but justified: this is the canonical search/fetch pattern for a documentation server, and each tool has a distinct, non-redundant role. It sits at the thin end of the range but is well scoped.

    Completeness4/5

    Discovery (search, including wildcard and version-specific queries) plus retrieval of markdown docs and JSON schemas covers the core documentation use case with no dead ends. Minor gaps exist, such as no explicit enumeration of available versions or collections, but '*' search largely compensates.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week