find_tool_for_task — HyperStore MCP Prompt

find_tool_for_task is one of 3 prompts on the HyperStore MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke find_tool_for_task from your client

• Claude Code HyperStore Prompt/find_tool_for_task run in your project directory
• Claude Desktop HyperStore Prompt/find_tool_for_task ~/Library/Application Support/Claude/claude_desktop_config.json
• Cursor HyperStore Prompt/find_tool_for_task ~/.cursor/mcp.json
• VS Code HyperStore Prompt/find_tool_for_task .vscode/mcp.json
• Zed HyperStore Prompt/find_tool_for_task ~/.config/zed/settings.json
• Windsurf HyperStore Prompt/find_tool_for_task ~/.codeium/windsurf/mcp_config.json
• Cline HyperStore Prompt/find_tool_for_task ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
• Gemini CLI HyperStore Prompt/find_tool_for_task ~/.gemini/settings.json
• Grok HyperStore Prompt/find_tool_for_task .mcp.json (in your project root)
• ChatGPT HyperStore Prompt/find_tool_for_task Settings → Connectors → Advanced → Developer mode
• Claude.ai HyperStore Prompt/find_tool_for_task Settings → Connectors → Add custom connector
• LangChain HyperStore Prompt/find_tool_for_task pip install langchain-mcp-adapters

Other prompts on this server

• compare_apps
• discover_category

HyperStore also offers 1 resource — data you attach as context, where a prompt is something you run.

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.