A
licenseA
qualityA
maintenanceProvides expert design and marketing guidance for AI coding agents through curated knowledge documents and tools. Covers UI/UX, copywriting, SEO, GEO, and conversion optimization.
36
120 npm
6
MIT
Inspo JP
by manab-b
Related Servers
Alternatives to Inspo JP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to plan, reference, and gate UI work through preflight briefs, design-intent dispatch, and a static review checklist.45MIT
- FlicenseAqualityDmaintenanceProvides comprehensive design principles and best practices to help LLMs generate modern, accessible web pages through guidance on layouts, colors, and typography. It enables users to review design approaches and access expert recommendations for responsive design, component structure, and current industry trends.1237 npm3-
- FlicenseBqualityDmaintenanceProvides design system guidelines and component documentation to Cursor Desktop, enabling accurate advice on UI components, patterns, and best practices.11-
uxloomofficial
AlicenseAqualityAmaintenanceEnables agents to validate UI designs for missing states, accessibility issues, and journey completeness using state machine modeling.172MIT- AlicenseAqualityAmaintenanceServes the complete Sekura Design System—tokens, components, layouts, UX patterns, accessibility contract, and paste-ready code—to MCP-capable tools, enabling agents to build accessible, dark-mode-first interfaces with verified values.21MIT
TDQS
A3.6/5.0
Scored across 10 tools
Disambiguation4/5
Most tools have clearly distinct purposes (e.g., copy patterns vs. legal blocks vs. form specs). Some overlap exists between search_jp_sites and list_jp_catalog (both retrieve catalog info), and get_jp_rules vs. get_jp_copy_patterns could be confused if an agent needs 'rules' vs. 'copy examples', but descriptions clarify the difference.
Naming Consistency4/5
Almost all tools follow a consistent verb_noun pattern: get_*, list_*, search_*, critique_*, recommend_. The only minor deviation is 'get_reference_jsx' which could be seen as 'get_jsx_reference' but is still readable and consistent with the get_ prefix. Overall a clear convention.
Tool Count4/5
Ten tools is within the ideal range (3-15) and the server has a broad but focused purpose (Japanese UI best practices). Each tool covers a distinct aspect (copy, legal, forms, rules, catalog, etc.). It could be slightly leaner by merging some, but the count is well-scoped for its stated purpose.
Completeness4/5
The surface covers the major aspects of Japanese UI design: copy, legal, forms, rules, catalog search, and even critique. A minor gap is the lack of tools for creating or updating content (e.g., no 'add_catalog_entry' or 'update_rule'), but since this is a knowledge/reference server, not a CRUD system, the absence is acceptable. The 'recommend_jp' tool aggregates everything, so the coverage feels complete.
Maintenance
ActivityMaintained
ResponsivenessNo issues