Timetastic MCP server

What the model can do

Timetastic staff leave: who is off on which days (bookings, public holidays and non-working days), leave requests with their type, dates, duration and status (pending, approved, declined, cancelled), users with their department and approver, departments, leave types and public holidays. Can book leave for a person, approve, decline or cancel a request, add time off in lieu, add a department, and add or archive a user, each only when asked.

Reads

• timetastic_usersTimetastic users: name, work e-mail, department, approver, whether they are an admin, director or account owner, start date…
• timetastic_leaveTimetastic leave bookings and requests ("holidays" covers every kind of absence) that overlap a date window: who, leave type, start and end…
• timetastic_whos_offWho is off, day by day, between two dates (at most 31 days): leave bookings with their leave type, public holidays, and, if asked, non-working days…
• timetastic_departmentsTimetastic departments: name, manager's user id, how many users, the most who may be off at once, and whether archived.
• timetastic_leave_typesTimetastic leave types (annual leave, sickness, training…): whether each comes off the allowance, needs approval, counts towards the most-off limit…
• timetastic_public_holidaysPublic holidays in Timetastic: name, date and the country or region set they belong to.

Acts, when you ask

These change something in Timetastic. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• timetastic_book_leaveBook leave in Timetastic for one person (user_id), from one date to another, as a leave type.
• timetastic_approve_leaveApprove a pending Timetastic leave request.
• timetastic_decline_leaveDecline a pending Timetastic leave request, with an optional reason the person sees.
• timetastic_cancel_leaveCancel a Timetastic leave booking or request; the days go back to the person's allowance.
• timetastic_add_toilAdd time off in lieu (TOIL) to one person's allowance for a leave year, in their allowance unit (days or hours), with a note of what it is for.
• timetastic_add_departmentAdd a Timetastic department with a manager (a user id) and optionally the most people who may be off at once (0 for no limit).
• timetastic_add_userAdd a user to Timetastic in a department with an annual allowance in days.
• timetastic_archive_userArchive a Timetastic user who has left, from a date in the past.

Connect it

First connect Timetastic on Dashboard → Connections, then add Memtro to your client once. The Timetastic tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Timetastic connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Who is off next week?
• › Which leave requests are waiting for approval?
• › Who in the support team is off on Friday?
• › Which public holidays are coming up in the UK this year?
• › Approve Maya's leave request for the 14th and let her know

Questions

Is this an official Timetastic MCP server?

No. It is Memtro's MCP server with Memtro's Timetastic connector behind it: the connector reads Timetastic through its API with the credentials you connect on Dashboard → Connections, and Timetastic publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Timetastic?

Only when you ask, and only what it has been granted: book leave for one person, optionally e-mailing them and their approver; approve a pending leave request, optionally e-mailing the person; decline a pending leave request, optionally e-mailing the person (cannot be undone); cancel a leave booking (cannot be undone); add time off in lieu (TOIL) to a person's allowance for a year; add a department with its manager; add a user, optionally sending them a welcome e-mail to sign in; archive a user, logging them out of Timetastic. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · People and HR

• BambooHR MCP server
• Personio MCP server
• Microsoft Entra ID MCP server
• Google Workspace MCP server
• HiBob MCP server
• Greenhouse MCP server