read_docs — The Tennis Desk MCP Tool Read-only
read_docs
(read docs) is one of 29 tools on the
The Tennis Desk
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call read_docs from your client
- Claude Code The Tennis Desk read_docs run in your project directory
- Claude Desktop The Tennis Desk read_docs ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor The Tennis Desk read_docs ~/.cursor/mcp.json
- VS Code The Tennis Desk read_docs .vscode/mcp.json
- Zed The Tennis Desk read_docs ~/.config/zed/settings.json
- Windsurf The Tennis Desk read_docs ~/.codeium/windsurf/mcp_config.json
- Cline The Tennis Desk read_docs ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI The Tennis Desk read_docs ~/.gemini/settings.json
- Grok The Tennis Desk read_docs .mcp.json (in your project root)
- ChatGPT The Tennis Desk read_docs Settings → Connectors → Advanced → Developer mode
- Claude.ai The Tennis Desk read_docs Settings → Connectors → Add custom connector
- LangChain The Tennis Desk read_docs pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http thetennisdesk https://thetennisdesk.com/api/mcpOther tools on this server
- plan_lineup
- query_team_record
- query_matchup
- query_roster
- query_player_history
- query_match_log
- compute_aggregate
- compute_roster_strength
- compute_match_line_ratings
- query_player_rating
- predict_matchup
- query_team_forecast
- query_club_teams
- query_club
- query_my_teams
- query_cohort_standing
- query_league_standings
- plan_lineup_from_availability
- prepare_score_entry
- match_date_check
- availability_loop
- read_research
- query_coverage
- project_standings
- query_playoff_history
- query_forecast_results
- scout_team
- get_desk_pass
This list was read from the server itself, by connecting to it and calling tools/list on 5 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.