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