search_entry_cases — Japan RuleWatch MCP Tool Read-only
search_entry_cases
(search entry cases) is one of 7 tools on the
Japan RuleWatch
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call search_entry_cases from your client
- Claude Code Japan RuleWatch search_entry_cases run in your project directory
- Claude Desktop Japan RuleWatch search_entry_cases ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Japan RuleWatch search_entry_cases ~/.cursor/mcp.json
- VS Code Japan RuleWatch search_entry_cases .vscode/mcp.json
- Zed Japan RuleWatch search_entry_cases ~/.config/zed/settings.json
- Windsurf Japan RuleWatch search_entry_cases ~/.codeium/windsurf/mcp_config.json
- Cline Japan RuleWatch search_entry_cases ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Japan RuleWatch search_entry_cases ~/.gemini/settings.json
- Grok Japan RuleWatch search_entry_cases .mcp.json (in your project root)
- ChatGPT Japan RuleWatch search_entry_cases Settings → Connectors → Advanced → Developer mode
- Claude.ai Japan RuleWatch search_entry_cases Settings → Connectors → Add custom connector
- LangChain Japan RuleWatch search_entry_cases pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http japan-rulewatch-mcp https://japan-rulewatch-mcp-mainnet.kadopi.workers.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.