Astryx Documentation MCP Server
Related Servers
Alternatives to Astryx Documentation MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables intent-based semantic search over external design system documentation, allowing MCP-compatible AI assistants to retrieve relevant design tokens, component architectures, and code patterns via a single tool.-
- AlicenseNot gradedqualityDmaintenanceProvides AI agents with component documentation, usage examples, and design tokens from the WordPress Design System, enabling them to follow the latest design system guidance for creating user interfaces.267 npmGPL 2.0
- AlicenseNot gradedqualityCmaintenanceEnables coding agents to retrieve accurate design system information, component APIs, design tokens, and coding standards, so they build with real specs rather than guessing.2MIT
- AlicenseNot gradedqualityBmaintenanceProvides a real API for coding agents to look up design system components, props, and tokens, preventing guessed answers.9MIT

@vaneui/mcpofficial
AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to read VaneUI's component reference, guides, and per-component prop tables on demand, and to search the full docs corpus for prop names, defaults, and Tailwind class mappings.1,702 npm1MIT- AlicenseNot gradedqualityCmaintenanceEnables AI models to interact with Astro projects by providing runtime information, documentation search, route listing, and integration details.61MIT
TDQS
Scored across 4 tools
Each tool targets a distinct area of the documentation: broad search, component details, theme syntax, and CLI commands. There is no meaningful overlap between the four tools.
Tool names follow a clear verb-first pattern, using `search_` for the lookup tool and `get_` for the three resource-specific tools. Minor inconsistency comes from only some tools including the 'astryx' prefix, but the structure is still predictable.
Four tools is a well-scoped set for a documentation MCP server, covering search plus the three primary documented areas: components, themes, and CLI. Each tool serves a distinct purpose without unnecessary redundancy.
The tool surface covers the main ways someone would interact with Astryx documentation: searching, component reference, theme customization, and CLI usage. A potential gap is the absence of a direct `get_guide` tool for retrieving a full guide article, but the search tool mitigates that.