jp_facility_signal — Japan Places — Japan Data Foundry MCP Tool
jp_facility_signal
(jp facility signal) is one of 16 tools on the
Japan Places — Japan Data Foundry
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call jp_facility_signal from your client
- Claude Code Japan Places — Japan Data Foundry jp_facility_signal run in your project directory
- Claude Desktop Japan Places — Japan Data Foundry jp_facility_signal ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Japan Places — Japan Data Foundry jp_facility_signal ~/.cursor/mcp.json
- VS Code Japan Places — Japan Data Foundry jp_facility_signal .vscode/mcp.json
- Zed Japan Places — Japan Data Foundry jp_facility_signal ~/.config/zed/settings.json
- Windsurf Japan Places — Japan Data Foundry jp_facility_signal ~/.codeium/windsurf/mcp_config.json
- Cline Japan Places — Japan Data Foundry jp_facility_signal ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Japan Places — Japan Data Foundry jp_facility_signal ~/.gemini/settings.json
- Grok Japan Places — Japan Data Foundry jp_facility_signal .mcp.json (in your project root)
- ChatGPT Japan Places — Japan Data Foundry jp_facility_signal Settings → Connectors → Advanced → Developer mode
- Claude.ai Japan Places — Japan Data Foundry jp_facility_signal Settings → Connectors → Add custom connector
- LangChain Japan Places — Japan Data Foundry jp_facility_signal pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http japan-foundry https://japan-places.local-connect-design.trade/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 9 November 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.