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