japan-ux-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_jp_formA | 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. |
| validate_jp_formA | 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. |
| generate_jp_placeholderA | 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日). |
| suggest_keigo_levelB | 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. |
| score_japan_readinessA | 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. |
| transform_for_japanA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| japan_form | Generate a culturally correct Japanese form. Specify the type and context. |
| japan_audit | Audit HTML/JSX markup for Japanese UX issues. Paste your form markup. |
| japan_transform | Transform Western markup into Japan-ready markup with before/after scoring. |
| japan_testdata | Generate realistic Japanese test data for prototypes. |
| japan_keigo | Get the right Japanese politeness level for UI text. |
| japan_score | Score a page or component for Japan-readiness (0-100). |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| keigo-guide | Complete Japanese keigo (politeness) reference for UI copy — 4 levels across 8 business contexts with 30+ pattern examples |
| form-checklist | Japanese form UX checklist — every convention to check before shipping a form for Japanese users |
| phone-formats | Japanese phone number formats — mobile, landline, toll-free, IP phone patterns with field splitting rules |
| era-calendar | Japanese era calendar — Reiwa, Heisei, Showa, Taisho, Meiji with date ranges and conversion rules |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mrslbt/japan-ux-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server