list_contests — v12 dfs MCP Tool Read-only
list_contests
(list contests) is one of 34 tools on the
v12 dfs
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_contests from your client
- Claude Code v12 dfs list_contests run in your project directory
- Claude Desktop v12 dfs list_contests ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor v12 dfs list_contests ~/.cursor/mcp.json
- VS Code v12 dfs list_contests .vscode/mcp.json
- Zed v12 dfs list_contests ~/.config/zed/settings.json
- Windsurf v12 dfs list_contests ~/.codeium/windsurf/mcp_config.json
- Cline v12 dfs list_contests ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI v12 dfs list_contests ~/.gemini/settings.json
- Grok v12 dfs list_contests .mcp.json (in your project root)
- ChatGPT v12 dfs list_contests Settings → Connectors → Advanced → Developer mode
- Claude.ai v12 dfs list_contests Settings → Connectors → Add custom connector
- LangChain v12 dfs list_contests pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http v12-dfs https://v12dfs-production.up.railway.app/mcpOther tools on this server
- agent_guide
- health_check
- health_v12
- list_slates
- get_slate_players
- slate_health
- slate_refresh
- slate_diff
- list_presets
- generate_lineups
- run_mlb_postmortem
- list_live_contests
- contest_semaforo
- scout_field
- contest_advice
- fill_template
- admin_issue_key
- betting_agent_guide
- betting_player_form
- betting_analyze_prop
- betting_scan_edges
- betting_best_bets
- betting_build_parlay
- betting_log_bet
- betting_my_bets
- betting_settle_bet
- betting_cross_book
- betting_game_lines
- betting_market
- betting_sharp
- betting_game_model
- betting_matchup
- betting_market_movers
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.