Japan Utils Mcp

Created By
vivek081166a month ago
Japan-specific utilities for AI agents — era ↔ Western year conversion, kanji-to-romaji, postal code lookup, holidays, kana conversion, name splitting. 9 tools, MIT, install via uvx.
Overview

MCP server exposing Japan-specific utilities to AI agents. Hand any Claude/Cursor/Cline agent the small bag of JP functions every Japan-related task needs but generic LLMs hallucinate on.

Why this exists

Generic LLMs are unreliable on JP-specific data:

  • "What year is 令和8年?" — often wrong
  • "Convert 山田太郎 to romaji" — gets the surname wrong half the time
  • "What's the address for postal code 150-0001?" — fabricates plausible-looking nonsense
  • "Is May 3rd a Japanese holiday?" — guesses

This MCP gives them deterministic answers backed by well-maintained Python libraries (jpholiday, posuto, pykakasi, jaconv, namedivider-python).

9 tools

  • era_to_western令和8年 / R8 / Reiwa 8 → 2026
  • western_to_era — 2026 → 令和8年 (with kanji + English + short forms)
  • kanji_to_romaji — Hepburn romaji + hiragana for any Japanese text
  • lookup_postal_code — 7-digit 郵便番号 → prefecture / city / area + kana
  • is_holiday — date → is national holiday + JP name + weekday
  • list_holidays — year → all 国民の祝日
  • convert_kana — hiragana ↔ katakana ↔ half-width katakana
  • normalize_width — full-width (全角) ↔ half-width (半角), per-category control
  • split_japanese_name — full name → surname + given (statistical model with confidence)

Install

uvx japan-utils-mcp

PyPI: https://pypi.org/project/japan-utils-mcp/

Configuration (Claude Desktop)

{
  "mcpServers": {
    "japan-utils": {
      "command": "uvx",
      "args": ["japan-utils-mcp"]
    }
  }
}

MIT licensed. Python 3.13+. Runs locally over stdio.

Server Config

{
  "mcpServers": {
    "japan-utils": {
      "command": "uvx",
      "args": [
        "japan-utils-mcp"
      ]
    }
  }
}
Project Info
Created At
a month ago
Updated At
a month ago
Author Name
vivek081166
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago