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