Inspo JP
Related Servers
Alternatives to Inspo JP
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceGives coding agents concrete, real product screens as inline references for unresolved layout, state, or interaction questions, plus licensed fonts and icons and the recorded design system behind a chosen web screen. Also bundles a token-free design workflow, diagnostics, and command playbooks that keep UI work grounded in the agent's own product.-
- FlicenseNot gradedqualityAmaintenanceGives coding agents real product-screen references, design materials, and recorded design references so UI work is grounded in actual surfaces rather than generic templates. It also serves the bundled design workflow, command playbooks, and connection diagnostics as MCP resources, prompts, and tools.-
- FlicenseNot gradedqualityAmaintenanceEnables coding agents to find real product screen references, fonts, icons, and recorded design-system details for UI work. It also exposes bundled design workflow resources, command prompts, and connection diagnostics.-
- AlicenseAqualityCmaintenanceProvides expert design and marketing guidance for AI coding agents through curated knowledge documents and tools. Covers UI/UX, copywriting, SEO, GEO, and conversion optimization.3675 npm6MIT
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to pull real product screens as inline image references, find licensed fonts and icons, and retrieve recorded design-system details for web screens so UI work is grounded in actual interfaces rather than generic templates.MIT
- AlicenseNot gradedqualityAmaintenanceEnables coding agents to look up real product screens, licensed fonts and icons, and recorded design-reference details (colors, typography, components) when building UI. Also ships bundled skill resources, help, and connection-status tools for diagnosing the setup without a token.MIT
TDQS
Scored across 10 tools
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.
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.
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.
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.