filter_players — Vosters Rosters MCP Tool
filter_players
(filter players) 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 filter_players from your client
- Claude Code Vosters Rosters filter_players run in your project directory
- Claude Desktop Vosters Rosters filter_players ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Vosters Rosters filter_players ~/.cursor/mcp.json
- VS Code Vosters Rosters filter_players .vscode/mcp.json
- Zed Vosters Rosters filter_players ~/.config/zed/settings.json
- Windsurf Vosters Rosters filter_players ~/.codeium/windsurf/mcp_config.json
- Cline Vosters Rosters filter_players ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Vosters Rosters filter_players ~/.gemini/settings.json
- Grok Vosters Rosters filter_players .mcp.json (in your project root)
- ChatGPT Vosters Rosters filter_players Settings → Connectors → Advanced → Developer mode
- Claude.ai Vosters Rosters filter_players Settings → Connectors → Add custom connector
- LangChain Vosters Rosters filter_players 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_rivalries
- get_team_games
- compare_rosters
- get_conference_stats
- get_position_stats
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.