Tamigo MCP by usefulapi

Normal and special opening hours per department for a date range. GET /OpeningHours/{start}/{end}/.

All absences (holiday, sickness, leave) that overlap a date range: employee, department, absence type, start and end, and whether it is approved or rejected. GET /LeaveRequests/All/.

List all departments (shops, restaurants, units) of the company: DepartmentId (a GUID, used by other tools), DepartmentKey (the POS key set in Tamigo), Name, IsDefault and ParentDepartmentId. GET /departments/application/.

Detailed employee records, 500 per page in alphabetical order: contact data, roles per department, home department, contract hours, wage type and history, absence balances, competencies, custom columns, notes and availability. Bank details and ID numbers are never returned. Large pages are returned in slices: pass the reply's next_page and next_offset to continue. GET /employees/getemployeedetails/.

List all employees of the company (basic): EmployeeId, Name, Email, IsPlanner, PosKey (the employee key used by the attendance tool) and DepartmentRoles. For contract, wage and absence-balance details use tamigo_list_employee_details. GET /employees/.

Per employee and day, the original rota, the planned (current) rota and the worked (timesheet) hours for a date range, with department, employee POS key, email and wage number. Use it for payroll checks, hours worked vs planned and who worked when. Shift values are hours. GET /shifts/all/{start}/{end}/.

WRITE: register check-in and check-out times in the Tamigo timesheet, for one or many employees (the same call a POS system makes). Each entry names a department key and an employee key (the POS keys set in Tamigo under Configuration -> Departments / POS Keys; they are shown by tamigo_list_departments and tamigo_list_employees) and EITHER a check_in_time OR a check_out_time, in chronological order per employee. A break is registered by giving the same activity_name (for example Lunch, SmallBreak) on its check-in and its check-out. Tamigo may round the times by the company's rules, and the reply echoes the times actually registered. This changes worked hours and wages: it is not undone by repeating it, so confirm the entries first.

WRITE: import daily revenue per department into Tamigo (the same call a cash-register system makes), used for revenue-based planning and KPIs. Each row is a department key (the POS key set in Tamigo), a date and a revenue amount (a plain number with a dot as decimal separator). A date that already has revenue for that department may be overwritten by Tamigo, so confirm the rows first. POST /Revenues/.