Salt MCP
Related Servers
Alternatives to Salt MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityDmaintenanceProvides AI agents with visibility into React applications by exposing tools to inspect component state, props, and performance metrics. It enables debugging and state analysis for both web and React Native applications through the Model Context Protocol.455 npm1MIT
- AlicenseAqualityBmaintenanceEnables 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.5183 npm20MIT
- AlicenseAqualityBmaintenanceIt lets AI coding agents look up design tokens, component specifications, and prohibition rules on demand, then validate generated HTML or JSX with the same lint logic used by CI and editor hooks so violations are caught and corrected immediately. It also exposes the design constitution and rule sets as resources for reference during generation.6272 npm202MIT
- AlicenseNot gradedqualityBmaintenanceEnables coding agents to read a React app's design-system context, scan for UI drift in buttons, cards, colors, and spacing, retrieve findings with file:line evidence and expected tokens, and verify fixes by rescanning affected routes.74 npm3MIT
- AlicenseAqualityCmaintenanceEnables AI agents to access and utilize GovBR Design System documentation, including component details, accessibility guidance, and search functionality via Model Context Protocol.311 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with access to AegisX UI components, CRUD generator commands, development patterns, and API contract discovery tools. It enables developers to browse component documentation, build generation commands, and test authenticated API endpoints through the Model Context Protocol.41 npmMIT
TDQS
Scored across 6 tools
Every tool has a clearly distinct purpose with no ambiguity: get-component-example retrieves example code, get-component-props provides API definitions, get-salt-docs returns documentation, hello is a test tool, list-components enumerates components, and search-components performs keyword searches. There is no overlap in functionality that could cause misselection.
The naming is mostly consistent with a verb_noun pattern (e.g., get-component-example, list-components, search-components), but the 'hello' tool deviates as a single-word, non-descriptive name. This minor inconsistency slightly reduces predictability, though the other tools follow a clear convention.
With 6 tools, the count is well-scoped for a Salt Design System server, covering key operations like listing, searching, retrieving examples, props, and documentation, plus a test tool. Each tool earns its place without being excessive or insufficient for the domain.
The tool surface is largely complete for accessing Salt Design System resources, covering listing, searching, and retrieving examples, props, and documentation. A minor gap is the lack of tools for interactive operations like modifying or testing components, but core informational workflows are well-covered without dead ends.