Add design tokens support for lookup/validation

[galkremer1]

Summary

The MCP currently indexes component documentation (design guidelines, accessibility, React examples) but does not include design tokens documentation from All PatternFly tokens.

Use Case

Developers writing custom SCSS/CSS need to:

• Validate that CSS variable names are correct (e.g. --pf-t--global--font--weight--heading vs --pf-t--global--font--weight--heading--default)
• Find the correct token when an invalid one is used
• Look up semantic token alternatives (e.g. --pf-t--global--text--color--subtle for secondary text instead of non-existent --pf-t--global--text--color--secondary)

Currently, searchPatternFlyDocs with queries like "design tokens", "pf-t--global", or "text--color--subtle" returns no results because the docs index is component-centric.

Proposed Enhancements

One or more of:

1. Include tokens in docs index – Add the tokens page(s) from patternfly.org so searchPatternFlyDocs can find token-related content
2. Add token validation/lookup tool – e.g. validateToken or getTokenInfo that accepts a token name and returns validity + suggested alternatives
3. Add tokens resource – Expose the full token list (e.g. from all-patternfly-tokens) as an MCP resource for programmatic use

Current Workaround

Manual validation against https://www.patternfly.org/tokens/all-patternfly-tokens or grepping node_modules/@patternfly for token definitions.

Related

• PatternFly tokens reference: https://www.patternfly.org/tokens/all-patternfly-tokens
• Architecture roadmap mentions "PatternFly API integration" and "Find PatternFly documentation tool" – tokens could be part of that expansion

---

Jira Issue: PF-3655

[cdcabrera]

Documentation work has been merged. Waiting for code release, before closing or marking things off...

• Token validation still taking a look. That's potentially a MCP tool and is being considered separate. We'll open another related issue if/when this one is closed.
  • Core server tools aren't necessarily going to be expanded beyond "pf library and codebase context"
  • It is possible to write you're own MCP tool plugins that work with the PF MCP server, this is intentional. Having an agent "[review this codebase]" and then asking it to "write me a PF MCP tool plugin" might get you started...
    • https://github.com/patternfly/patternfly-mcp/blob/main/docs/development.md#authoring-tools
    • Another possibility we're considering is adding tool plugins that users can activate or not and they're baked into the PF MCP dist
• The full "token list" still taking a look... we're debating if that should be a separate issue.