Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Read Tamigo departments, employees, shifts, absences and opening hours; register attendance.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
https://tamigo.usefulapi.io/mcpRun this in your terminal
claude mcp add --transport http tamigo https://tamigo.usefulapi.io/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"tamigo": {
"url": "https://tamigo.usefulapi.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"tamigo": {
"type": "http",
"url": "https://tamigo.usefulapi.io/mcp"
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
ChatGPT connects only to servers on the internet:
https://tamigo.usefulapi.io/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.
tamigo_list_departmentsList 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_employeesList 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_detailsDetailed 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_shiftsPer 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_absencesAll 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_hoursNormal and special opening hours per department for a date range. GET /OpeningHours/{start}/{end}/.
tamigo_register_attendanceWRITE: 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_revenueWRITE: 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
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 52 ms (HTTP 200)
No sign-in needed
Read 8 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.16.3) reached the registry yesterday.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, Apify MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Read Tamigo departments, employees, shifts, absences and opening hours; register attendance.
Live endpoint: https://tamigo.usefulapi.io/mcp · Homepage: https://usefulapi.io/tamigo
https://tamigo.usefulapi.io/mcp.claude mcp add --transport http tamigo https://tamigo.usefulapi.io/mcp, then run /mcp to log in.{
"mcpServers": { "tamigo": { "url": "https://tamigo.usefulapi.io/mcp" } } }
Add only the URL. Do not add an Authorization header or an API key to the client config: the server signs you in with OAuth, and the login page asks for your Tamigo credentials.
Step-by-step setup, where to find your credentials, and FAQ: https://usefulapi.io/tamigo/
On first connect you'll enter your Tamigo application name and application key (Configuration → Web Services (API); an administrator creates them).
| Tool | Type | What it does |
|---|---|---|
tamigo_list_departments | read | List departments |
tamigo_list_employees | read | List employees |
tamigo_list_employee_details | read | List employee details |
tamigo_list_shifts | read | List shifts (original, planned, worked) |
tamigo_list_absences | read | List absences |
tamigo_get_opening_hours | read | Get opening hours |
tamigo_register_attendance | write | Register check-ins / check-outs |
tamigo_upload_daily_revenue | write | Upload daily revenue |
tamigo_usage_status | meta | Usage status (free-tier meter) |
tamigo_request_feature | meta | Request a missing feature |
tamigo_upgrade | meta | Upgrade to Pro or Pro+ |
tamigo_cancel_subscription | meta | Cancel the Pro subscription |
read tools are read-only; write tools mutate data (clients should confirm them); meta tools report usage, manage your subscription or send a feature request.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Pro (per user) | $9/mo or $90/yr (2 months free) | Unlimited* |
\*Pro has a fair use limit of 10,000 tool calls a month on this server. For more, write to support@usefulapi.io.
Pro covers this server only. Subscribe with tamigo_upgrade (it returns a Stripe Checkout link). Cancel any time with tamigo_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running tamigo_upgrade before then undoes the cancel. Or write to support@usefulapi.io.
MIT © usefulapi. Not affiliated with or endorsed by Tamigo.