gnss_in_japan — kuongeo MCP Tool
gnss_in_japan
(gnss in japan) is one of 6 tools on the
kuongeo
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call gnss_in_japan from your client
- Claude Code kuongeo gnss_in_japan run in your project directory
- Claude Desktop kuongeo gnss_in_japan ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor kuongeo gnss_in_japan ~/.cursor/mcp.json
- VS Code kuongeo gnss_in_japan .vscode/mcp.json
- Zed kuongeo gnss_in_japan ~/.config/zed/settings.json
- Windsurf kuongeo gnss_in_japan ~/.codeium/windsurf/mcp_config.json
- Cline kuongeo gnss_in_japan ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI kuongeo gnss_in_japan ~/.gemini/settings.json
- Grok kuongeo gnss_in_japan .mcp.json (in your project root)
- ChatGPT kuongeo gnss_in_japan Settings → Connectors → Advanced → Developer mode
- Claude.ai kuongeo gnss_in_japan Settings → Connectors → Add custom connector
- LangChain kuongeo gnss_in_japan pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http kuongeo https://kuongeo.com/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.