io.usefulapi/tamigo · v1.0.0 · communication
Tamigo MCP by usefulapi is healthy: it completed an MCP handshake in 857 ms and exposes 8 tools.
Read Tamigo departments, employees, shifts, absences and opening hours; register attendance.
Endpoint: https://tamigo.usefulapi.io/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 8 |
| Latency | 857 ms |
| Last checked (UTC) | 2026-10-24T11:30:16.808Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-24T11:30:16.808Z | Healthy | 857 |
tamigo_list_departments | 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/. |
tamigo_list_employees | 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/. |
tamigo_list_employee_details | 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 |
tamigo_list_shifts | 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}/{en |
tamigo_list_absences | 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/. |
tamigo_get_opening_hours | Normal and special opening hours per department for a date range. GET /OpeningHours/{start}/{end}/. |
tamigo_register_attendance | 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_departmen |
tamigo_upload_daily_revenue | 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 h |