TimeCard MCP

Get list of available projects. Returns project id and name.

Use the project id with timecard_get_activities to get activity options, and with timecard_save to set entries.

Get list of activities for a specific project. Returns activity id, name, and value.

The 'value' field (format: "bottom$uid$pid$progress") is the activity_value needed by timecard_save's entries parameter.

Get timesheet data for a specific week. Read-only, no side effects.

Returns for each entry:

• daily_hours: Hours worked each day (monday-saturday)

• daily_status: Approval status each day (draft/submitted/approved/rejected)

• daily_notes: Notes for each day

Status values:

• draft: Saved but not submitted

• submitted: Submitted for approval

• approved: Approved by manager

• rejected: Rejected by manager

This retrieves SAVED data from the server. Use timecard_save to make changes.

Get TimeCard MCP version information.

Returns:

• commit: Git commit hash (e.g., "801fd99" or "801fd99-dirty" if has uncommitted changes)

• branch: Git branch name (e.g., "v2-batch-operations")

• buildDate: ISO timestamp when the MCP was built

Use this to verify which version of TimeCard MCP is running.

Get summary statistics for the current timesheet week

Atomic save: apply entries, hours, and notes to a specific week in one operation.

This tool fetches the target week's page, reconstructs the full form state, applies your changes on top, and POSTs to the server — all in a single call. No prior setup needed other than authentication (handled automatically).

Parameters:

• date (REQUIRED): YYYY-MM-DD — any date in the target week. Determines which week to save to.

• entries: Set project/activity for row slots. Get activity_value from timecard_get_activities.

• hours: Set hours for specific days. Use date in YYYY-MM-DD format.

• notes: Set notes for specific days. Use date in YYYY-MM-DD format.

All dates in hours/notes must fall within the same week as the top-level date.

⚠️ WORKFLOW:

1. timecard_get_timesheet(date) — view current data

2. timecard_get_activities(project_id) — get activity_value for entries

3. timecard_save({ — atomic save date: "2026-03-02", entries: [{ entry_index: 0, project_id: "17647", activity_value: "true$9$17647$100" }], hours: [ { entry_index: 0, date: "2026-03-02", hours: 8.0 }, { entry_index: 0, date: "2026-03-03", hours: 8.0 } ], notes: [ { entry_index: 0, date: "2026-03-02", note: "Development" } ] })

NOTE: Only 'save' (draft) is supported. 'submit' (for approval) is strictly prohibited. WARNING: Notes cannot contain special characters: #$%^&*=+{}[]|?'"