find_api_endpoints — NetActuate MCP Tool Read-only
find_api_endpoints
(find api endpoints) 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_api_endpoints from your client
- Claude Code NetActuate find_api_endpoints run in your project directory
- Claude Desktop NetActuate find_api_endpoints ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor NetActuate find_api_endpoints ~/.cursor/mcp.json
- VS Code NetActuate find_api_endpoints .vscode/mcp.json
- Zed NetActuate find_api_endpoints ~/.config/zed/settings.json
- Windsurf NetActuate find_api_endpoints ~/.codeium/windsurf/mcp_config.json
- Cline NetActuate find_api_endpoints ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI NetActuate find_api_endpoints ~/.gemini/settings.json
- Grok NetActuate find_api_endpoints .mcp.json (in your project root)
- ChatGPT NetActuate find_api_endpoints Settings → Connectors → Advanced → Developer mode
- Claude.ai NetActuate find_api_endpoints Settings → Connectors → Add custom connector
- LangChain NetActuate find_api_endpoints 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.