find_a_team — ClusterHack MCP Prompt

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

by client

How to invoke find_a_team from your client

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

Other prompts on this server

• set_up_event
• write_submission

ClusterHack 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.