residence_processing_latest — Japan Residence Processing Times MCP Tool
residence_processing_latest
(residence processing latest) is one of 5 tools on the
Japan Residence Processing Times
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call residence_processing_latest from your client
- Claude Code Japan Residence Processing Times residence_processing_latest run in your project directory
- Claude Desktop Japan Residence Processing Times residence_processing_latest ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Japan Residence Processing Times residence_processing_latest ~/.cursor/mcp.json
- VS Code Japan Residence Processing Times residence_processing_latest .vscode/mcp.json
- Zed Japan Residence Processing Times residence_processing_latest ~/.config/zed/settings.json
- Windsurf Japan Residence Processing Times residence_processing_latest ~/.codeium/windsurf/mcp_config.json
- Cline Japan Residence Processing Times residence_processing_latest ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Japan Residence Processing Times residence_processing_latest ~/.gemini/settings.json
- Grok Japan Residence Processing Times residence_processing_latest .mcp.json (in your project root)
- ChatGPT Japan Residence Processing Times residence_processing_latest Settings → Connectors → Advanced → Developer mode
- Claude.ai Japan Residence Processing Times residence_processing_latest Settings → Connectors → Add custom connector
- LangChain Japan Residence Processing Times residence_processing_latest pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http jp-residence-processing https://jp-residence-processing-production.mk-career-planning.workers.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 25 October 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.