get_head_to_head — StrikerAPI MCP Tool Read-only
get_head_to_head
(get head to head) is one of 19 tools on the
StrikerAPI
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_head_to_head from your client
- Claude Code StrikerAPI get_head_to_head run in your project directory
- Claude Desktop StrikerAPI get_head_to_head ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor StrikerAPI get_head_to_head ~/.cursor/mcp.json
- VS Code StrikerAPI get_head_to_head .vscode/mcp.json
- Zed StrikerAPI get_head_to_head ~/.config/zed/settings.json
- Windsurf StrikerAPI get_head_to_head ~/.codeium/windsurf/mcp_config.json
- Cline StrikerAPI get_head_to_head ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI StrikerAPI get_head_to_head ~/.gemini/settings.json
- Grok StrikerAPI get_head_to_head .mcp.json (in your project root)
- ChatGPT StrikerAPI get_head_to_head Settings → Connectors → Advanced → Developer mode
- Claude.ai StrikerAPI get_head_to_head Settings → Connectors → Add custom connector
- LangChain StrikerAPI get_head_to_head pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http strikerapi https://mcp.strikerapi.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 October 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.