Tamigo MCP by usefulapi

io.usefulapiPublished by usefulapi.ioOfficial publisherv1.17.4Updated Nov 7, 2026

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

The publisher's own server: Ably MCP by usefulapi

Overview

AI-generated overview

Hosted Tamigo connector that lets an assistant read departments, employees, shifts, absences and opening hours, and register attendance or daily revenue.

What you can do
  • List departments with their POS keys and parent units
  • List employees and detailed records: roles, contracts, wage history, absence balances, availability
  • Read shifts per employee and day: original rota, planned rota and worked hours for a date range
  • List absences overlapping a date range with type and approval status
  • Get normal and special opening hours per department
  • Write check-in/check-out times and import daily revenue per department
When to use it
Useful when you work with Tamigo for staff scheduling and want to ask questions in plain language: planned versus worked hours, who is absent next week, department keys, opening hours, or payroll checks. Also for pushing attendance or revenue figures into Tamigo from an assistant instead of a POS or cash-register system.
Requirements
Remote MCP endpoint; no local install. Sign-in is via OAuth, and the login page asks for Tamigo credentials plus the Tamigo application name and application key created by an administrator under Configuration → Web Services (API). No API key or Authorization header goes in the client config. A free plan allows 50 tool calls per month.
Before you install
Two tools write to Tamigo: attendance registration and daily revenue import, the latter overwriting an existing date. The server asks for Tamigo application credentials and signs in with OAuth. Usage is metered and paid plans (Pro, Pro+) are sold through Stripe checkout links returned by a tool; cancellation has no refund for the current period. Employee data includes contact, contract and wage details.

Installation

In SourceWeft

  1. Open Tamigo MCP by usefulapi in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.usefulapi%2Ftamigo/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "tamigo-by-usefulapi": {
      "type": "http",
      "url": "https://tamigo.usefulapi.io/mcp"
    }
  }
}

README

Tamigo MCP by usefulapi

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

Live endpoint: https://tamigo.usefulapi.io/mcp · Homepage: https://usefulapi.io/tamigo

Connect

  • Claude (claude.ai, Desktop): open Customize → Connectors, click + Add → Add custom connector, and paste https://tamigo.usefulapi.io/mcp.
  • Claude Code: claude mcp add --transport http tamigo https://tamigo.usefulapi.io/mcp, then run /mcp to log in.
  • VS Code: Add to VS Code.
  • Cursor and other clients: add the URL as a remote MCP server:
json
{  "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).

Tools

ToolTypeWhat it does
tamigo_list_departmentsreadList departments
tamigo_list_employeesreadList employees
tamigo_list_employee_detailsreadList employee details
tamigo_list_shiftsreadList shifts (original, planned, worked)
tamigo_list_absencesreadList absences
tamigo_get_opening_hoursreadGet opening hours
tamigo_register_attendancewriteRegister check-ins / check-outs
tamigo_upload_daily_revenuewriteUpload daily revenue
tamigo_usage_statusmetaUsage status (free-tier meter)
tamigo_request_featuremetaRequest a missing feature
tamigo_upgrademetaUpgrade to Pro or Pro+
tamigo_cancel_subscriptionmetaCancel 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.

Pricing

PlanPriceLimit
Free$050 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 [email protected].

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 [email protected].

License

MIT © usefulapi. Not affiliated with or endorsed by Tamigo.

Source: servers/tamigo/README.md at commit 4046075

Tools

8

tamigo_list_departments

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/.

Parameterslimitoffsetinclude_parents

tamigo_list_employees

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/.

Parameterslimitoffset

tamigo_list_employee_details

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/.

Parameterspagelimitoffsetinclude_deleted

tamigo_list_shifts

List shifts (original, planned, worked)

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}/.

Parameterslimitoffsetend_daterequiredstart_daterequireddepartment_id

tamigo_list_absences

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/.

Parameterslimitoffsetend_daterequiredstart_daterequired

tamigo_get_opening_hours

Get opening hours

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

Parameterslimitoffsetend_daterequiredstart_daterequired

tamigo_register_attendance

Register check-ins / check-outs

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.

Parametersentriesrequired

tamigo_upload_daily_revenue

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/.

Parametersrowsrequired

Version history

15
  1. v1.17.4LatestNov 7, 2026
  2. v1.16.3Nov 5, 2026
  3. v1.16.2Nov 5, 2026
  4. v1.16.1Nov 4, 2026
  5. v1.16.0Nov 3, 2026
  6. v1.15.1Nov 3, 2026
  7. v1.14.0Nov 1, 2026
  8. v1.12.0Oct 31, 2026
  9. v1.11.0Oct 31, 2026
  10. v1.10.2Oct 30, 2026
  11. v1.10.0Oct 30, 2026
  12. v1.5.0Oct 26, 2026
  13. v1.2.3Oct 25, 2026
  14. v1.2.0Oct 25, 2026
  15. v1.1.0Oct 24, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

Other Usefulapi integrations