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