summary_week — time tracking MCP Tool

summary_week (summary week) is one of 20 tools on the time tracking MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call summary_week from your client

Claude Code time tracking summary_week run in your project directory
Claude Desktop time tracking summary_week ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor time tracking summary_week ~/.cursor/mcp.json
VS Code time tracking summary_week .vscode/mcp.json
Zed time tracking summary_week ~/.config/zed/settings.json
Windsurf time tracking summary_week ~/.codeium/windsurf/mcp_config.json
Cline time tracking summary_week ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI time tracking summary_week ~/.gemini/settings.json
Grok time tracking summary_week .mcp.json (in your project root)
ChatGPT time tracking summary_week Settings → Connectors → Advanced → Developer mode
Claude.ai time tracking summary_week Settings → Connectors → Add custom connector
LangChain time tracking summary_week pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http time-tracking https://mcp.zovo.one/mcp/time-tracking

Other tools on this server

license_status
license_activate
timer_start
timer_stop
timer_status
entry_add
entry_log
summary_day
summary_client
target_set
target_check
entry_list
entry_delete
entry_edit
project_set_rate
report
export_csv
entry_mark_billed
invoice_summary

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.

time tracking MCP server