mcpField
T
Tamigo MCP by usefulapi

Tamigo MCP by usefulapi

Remote
usefulapi.ioBusiness & Marketing0Updated today

About Tamigo MCP by usefulapi

Tamigo MCP by usefulapi connects MCP clients to Tamigo workforce data. It supports read access to staffing information and write actions for attendance and revenue.

Key features

  1. 01List departments and employees
  2. 02View shifts and absences
  3. 03Retrieve opening hours
  4. 04Register attendance
  5. 05Upload daily revenue

Use cases

  1. 01Review employee shifts and absences
  2. 02Check opening hours
  3. 03Record employee check-ins and check-outs
  4. 04Submit daily revenue

MCP support

Exposes Tamigo data and actions as tools for MCP clients. The remote server uses OAuth sign-in and requires Tamigo application credentials.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://tamigo.usefulapi.io/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project 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:
{
  "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 (unlimited*)
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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.