get_matchup_context — DeepChamp for Agents MCP Tool Read-only
get_matchup_context
(get matchup context) is one of 8 tools on the
DeepChamp for Agents
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_matchup_context from your client
- Claude Code DeepChamp for Agents get_matchup_context run in your project directory
- Claude Desktop DeepChamp for Agents get_matchup_context ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DeepChamp for Agents get_matchup_context ~/.cursor/mcp.json
- VS Code DeepChamp for Agents get_matchup_context .vscode/mcp.json
- Zed DeepChamp for Agents get_matchup_context ~/.config/zed/settings.json
- Windsurf DeepChamp for Agents get_matchup_context ~/.codeium/windsurf/mcp_config.json
- Cline DeepChamp for Agents get_matchup_context ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DeepChamp for Agents get_matchup_context ~/.gemini/settings.json
- Grok DeepChamp for Agents get_matchup_context .mcp.json (in your project root)
- ChatGPT DeepChamp for Agents get_matchup_context Settings → Connectors → Advanced → Developer mode
- Claude.ai DeepChamp for Agents get_matchup_context Settings → Connectors → Add custom connector
- LangChain DeepChamp for Agents get_matchup_context pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http deepchamp-agents https://deepchampai.com/mcpOther tools on this server
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.