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