timer_start — McpStamp Time Tracker MCP Tool
timer_start
(timer start) is one of 20 tools on the
McpStamp Time Tracker
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call timer_start from your client
- Claude Code McpStamp Time Tracker timer_start run in your project directory
- Claude Desktop McpStamp Time Tracker timer_start ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor McpStamp Time Tracker timer_start ~/.cursor/mcp.json
- VS Code McpStamp Time Tracker timer_start .vscode/mcp.json
- Zed McpStamp Time Tracker timer_start ~/.config/zed/settings.json
- Windsurf McpStamp Time Tracker timer_start ~/.codeium/windsurf/mcp_config.json
- Cline McpStamp Time Tracker timer_start ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI McpStamp Time Tracker timer_start ~/.gemini/settings.json
- Grok McpStamp Time Tracker timer_start .mcp.json (in your project root)
- ChatGPT McpStamp Time Tracker timer_start Settings → Connectors → Advanced → Developer mode
- Claude.ai McpStamp Time Tracker timer_start Settings → Connectors → Add custom connector
- LangChain McpStamp Time Tracker timer_start pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http time-tracker-timesheet-billable-hours https://mcp.zovo.one/mcp/time-trackerOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.