Agent Genesis Tools
Related Servers
Alternatives to Agent Genesis Tools
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceThis MCP server generates accessible, harmonized presentation design tokens — primary, background, surface, text, and border colors — from a single brand color while computing exact WCAG AA/AAA contrast ratios and typography pairings. It lets agents validate legibility and produce a complete semantic styling token set without any third-party math libraries.7MIT
- AlicenseNot gradedqualityCmaintenanceVisual frontend accessibility inspector MCP server. WCAG contrast checking, touch target validation, heading hierarchy audits, responsive screenshots, and S+ grading across mobile and desktop viewports.MIT
- AlicenseNot gradedqualityDmaintenanceA comprehensive Python MCP server with built-in knowledge base (SQLite + FTS5), web management interface, and flexible tool grouping system. Supports multiple transport protocols (stdio, SSE, HTTP Stream) with zero external dependencies.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that extracts accessibility tree, design tokens, screenshots, Claude DSL, and Figma JSON from any URL using a persistent Chromium browser with zero LLM cost.MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that exposes a design system and UX rulebook as tools, enabling AI to generate UI consistent with your design tokens, components, layout rules, accessibility guidelines, and templates. It also provides a review tool to score UI proposals against the design system.MIT
- AlicenseAqualityBmaintenanceEnables building and running zero-dependency MCP servers with automatic JSON Schema generation, exposing Python tools to Claude Desktop, Cursor, and autonomous agent fleets.2Apache 2.0
TDQS
Scored across 6 tools
The six tools form three clearly separated pairs: design/contrast, skill discovery/equipping, and codebase-graph status/query. Each description explicitly states when to use the sibling tool instead, eliminating overlap. An agent can reliably distinguish all tools by resource and action.
All tool names use snake_case with a verb-first pattern: check_contrast, equip_skill, get_brand_design, get_graphify_status, list_vault_skills, query_codebase_graph. The verbs are varied but predictable and appropriate to each action. No mixed casing or inconsistent naming styles appear.
Six tools is well within the appropriate range and each tool has a distinct, non-redundant role. The set is compact but covers three focused utility areas with two tools each. No tool feels filler or missing from the count perspective.
Core workflows are covered: brand retrieval with contrast validation, skill discovery with installation, and graph health with querying. Minor lifecycle gaps remain, such as no explicit skill unequip/removal tool and no direct graph-build tool, though status provides generation instructions and query has a fallback. These are workable gaps rather than dead ends.