rival_head_to_head — signals MCP Prompt

rival_head_to_head is one of 6 prompts on the signals MCP server. Connect the server and it appears in your client, ready to invoke.

by client

How to invoke rival_head_to_head from your client

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

Other prompts on this server

• weekly_competitor_sweep
• price_drop_brief
• ai_readiness_gap
• dna_competitor_map
• new_domain_onboarding

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.