team_report — LiveScore MCP MCP Prompt
team_report
is one of 4 prompts on the
LiveScore MCP
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke team_report from your client
- Claude Code LiveScore MCP Prompt/team_report run in your project directory
- Claude Desktop LiveScore MCP Prompt/team_report ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor LiveScore MCP Prompt/team_report ~/.cursor/mcp.json
- VS Code LiveScore MCP Prompt/team_report .vscode/mcp.json
- Zed LiveScore MCP Prompt/team_report ~/.config/zed/settings.json
- Windsurf LiveScore MCP Prompt/team_report ~/.codeium/windsurf/mcp_config.json
- Cline LiveScore MCP Prompt/team_report ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI LiveScore MCP Prompt/team_report ~/.gemini/settings.json
- Grok LiveScore MCP Prompt/team_report .mcp.json (in your project root)
- ChatGPT LiveScore MCP Prompt/team_report Settings → Connectors → Advanced → Developer mode
- Claude.ai LiveScore MCP Prompt/team_report Settings → Connectors → Add custom connector
- LangChain LiveScore MCP Prompt/team_report pip install langchain-mcp-adapters
Other prompts on this server
LiveScore MCP also offers 1 resource — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 14 November 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.