Japan Ux MCP server

by mrslbt·io.github.mrslbt/japan-ux·v2.1.1

No reviews yet

Japanese UI + UX correctness for AI coding agents — typography, forms, keigo, JLReq checks.

A88/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A88/100

full report

Adoption

New

0 stars55 downloads/wk

Reviews

Write one

Nobody has reviewed Japan Ux yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Japan Ux tools (11)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

audit_japan_ux
Comprehensive Japanese UX audit covering 7 categories: layout (density, breadcrumbs, CTA placement), typography (fonts, line-height, kinsoku shori), visual (color meanings, red-name taboo, dark theme), navigation (phone number, footer links, hamburger rules), trust (会社概要, case studies, proof numbers, legal links), content (Japanese text, FAQ, pricing tables), and mobile (viewport, tel: links, touc
check_jp_typography
Audit CSS and markup for Japanese typography issues. Checks: font stacks (Noto Sans JP, Hiragino, Yu Gothic), line-height (1.7-2.0 for Japanese body text), font sizes (14px body minimum, 12px captions floor), kinsoku shori (line-break: strict), text-on-photo overlays, font-feature-settings 'palt' on headings, font-synthesis, and more. Returns score, issues, and a recommended font stack for your co
design_direction_for_japan
Generate a Japan-specific visual direction for a website or interface. Takes a loose brand type, audience, and industry, then returns a practical design brief covering visual direction, information density, color palette, typography, imagery style, CTA style, trust layout, and section priorities.
generate_jp_form
Generate culturally correct Japanese form markup with proper field order (姓→名), furigana, 3-field phone, 〒 postal address, 年月日 dates, and context-appropriate keigo. Use this when building any form for a Japanese audience.
generate_jp_placeholder
Generate realistic Japanese test data for prototypes and development. Returns names (kanji + katakana furigana + romaji), addresses (real postal codes and prefectures), phone numbers (correct 3-field format), company names, and dates (both Gregorian and Japanese era format like 平成4年3月15日).
get_seasonal_context
Get the current Japanese seasonal context for design decisions. Returns: current season with traditional colors, active events (正月, 花見, お盆, etc.), upcoming events, the current microseason (二十四節気), recommended design colors, and warnings (e.g., do not launch during Golden Week). Covers all 24 Japanese microseasons and 24+ major events.
review_jp_ui
Review CSS/markup against the Japanese UI standard (typography, colour, font performance) and return a pass/needs_work/fail verdict with violations, JLReq/JIS citations, and fixes. The front-end correctness enforcer — run on any UI (including Western-built) before shipping to Japan; call transform_for_japan to auto-apply form/copy fixes.
score_japan_readiness
Score any page or component for Japan-readiness on a 0-100 scale. Analyzes 5 categories: forms (name order, furigana, phone, postal), copy (keigo, Japanese text, placeholders), trust (特定商取引法, phone number, company info), typography (font, size, line-height), and cultural (seasonal awareness, imagery). Returns breakdown with issues and quick wins per category.
suggest_keigo_level
Suggest appropriately polite Japanese UI text based on context. Maps business context to keigo level (casual → very_formal) and returns the right Japanese translation for buttons, error messages, empty states, confirmations, and more. Includes alternatives for different formality levels.
transform_for_japan
Transform Western markup into Japan-ready markup. Automatically fixes: name field order (firstName/lastName → 姓/名), adds furigana, splits phone into 3 fields, restructures address to 〒 postal format, translates buttons with appropriate keigo, replaces Western placeholder data with Japanese examples. Shows before/after scores and explains every change.
validate_jp_form
Audit an existing form against Japanese UX conventions. Checks for: name field order (姓/名), furigana, 3-field phone, postal code auto-fill, keigo-appropriate button text, full-width character handling. Returns score (0-100), issues with fixes, and what passed.

Public scan report

scanner v0.1.9 · 2026-09-23 · same rubric, same numbers if you re-run it

no findings

Code scan57 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 38 days ago12/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

What the publisher says

From the Japan Ux repository's README, as published. We do not edit it. Read it on GitHub

japan-ux-mcp

Japan Design — UI + UX correctness for AI coding agents. A front-end enforcer: point it at real CSS/markup and it scores your UI against the Japanese standard — typography (kinsoku, line-height, fonts), colour symbolism, font performance — with W3C JLReq / JIS X 4051 citations and fixes. Plus the full UX layer: forms (姓名/furigana), keigo, trust signals, legal, and seasonal design.

Lead tool: reviewjpui — the front-end correctness enforcer (run it on any UI, including Western-built, before shipping to Japan).

Eleven tools, ten prompts, nine resources. Runs locally, no API keys. Findings are labelled spec (JLReq/JIS) vs convention (documented JP web practice) so authority is never overstated.

Install

claude mcp add japan-ux -- npx -y japan-ux-mcp

JSON config

The server config is the same across clients; only the file path differs.

Claude Code — ~/.claude/.mcp.json

{
  "mcpServers": {
    "japan-ux": { "command": "npx", "args": ["-y", "japan-ux-mcp"] }
  }
}

Cursor — ~/.cursor/mcp.json

{
  "mcpServers": {
    "japan-ux": { "command": "npx", "args": ["-y", "japan-ux-mcp"] }
  }
}

Windsurf — ~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "japan-ux": { "command": "npx", "args": ["-y", "japan-ux-mcp"] }
  }
}

VS Code (GitHub Copilot) — .vscode/mcp.json

{
  "servers": {
    "japan-ux": { "type": "stdio", "command": "npx", "args": ["-y", "japan-ux-mcp"] }
  }
}

Cline (VS Code extension)

Open Cline's MCP settings panel and add:

{
  "mcpServers": {
    "japan-ux": { "command": "npx", "args": ["-y", "japan-ux-mcp"] }
  }
}

Claude Desktop — claudedesktopconfig.json

{
  "mcpServers": {
    "japan-ux": { "command": "npx", "args": ["-y", "japan-ux-mcp"] }
  }
}

Config path:

macOS: ~/Library/Application Support/Claude/claudedesktopconfig.json
Windows: %APPDATA%\Claude\claudedesktopconfig.json

Zed — ~/.config/zed/settings.json

{
  "context_servers": {
    "japan-ux": { "command": { "path": "npx", "args": ["-y", "japan-ux-mcp"] } }
  }
}

From source

git clone https://github.com/mrslbt/japan-ux-mcp.git
cd japan-ux-mcp
npm install && npm run build

Point the client config at the built entry:

{ "command": "node", "args": ["/absolute/path/to/japan-ux-mcp/dist/index.js"] }

Tools

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

Runs npx -y japan-ux-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add japan-ux -- npx -y japan-ux-mcp

Add to Cursor

Japan Ux: common questions

Is Japan Ux MCP server safe?: Yes, by our scan: it is graded A (88/100). Read the Japan Ux safety report
How do I install Japan Ux?: It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
Does Japan Ux need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Japan Ux maintained?: The last commit was 39 days ago (2026-08-16). The latest release is v2.1.1.