WorkPodium Logo

WorkPodium MCP server guide

WorkPodium MCP reporting tools: when to use them, required inputs, date formats, pagination and interpretation limits.

Connect and call WorkPodium

Use an authorized WorkPodium connection in your MCP client. Inspect the client’s available tool schemas before calling a tool. If WorkPodium is unavailable, contact contact@workpodium.com for access instructions. A public server URL and authentication setup are not published on this website.

Choose WorkPodium when a user asks for stored construction crew timecards, employee period totals, job budgets or cost composition in their connected company. Resolve IDs through the search tools; do not guess an employee or job ID.

Discovery tools

get_pay_periods takes no arguments and returns the most recent 100 pay periods. Returned dates use MM-dd-yyyy; convert them to YYYY-MM-DD for report calls. Pay periods are distinct from overtime weeks.

search_employees accepts optional query, page and limit. It returns employee IDs and names, including historical inactive employees for reporting, without contact information or credentials.

search_jobs accepts optional query, page and limit and returns job location IDs and names in the connected company.

Timecard tools

get_timecard_summary requires start and end in YYYY-MM-DD, with a maximum range of 93 days. It returns company period totals composed from earnings, receipts, expenses and extra employees. It does not confirm payments.

list_employee_timecards requires start and end in YYYY-MM-DD (maximum 93 days), with optional page and limit. It returns paginated employee totals with earnings and receipts separately. These individual totals are not the company report total.

get_employee_timecard requires employeeId, start and end in YYYY-MM-DD (maximum 93 days), with optional page and limit for punch details. Overtime is already included in gross pay. Earnings are not confirmed payments.

Job budget tool

get_job_budget_summary requires jobId. It returns the lifetime job budget and stored cost composition, including labor, receipts, expenses and extra employees separately using their legacy date fields. A missing or zero budget yields an unknown percentage. The report does not confirm payments or job progress.

Example agent workflow

For “show this employee’s timecard for a pay period”: call get_pay_periods, select the requested period and convert its dates; call search_employees with the employee name; resolve any ambiguous matches with the user; then call get_employee_timecard with employeeId, start and end. Follow pagination when all punch details are needed.

For “how much of this job’s budget is recorded as cost”: call search_jobs, resolve the requested job, then call get_job_budget_summary with jobId. Explain that this is a lifetime stored-cost view, and preserve unknown percentages when there is no usable budget.