mcpbeat Sign in

Tamigo MCP by usefulapi MCP Server

by usefulapi Your server? Claim it
answering

Tamigo MCP by usefulapi is answering right now. Last checked moments ago. It exposes 8 tools. Last commit 1 Nov 2026.

Read Tamigo departments, employees, shifts, absences and opening hours; register attendance.

Uptime history 8 days of history · worst day 99%
8 days agonow
100.0%
Uptime 24h
92 of 92 checks
8
Tools
read from the server
185 ms
Response time
average over 24h
1
Stars
last commit 1 Nov 2026

What changed 14

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 25 October 2026. No other catalogue keeps this.

31 Oct a tool changed version4 times that day
30 Oct a tool changed version2 times that day
29 Oct a tool changed version2 times that day
28 Oct a tool changed version2 times that day
25 Oct a tool changed version4 times that day
and 9 more, back to 25 October 2026

Tamigo MCP by usefulapi missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 0 min ago.

run in your terminal
claude mcp add tamigo --transport http https://tamigo.usefulapi.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://tamigo.usefulapi.io/mcp
~/.codex/config.toml
[mcp_servers.tamigo]
url = "https://tamigo.usefulapi.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "tamigo": {
      "url": "https://tamigo.usefulapi.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "tamigo": {
      "type": "http",
      "url": "https://tamigo.usefulapi.io/mcp"
    }
  }
}

Available tools 8

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

tamigo
tamigo_get_opening_hours
Normal and special opening hours per department for a date range. GET /OpeningHours/{start}/{end}/.
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_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_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 in slices: pass the reply's next_page and next_offset to continue. GET /employees/getemployeedetails/.
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_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}/{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_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.
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 has revenue for that department may be overwritten by Tamigo, so confirm the rows first. POST /Revenues/.

Endpoints

URLTransportStateLatencyChecked
https://tamigo.usefulapi.io/mcp streamable-http answering 260 ms 0 min ago

Alternatives to Tamigo MCP by usefulapi

same job, measured the same way
Talenta MCP by usefulapi
by usefulapi

MCP server for Talenta — read employee, attendance, leave, payroll and recruitment data.

30 tools answering
SmartHR MCP by usefulapi
by usefulapi

MCP server for SmartHR — employees, departments, dependents and employee invitations.

23 tools answering
Breathe HR MCP by usefulapi
by usefulapi

Read Breathe HR employees, absences, sickness and leave; create and review leave requests.

25 tools answering
Craftboxx MCP by usefulapi
by usefulapi

Read employees, assignments, timesheets and absences; create customers and projects in Craftboxx.

16 tools answering
Smartplan MCP by usefulapi
by usefulapi

Read accounts, staff, shifts, worklogs and absence dates in Smartplan.

14 tools answering
Eventzilla MCP by usefulapi
by usefulapi

Read Eventzilla events, tickets, orders, attendees and users; open or close ticket sales.

11 tools answering
Jisr MCP by usefulapi
by usefulapi

Read employees, attendance, leave and payroll; create employee records and import device punches.

16 tools answering
TimeTac MCP by usefulapi
by usefulapi

Read hours, absences and projects; start timers, add entries, approve leave in TimeTac.

16 tools answering

Tamigo MCP by usefulapi — questions

Answers built from our own checks of this server.

What can Tamigo MCP by usefulapi do?
It exposes 8 tools, read directly from the server on our last check. Among them: tamigo_get_opening_hours, tamigo_list_absences, tamigo_list_departments, tamigo_list_employee_details, tamigo_list_employees, tamigo_list_shifts and 2 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Tamigo MCP by usefulapi working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 185 ms. The bar chart above shows every period we have measured.
How do I connect Tamigo MCP by usefulapi?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Tamigo MCP by usefulapi need an API key?
No. Tamigo MCP by usefulapi completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 8 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Tamigo MCP by usefulapi?
It answers our handshake in 185 ms on average, which is faster than 75% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is Tamigo MCP by usefulapi open source?
The code is open source: it is published under the MIT licence, written in JavaScript, 1 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at tamigo.usefulapi.io, which runs on its operator's own terms.