get_head_to_head — BirdieAPI MCP Tool Read-only
get_head_to_head
(get head to head) is one of 14 tools on the
BirdieAPI
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 BirdieAPI get_head_to_head run in your project directory
- Claude Desktop BirdieAPI get_head_to_head ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor BirdieAPI get_head_to_head ~/.cursor/mcp.json
- VS Code BirdieAPI get_head_to_head .vscode/mcp.json
- Zed BirdieAPI get_head_to_head ~/.config/zed/settings.json
- Windsurf BirdieAPI get_head_to_head ~/.codeium/windsurf/mcp_config.json
- Cline BirdieAPI get_head_to_head ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI BirdieAPI get_head_to_head ~/.gemini/settings.json
- Grok BirdieAPI get_head_to_head .mcp.json (in your project root)
- ChatGPT BirdieAPI get_head_to_head Settings → Connectors → Advanced → Developer mode
- Claude.ai BirdieAPI get_head_to_head Settings → Connectors → Add custom connector
- LangChain BirdieAPI get_head_to_head pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http birdieapi https://mcp.birdieapi.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.