Koskamo

Shirabe MCP MCP server

Shirabe is an official MCP server operated by Techwell that provides deterministic Japanese data tools for AI agents. It exposes four REST APIs via MCP: Calendar (rokuyo, lunar dates), Address Normalization (JIS codes), Japanese Text Processing (morphological analysis, name splitting), and Corporate Number Lookup (tax office data). It ensures consistent JSON schemas, low latency, and attribution from public sources.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-05Operated by 株式会社テックウェル
MCP endpoint (Streamable HTTP)
https://shirabe.dev/mcp
Vendor documentation

What you can do with it

  • Retrieve deterministic Japanese calendar data like rokuyo and lunar dates
  • Normalize Japanese addresses to official JIS codes and district IDs
  • Perform morphological analysis and name splitting on Japanese text
  • Verify corporate existence and normalize company names using tax data
Tools advertised by the last live check:
  • lookup_calendar
  • normalize_japanese_address
  • split_japanese_name
  • corporation_lookup
  • corporation_search

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http shirabe-mcp https://shirabe.dev/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add shirabe-mcp --url https://shirabe.dev/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable shirabe-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "shirabe-mcp": {
      "url": "https://shirabe.dev/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "shirabe-mcp": {
      "type": "streamableHttp",
      "url": "https://shirabe.dev/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start shirabe-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "shirabe-mcp": {
      "type": "http",
      "url": "https://shirabe.dev/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http shirabe-mcp https://shirabe.dev/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "shirabe-mcp": {
      "url": "https://shirabe.dev/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "shirabe-mcp": {
      "serverUrl": "https://shirabe.dev/mcp"
    }
  }
}

Do you run Shirabe MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing