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