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