PatternFly MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOC_MCP_FETCH_TIMEOUT_MS | No | Milliseconds to wait before aborting an HTTP fetch | 15000 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| usePatternFlyDocsA | Get markdown documentation and component JSON schemas for PatternFly resources and components. |
| searchPatternFlyDocsA | Search collections and get component names with documentation and guidance URLs. Supports case-insensitive partial, version-specific (e.g., "card v5"), and all ("*") matches. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| patternfly-context | Information about the PatternFly design system, documentation collections, and how to use this MCP server, including environment and troubleshooting information. |
| Components Index (Latest) | Component documentation entry point for the latest PatternFly version. This is the recommended starting point. Filter by PatternFly version and category. patternfly://components/index{?version,category} |
| Component Index (v6) | Component documentation entry point for PatternFly version v6. Filter by PatternFly version and category. patternfly://components/index{?version,category} |
| Docs Index | Documentation entry point for collections. This is the recommended starting point. Filter by resource version, category, section, and collection. patternfly://docs/index{?version,category,section,collection} |
| Docs Index for AI Handbook | Documentation entry point for collection ai-handbook. Filter by resource version, category, section, and collection. patternfly://docs/index{?version,category,section,collection} |
| Docs Index for Component Schemas | Documentation entry point for collection patternfly-component-schemas. Filter by resource version, category, section, and collection. patternfly://docs/index{?version,category,section,collection} |
| Docs Index for PatternFly API | Documentation entry point for collection patternfly-api. Filter by resource version, category, section, and collection. patternfly://docs/index{?version,category,section,collection} |
| Docs Index for PatternFly Docs | Documentation entry point for collection patternfly-docs. Filter by resource version, category, section, and collection. patternfly://docs/index{?version,category,section,collection} |
| JSON Component Schemas Index (Latest) | JSON component schemas entry point for the latest PatternFly version. This is the recommended starting point. Filter by PatternFly version and category. patternfly://schemas/index{?version,category} |
| JSON Component Schemas Index (v6) | JSON component schemas for PatternFly version v6. Filter by PatternFly version and category. patternfly://schemas/index{?version,category} |
TDQS
Scored across 2 tools
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.
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.
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.
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.