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