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