# Tamigo Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Tamigo

View staff schedules, absences, and departments; record attendance and revenue for your business.

- Record: https://musedirectory.ai/connector/tamigo
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/tamigo/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 174ms, checked 2026-10-29T22:41:16Z
- Endpoint: https://tamigo.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T22:41:16Z)
- Source: Found in the official MCP Registry (io.usefulapi/tamigo) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Ftamigo

Connects to Tamigo workforce management for restaurants and retail. View departments, employees, shifts, absences and opening hours. Register employee check-in and check-out times, and upload daily revenue data.

Example request: "Show me who is scheduled to work tomorrow and record when my staff members clock in."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Tamigo to help me. It is a free service with an MCP server at https://tamigo.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- 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
- 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 /sh
- 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 t
- 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

Screening checks:
- MCP handshake: pass (Answered in 174ms)
- Domain against threat feeds (Cloudflare security DNS): pass (tamigo.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (8 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)