get_rivalries — Vosters Rosters MCP Tool Read-only
get_rivalries
(get rivalries) is one of 25 tools on the
Vosters Rosters
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_rivalries from your client
- Claude Code Vosters Rosters get_rivalries run in your project directory
- Claude Desktop Vosters Rosters get_rivalries ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Vosters Rosters get_rivalries ~/.cursor/mcp.json
- VS Code Vosters Rosters get_rivalries .vscode/mcp.json
- Zed Vosters Rosters get_rivalries ~/.config/zed/settings.json
- Windsurf Vosters Rosters get_rivalries ~/.codeium/windsurf/mcp_config.json
- Cline Vosters Rosters get_rivalries ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Vosters Rosters get_rivalries ~/.gemini/settings.json
- Grok Vosters Rosters get_rivalries .mcp.json (in your project root)
- ChatGPT Vosters Rosters get_rivalries Settings → Connectors → Advanced → Developer mode
- Claude.ai Vosters Rosters get_rivalries Settings → Connectors → Add custom connector
- LangChain Vosters Rosters get_rivalries pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http vosters-rosters https://app-production-3068.up.railway.app/mcpOther tools on this server
- search_football_teams
- resolve_football_team
- get_football_team
- get_football_team_roster
- search_football_players
- get_football_player
- list_football_conferences
- get_football_stats
- get_football_position_stats
- resolve_team
- search_teams
- search_players
- search_coaches
- list_conferences
- get_team
- get_team_roster
- get_player
- get_stadium
- get_team_stories
- get_team_games
- compare_rosters
- get_conference_stats
- get_position_stats
- filter_players
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 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.