target_check — time tracking MCP Tool

target_check (target check) 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 target_check from your client

Claude Code time tracking target_check run in your project directory
Claude Desktop time tracking target_check ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor time tracking target_check ~/.cursor/mcp.json
VS Code time tracking target_check .vscode/mcp.json
Zed time tracking target_check ~/.config/zed/settings.json
Windsurf time tracking target_check ~/.codeium/windsurf/mcp_config.json
Cline time tracking target_check ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI time tracking target_check ~/.gemini/settings.json
Grok time tracking target_check .mcp.json (in your project root)
ChatGPT time tracking target_check Settings → Connectors → Advanced → Developer mode
Claude.ai time tracking target_check Settings → Connectors → Add custom connector
LangChain time tracking target_check 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_week
summary_client
target_set
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