[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Timetastic API and MCP server

> Yes, Timetastic has a REST API with a bearer token, and no official MCP server (checked 20 Oct 2026). Only admin users can get a token, and the API has no endpoints for the monthly and annual summary reports.

Leave and absence planner for teams: a Wallchart of who is off, leave requests with approvals, allowances and downloadable reports.

## What is the Timetastic API?

Cotlet's Timetastic API exposes 9 endpoints for your own Timetastic account: list who is off on the Wallchart, get one person's calendar, list pending leave requests, get the monthly leave summary, get the annual allowance summary, book time off, approve a leave request, decline a leave request and cancel a booking. The list_wallchart endpoint returns absences per person for one month, as the Wallchart shows them. Each endpoint takes simple JSON inputs like reason, request_id or month and works both as an operation of the timetastic_read or timetastic_write MCP tool for agents and as a REST call for scripts.

- **Category:** [Productivity & teams](https://cotlet.dev/integrations/category/productivity-teams.md)
- **Endpoints:** 9 (5 read, 4 write)
- **Updated:** 2026-10-22

Yes, Timetastic has a REST API with a bearer token, and no official MCP server (checked 20 Oct 2026). Cotlet is a hosted MCP server and REST API for Timetastic with 9 endpoints (5 read, 4 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Timetastic have an official API?

Yes, Timetastic has a REST API with a bearer token, and no official MCP server (checked 20 Oct 2026). Only admin users can get a token, and the API has no endpoints for the monthly and annual summary reports.

| Task | Timetastic official | Cotlet |
|---|---|---|
| See who is off in a date range | Yes: Needs an admin API token | Yes |
| Read pending leave requests | Yes: Needs an admin API token | Yes |
| Approve or decline a request | Yes: Needs an admin API token | Yes |
| Book time off for yourself or someone else | Yes: Needs an admin API token | Yes |
| Cancel a booking | Yes: Needs an admin API token | Yes |
| Read one person's allowance and bookings | Yes: Needs an admin API token | Yes |
| Monthly and annual summary reports | Partly: The API lists holidays and allowances, but has no report endpoints; totals per leave type are built by hand | Yes |
| Use any of this as a manager or employee | No: Only admin users have access to an API token | Yes |

Sources: [Timetastic Help: Timetastic API](https://help.timetastic.co.uk/en/articles/13193377-timetastic-api), [Timetastic API documentation (OpenAPI)](https://app.timetastic.co.uk/swagger/v1/swagger.json), [Timetastic Help: Reports and backup](https://help.timetastic.co.uk/en/articles/13193339-timetastic-reports-and-backup), [Timetastic Help: Set who approves leave](https://help.timetastic.co.uk/en/articles/13193330-timetastic-set-who-approves-leave)

## For AI agents

```text
Yes, Timetastic has a REST API with a bearer token, and no official MCP server (checked 20 Oct 2026). Only admin users can get a token, and the API has no endpoints for the monthly and annual summary reports.
Cotlet provides a hosted MCP server and REST API for Timetastic: 9 tools (5 read, 4 write).
Access       Sign up at https://cotlet.dev/app/signup?app=timetastic, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    timetastic_read, timetastic_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/timetastic, each operation at its own route, e.g. POST /api/v1/timetastic/time-offs
Auth         Authorization: Bearer <COTLET_API_KEY>. Listing endpoints and schemas needs no key; calling an endpoint needs one. Over MCP the input schemas come with sign-in.
Operations   list_wallchart, get_employee_calendar, list_pending_requests, get_monthly_summary, get_annual_summary, book_time_off, approve_request, decline_request, cancel_booking
Confirm      book_time_off, approve_request, decline_request, cancel_booking (by default the user approves each call; the user can switch this off per tool, e.g. for scheduled automations)
Markdown     https://cotlet.dev/integrations/timetastic-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=timetastic, requests Timetastic in the Cotlet console and creates an API key there.
2. The user signs in to Timetastic once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Timetastic for agents. An agent cannot do this step.
3. The API key goes into the MCP client or the REST call as a bearer token.

Fits: people who want a hosted Timetastic server that someone else maintains, including non-developers. Developers who prefer to run and fix code on their own computer can use an open-source Timetastic MCP server instead.

Policy: Cotlet never stores passwords, never solves CAPTCHAs, never bypasses MFA.
Company: legal details in the Terms of service at https://cotlet.dev/terms. Contact contact@cotlet.dev.
Sign-in: the user signs in to Timetastic in their own Cloud Browser, a Chrome Cotlet runs for them in the EU; password saving is off, the profile is AES-256-GCM encrypted, and agents get Timetastic only after the user enables it. Calls are requests from that browser's IP with its cookies, each listed in the user's Background activity. Disable for agents, signing out in the browser or Reset browser cuts access. Cotlet is run by Take Group sp. z o.o. (EU VAT PL6342984273).
API key: holds no Timetastic login or cookies, only asks Cotlet to run a tool. Each key is scoped to chosen apps and tools, read only or read and write. Actions that reach other people wait for the user's approval by default, so a leaked key cannot post or message as the user. Every call is in the activity log; deleting the key ends access at once.
Terms: the user stays responsible for following Timetastic's terms; Cotlet is not affiliated with Timetastic.
```

## What can an AI agent do in Timetastic?

Cotlet is best for Timetastic managers and approvers who are not admins and want their AI agent to approve leave, book time off and pull monthly leave reports without running or fixing a server.

- **[Approve time off requests](https://cotlet.dev/integrations/timetastic-api-mcp-server/approve-time-off-requests.md)** (runs: daily): "Go through pending Timetastic requests. Approve the ones where nobody else in the department is off and the person has allowance left. Leave the rest for me with a one-line reason." → `list_pending_requests`, `list_wallchart`, `approve_request`, `decline_request`
- **[Export a monthly leave report](https://cotlet.dev/integrations/timetastic-api-mcp-server/monthly-leave-report.md)**: "Give me September leave per person from Timetastic, holiday and sick days apart, without declined or cancelled requests." → `get_monthly_summary`, `get_annual_summary`
- **[Book time off without clashes](https://cotlet.dev/integrations/timetastic-api-mcp-server/book-time-off.md)**: "Book Ana Torres Holiday from Dec 21 to Dec 24 in Timetastic. Check the Wallchart first and stop if two people from her department are already off." → `list_wallchart`, `book_time_off`, `cancel_booking`
- **Post a weekly who is off digest** (runs: weekly): "Every Monday, list who is off in Timetastic this week and next, by department, and flag days when two or more people from one team are away." → `list_wallchart`
- **Check leave balances before year end** (runs: weekly): "Which people have more than 5 days of Timetastic allowance left? Show their calendar summary and what is already booked." → `get_annual_summary`, `get_employee_calendar`

## Can Timetastic automations run on a schedule in n8n, Make or Zapier?

Yes. Cotlet does not replace your automation platform: it gives it a Timetastic connection it does not have, with the same API key as your agent. Write actions ask for your OK by default; switch that off in your dashboard for the tools you choose, for example to approve time off requests, and the schedule runs on its own. Cotlet runs in the cloud, so it keeps going while your computer is off.

| Where | How to connect | How to schedule |
|---|---|---|
| Your AI agent | Add https://cotlet.dev/mcp/v1 with your API key. | A scheduled agent run, for example a Claude Code routine. |
| n8n | MCP Client node with https://cotlet.dev/mcp/v1, or an HTTP Request node with the endpoint's method and URL, such as GET https://cotlet.dev/api/v1/timetastic/pending-requests. | Schedule Trigger node. |
| Make | HTTP module: the endpoint's method and URL with an Authorization: Bearer header, and a JSON body for POST, PUT and PATCH. | Scenario schedule. |
| Zapier | Webhooks by Zapier, Custom Request: the same method, URL, header and body. | Schedule by Zapier trigger. |
| Your own script | GET https://cotlet.dev/api/v1/timetastic/pending-requests with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 9 endpoints on this page, with parameters and example responses, can be listed without an account. Calling one returns 401 without an API key and 403 while the key has no access to Timetastic.

### list_wallchart

Absences per person for one month, as the Wallchart shows them. Access: read. REST: `GET /api/v1/timetastic/wallcharts`. MCP: `timetastic_read → list_wallchart`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `month` | string | no | Month as YYYY-MM. Defaults to the current month. |
| `filter` | string | no | A department name or My favourites, as in the Wallchart Filter menu. Defaults to your own department. |

Returns one entry per person with their absences in that month and the allowance remaining that the Wallchart shows next to the name. Each absence has its leave type and whether it is approved or pending. It shows only the people your account can see on its Wallchart.

Example response:

```json
{
  "month": "2026-11",
  "filter": "Support",
  "people": [
    {
      "employee": "Ana Torres",
      "allowance_remaining": 10,
      "absences": [
        {
          "from": "2026-11-23",
          "to": "2026-11-27",
          "leave_type": "Holiday",
          "status": "Pending",
          "days": 5
        }
      ]
    },
    {
      "employee": "Ben Okafor",
      "allowance_remaining": 5,
      "absences": [
        {
          "from": "2026-11-25",
          "to": "2026-11-27",
          "leave_type": "Holiday",
          "status": "Approved",
          "days": 3
        }
      ]
    },
    {
      "employee": "Priya Nair",
      "allowance_remaining": 18,
      "absences": [
        {
          "from": "2026-11-30",
          "to": "2026-11-30",
          "leave_type": "Sick leave",
          "status": "Approved",
          "days": 1
        }
      ]
    }
  ]
}
```

### get_employee_calendar

A year of one person's bookings with leave taken and remaining. Access: read. REST: `GET /api/v1/timetastic/employee-calendar`. MCP: `timetastic_read → get_employee_calendar`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `employee` | string | yes | Full name of the person, as the Wallchart shows it. |
| `year` | integer | no | Year such as 2026. Defaults to the current year. |

Returns the bookings of that year with leave type and status, and the summary Timetastic shows beside the Calendar: annual leave taken, annual leave remaining and total non-deductible leave. Managers and admins can open an employee's Calendar for their leave summary.

Example response:

```json
{
  "employee": "Ana Torres",
  "year": 2026,
  "annual_leave_taken": 18,
  "annual_leave_remaining": 10,
  "non_deductible_leave": 1,
  "bookings": [
    {
      "from": "2026-09-07",
      "to": "2026-09-08",
      "leave_type": "Holiday",
      "status": "Approved",
      "days": 2
    },
    {
      "from": "2026-09-15",
      "to": "2026-09-15",
      "leave_type": "Sick leave",
      "status": "Approved",
      "days": 1
    }
  ]
}
```

### list_pending_requests

The requests waiting in your inbox, with the overlaps Timetastic flags. Access: read. REST: `GET /api/v1/timetastic/pending-requests`. MCP: `timetastic_read → list_pending_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `approver` | string | no | Only requests that go to this approver, by full name. Defaults to every request your account can see under View all. |

Returns each pending request with the person, department, leave type, dates, the days asked for, the reason and the approver. A request that overlaps another person's time off lists that person under clashes. It reads the inbox and changes nothing.

Example response:

```json
{
  "total": 2,
  "requests": [
    {
      "request_id": "5128840",
      "employee": "Ana Torres",
      "department": "Support",
      "leave_type": "Holiday",
      "from": "2026-11-23",
      "to": "2026-11-27",
      "days": 5,
      "reason": "Family visit",
      "requested_on": "2026-10-19",
      "approver": "Priya Nair",
      "clashes": [
        {
          "employee": "Ben Okafor",
          "from": "2026-11-25",
          "to": "2026-11-27"
        }
      ]
    },
    {
      "request_id": "5128861",
      "employee": "Tomas Lind",
      "department": "Support",
      "leave_type": "Holiday",
      "from": "2026-12-07",
      "to": "2026-12-11",
      "days": 5,
      "reason": "",
      "requested_on": "2026-10-20",
      "approver": "Priya Nair",
      "clashes": []
    }
  ]
}
```

### get_monthly_summary

Leave totals per person and leave type for one month, plus the booking rows. Access: read. REST: `GET /api/v1/timetastic/monthly-summary`. MCP: `timetastic_read → get_monthly_summary`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `month` | string | yes | Month as YYYY-MM. |
| `include_rows` | boolean | no | Also return the booking rows of the Leave sheet. Defaults to true. |

Reads the Monthly summary from Settings > Reporting & Backup: totals per active user by leave type, and the month's requests and bookings. The rows include declined and cancelled requests, each with its status. The account must be able to open that page, or the call fails with APP_PERMISSION_DENIED.

Example response:

```json
{
  "month": "2026-09",
  "totals": [
    {
      "employee": "Ana Torres",
      "leave": {
        "Holiday": 2,
        "Sick leave": 1
      }
    },
    {
      "employee": "Ben Okafor",
      "leave": {
        "Sick leave": 2
      }
    },
    {
      "employee": "Priya Nair",
      "leave": {}
    }
  ],
  "rows": [
    {
      "employee": "Ana Torres",
      "leave_type": "Holiday",
      "from": "2026-09-07",
      "to": "2026-09-08",
      "status": "Approved"
    },
    {
      "employee": "Ana Torres",
      "leave_type": "Sick leave",
      "from": "2026-09-15",
      "to": "2026-09-15",
      "status": "Approved"
    },
    {
      "employee": "Ben Okafor",
      "leave_type": "Sick leave",
      "from": "2026-09-02",
      "to": "2026-09-03",
      "status": "Approved"
    },
    {
      "employee": "Ben Okafor",
      "leave_type": "Holiday",
      "from": "2026-09-28",
      "to": "2026-09-30",
      "status": "Declined"
    }
  ]
}
```

### get_annual_summary

Allowance, carry forward, time in lieu, leave used and remaining per person for one year. Access: read. REST: `GET /api/v1/timetastic/annual-summary`. MCP: `timetastic_read → get_annual_summary`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `year` | integer | yes | Year such as 2026. |

Reads the Annual summary from Settings > Reporting & Backup and returns the Allowances sheet: allowance, brought forward, leave used, time in lieu and remaining per person. It does not return the Leave sheet; use get_monthly_summary for rows. The account must be able to open that page.

Example response:

```json
{
  "year": 2026,
  "unit": "days",
  "people": [
    {
      "employee": "Ana Torres",
      "allowance": 25,
      "carried_forward": 3,
      "used": 18,
      "time_in_lieu": 0,
      "remaining": 10
    },
    {
      "employee": "Ben Okafor",
      "allowance": 25,
      "carried_forward": 0,
      "used": 21,
      "time_in_lieu": 1,
      "remaining": 5
    }
  ]
}
```

### book_time_off

Request leave for yourself or, as a manager or admin, for someone else. Access: write, asks the user first. REST: `POST /api/v1/timetastic/time-offs`. MCP: `timetastic_write → book_time_off`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `who_for` | string | yes | Full name of the person the leave is for, as in the Who for field. |
| `from_date` | string | yes | First day, YYYY-MM-DD. |
| `to_date` | string | yes | Last day, YYYY-MM-DD. |
| `leave_type` | string | yes | Leave type as the Type drop-down lists it, for example Holiday or Sick leave. |
| `reason` | string | no | Optional reason the approver reads. |
| `confirm_override` | boolean | no | Manager or admin only: book anyway when Timetastic shows a staffing warning. Defaults to false. |

Returns the request id, the days booked, the status and the approver. When a department limit blocks an employee booking for themselves, the call returns Timetastic's message and books nothing. The approver gets an email. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "5129012",
  "employee": "Ana Torres",
  "leave_type": "Holiday",
  "from": "2026-12-21",
  "to": "2026-12-24",
  "days": 4,
  "status": "Pending",
  "approver": "Priya Nair",
  "warning": null
}
```

### approve_request

Approve one pending request from the inbox. Access: write, asks the user first. REST: `POST /api/v1/timetastic/requests/{request_id}/approve`. MCP: `timetastic_write → approve_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_id` | string | yes | Request id from list_pending_requests. |

Returns the request with its new status and who approved it. It works for the requests your account may approve; an approver handles their own people, and an admin can approve any employee's leave. Timetastic emails the person right away. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "5128840",
  "employee": "Ana Torres",
  "leave_type": "Holiday",
  "from": "2026-11-23",
  "to": "2026-11-27",
  "days": 5,
  "status": "Approved",
  "approved_by": "Priya Nair"
}
```

### decline_request

Decline one pending request, with an optional reason. Access: write, asks the user first. REST: `POST /api/v1/timetastic/requests/{request_id}/decline`. MCP: `timetastic_write → decline_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_id` | string | yes | Request id from list_pending_requests. |
| `reason` | string | no | Reason the employee reads in the decline. |

Returns the request with the status Declined and the reason. The employee is told right away. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "5128861",
  "employee": "Tomas Lind",
  "leave_type": "Holiday",
  "from": "2026-12-07",
  "to": "2026-12-11",
  "days": 5,
  "status": "Declined",
  "reason": "Planning week, the whole team is needed",
  "declined_by": "Priya Nair"
}
```

### cancel_booking

Cancel a booking with an optional reason. Access: write, asks the user first. REST: `POST /api/v1/timetastic/requests/{request_id}/booking/cancel`. MCP: `timetastic_write → cancel_booking`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_id` | string | yes | Request id of the booking. |
| `reason` | string | no | Optional reason that goes with the cancellation. |

Returns the booking with the status Cancelled. Anyone can cancel their own leave from tomorrow on; leave for today or earlier needs the approver or an admin, or the call fails with APP_PERMISSION_DENIED. The approver gets an email. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "5129012",
  "employee": "Ana Torres",
  "leave_type": "Holiday",
  "from": "2026-12-21",
  "to": "2026-12-24",
  "status": "Cancelled",
  "cancelled_by": "Ana Torres"
}
```

## How do I connect Timetastic to Claude Code, Codex or Cursor?

Connecting Timetastic takes three steps: sign up, sign in to Timetastic once in your Cloud Browser and enable it for agents, then add one MCP server or call the REST API with the same key.

### Connect Timetastic to your agent.

1. **Create an account** Sign up and add Timetastic in the console. Your API key is there too.

2. **Sign in to Timetastic in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Timetastic there yourself, the way you always do, then press Enable for agents, read only or read and write. We never save your password, and your agent keeps working even when your computer is off.

3. **Add Cotlet to your agent** Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

   Claude Code:

```
claude mcp add --transport http cotlet \
  https://cotlet.dev/mcp/v1 \
  --header "Authorization: Bearer $COTLET_API_KEY"
```

   Cursor:

```
{
  "mcpServers": {
    "cotlet": {
      "url": "https://cotlet.dev/mcp/v1",
      "headers": {
        "Authorization": "Bearer ${COTLET_API_KEY}"
      }
    }
  }
}
```

   Codex:

```
# ~/.codex/config.toml
[mcp_servers.cotlet]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
```

4. **Ask your agent** Ask in plain words. Your agent finds the Timetastic tools on the server and calls them for you; anything that reaches other people waits for your OK unless you switch that off for a tool.

```
Go through pending Timetastic requests. Approve the ones where nobody else in the department is off and the person has allowance left. Leave the rest for me with a one-line reason.
```

### Call Timetastic from your scripts.

1. **Export your API key** Your scripts use the same API key as your agent. Keep it in an environment variable, never in your code.

```
export COTLET_API_KEY="cotlet_..."
```

2. **Call a tool** Every tool is an endpoint under /api/v1/timetastic with its own method and path, listed with the endpoints above. Path parameters go in the URL; the other parameters go in the query for GET and DELETE and in a JSON body otherwise.

```
curl -X POST https://cotlet.dev/api/v1/timetastic/time-offs \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"who_for":"Ana Torres","from_date":"2026-12-21","to_date":"2026-12-24","leave_type":"Holiday","reason":"Christmas week"}'
```

3. **Read the result** You get plain JSON back, ready for your script. A failed call costs nothing.

```
{
  "request_id": "5129012",
  "employee": "Ana Torres",
  "leave_type": "Holiday",
  "from": "2026-12-21",
  "to": "2026-12-24",
  "days": 4,
  "status": "Pending",
  "approver": "Priya Nair",
  "warning": null
}
```

## Why use Cotlet for Timetastic?

**Built for agents**

- One MCP server for every app you connect.
- The same tools as a REST API for scripts and cron jobs.
- Works with Claude Code, Codex and Cursor.

**Your login stays yours**

- You sign in to Timetastic yourself, in your own Cloud Browser. We never save your password; the profile is encrypted with AES-256-GCM, the cipher 1Password uses.
- A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory.
- The model never sees a login.
- No stored passwords, no CAPTCHA solving, no MFA bypass.

**You stay in control**

- Scope each API key: its apps, its tools, read only or read and write.
- Anything that reaches other people waits for your OK, so a leaked key cannot post or message as you.
- Every background request listed in your Background activity. Disable for agents in one click.

**Kept working for you**

- We test every integration every 6 hours.
- When Timetastic changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Timetastic to Cotlet?

Yes. You sign in to Timetastic yourself, in your own Cloud Browser, and we never save your password. Your agents only get Timetastic once you enable it, and every background request is listed. The browser profile is stored encrypted with AES-256-GCM, the same cipher 1Password uses for its vaults and Apple for iCloud Keychain. Independent public scanners grade cotlet.dev A+ and find it clean; click a result to rerun it yourself.

- **A+ on Qualys SSL Labs**: Encryption in transit: TLS setup and certificates, on all four server addresses. [Live result](https://www.ssllabs.com/ssltest/analyze.html?d=cotlet.dev)
- **A+ on securityheaders.com**: Browser protections sent with every page, all six headers present. [Live result](https://securityheaders.com/?q=cotlet.dev&followRedirects=on)
- **A+ on Mozilla Observatory**: Mozilla's web security baseline: score 120 of 100, 12 of 12 tests passed. [Live result](https://developer.mozilla.org/en-US/observatory/analyze?host=cotlet.dev)
- **Clean on Sucuri SiteCheck**: No malware, spam or defacement, and not on any of 9 blocklists, Google Safe Browsing included. [Live result](https://sitecheck.sucuri.net/results/cotlet.dev)

[How Cotlet protects your access](https://cotlet.dev/security.md)

### Common concerns

**Who runs Cotlet?**

Cotlet is run by Take Group, a Polish software company working since 2019. Take Group runs about 3,200 websites on its own systems and has its own DevOps team for infrastructure security. We built and used integrations like this inside the company for years before opening them as Cotlet.

**Is this an official Timetastic integration?**

No, Cotlet is independent of Timetastic. Timetastic's own API is too limited for this work. Cotlet works through your own Timetastic account, the way you use Timetastic in the browser, so you need no partner approval and no developer setup.

**What about client data and GDPR?**

Cotlet is run from the EU and follows the GDPR. Cloud Browsers run in Finland, a Tier 1 country in the ITU Global Cybersecurity Index 2024. Data passes through a call and is not kept after it.

**Can I start with read only?**

Yes. Enable the app for agents as read only, or make the API key read only, and anything that reaches other people waits for your OK unless you switch that off per tool.

**Is it reliable?**

Every Cotlet service is checked every 3 minutes from Europe, North America, Asia and Australia. The live results and any outage are public at status.cotlet.dev.

**How do I stop?**

Press Disable for agents next to Timetastic in your console: your agents lose access at once and you stay signed in. Signing out of Timetastic in the browser works too, and Reset browser deletes the whole profile.

## Is there a Timetastic MCP server on GitHub?

Yes. Community Timetastic MCP servers exist on GitHub, usually maintained by one person. You install one on your own computer, give it an admin API token and keep it running yourself; when the API changes, it stops working until you or the maintainer fix it. Cotlet hosts the same kind of server for you, works in your own account and also reads the app screens the API leaves out.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Install it, create an admin API token, add both to each MCP client | Sign up, sign in to Timetastic once, add one MCP server or API key |
| Account needed | An admin user, because only admins get a token | Your own account: an employee, manager, approver or admin, with that role's rights |
| When Timetastic changes | It breaks until you or the maintainer fix it | Automatic checks run against it and our team fixes it for you; failed calls are free |
| Your access | The token sits in a config file on your computer, readable by any program you run | Your session lives in your own Cloud Browser in the EU, encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Tools fail until an admin gives you a new token | Your Cloud Browser keeps you signed in; if Timetastic logs you out, your agent gets a link to sign in again |
| Where it runs | Your computer, while it is on | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Free, paid for with your time | Free 7-day trial, then pay-as-you-go credit packs, no subscription |

### Which one fits you

**Pick Cotlet if**

- you are not a developer, or you do not want to maintain a server
- you need it to keep working when Timetastic changes, without checking it yourself
- your agent or a script should run it on a schedule, also while your computer is off

**Pick an open-source server if**

- you are comfortable installing, updating and fixing it yourself
- you want your sign-in to stay on your own computer
- you only need it now and then, from one MCP client

## How much does the Timetastic API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Timetastic API is pay as you go with no limit on apps: Credit packs from $29 for 5,000 credits, one-time, no subscription. A successful call uses 20 to 30 credits (25 for most tools, about $0.10 to $0.15), your Cloud Browser uses 50 credits a day while it has an app enabled for agents, however many apps that is, and an agent driving the browser itself uses 5 credits a minute. Credit packs stay valid for 12 months and stack, so unused credits carry over.

| Credits | Price, one time | Calls at 25 credits | Per 1,000 credits |
|---|---|---|---|
| 5,000 | $29 | 200 | $5.80 |
| 15,000 | $79 | 600 | $5.27 |
| 32,000 | $149 | 1,280 | $4.66 |
| 60,000 | $249 | 2,400 | $4.15 |

Only successful calls use credits; failed calls and timeouts cost nothing. At a balance of 0 calls pause, never a surprise charge. Authenticate with the `Authorization: Bearer` header. [See full pricing](https://cotlet.dev/pricing.md)

## How Cotlet holds your access

Cotlet hosts MCP servers and REST APIs for apps with no usable API. Your agent works in your own Timetastic account.

- **Company details:** Cotlet is run by Take Group sp. z o.o., a company registered in Poland. Its full address and registration numbers are in the Terms of service. [Terms of service](https://cotlet.dev/terms)
- **Your sign-in:** You sign in to Timetastic yourself, in your own Cloud Browser: a Chrome we run for you in the EU, one per app. We never save your password (password saving is off), the profile is stored encrypted with AES-256-GCM, and your agents get Timetastic only after you enable it. When Timetastic signs you out, your agent gives you a link to sign in again. [Security](https://cotlet.dev/security.md)
- **Revoking access:** Press Disable for agents next to Timetastic, sign out of Timetastic in your Cloud Browser, or reset the browser. Every background request is listed in your Background activity. Actions that reach other people wait for your OK unless you switch that off per tool.
- **What we never do:** Store passwords, solve CAPTCHAs or bypass MFA.
- **Timetastic's terms:** You use your own Timetastic account and stay responsible for following Timetastic's terms. Cotlet is independent and not affiliated with Timetastic. [Terms](https://cotlet.dev/terms)
- **Contact:** Questions about the company, security or an app: [contact@cotlet.dev](mailto:contact@cotlet.dev)

## Frequently asked questions

**How do I get access?**

Sign up free, open Timetastic in the console and press Request access. Then you create your API key and connect Timetastic there.

**Do I need to be technical?**

No. You sign in to Timetastic once in your Cloud Browser, a normal Chrome you open from the console, and paste one command into your agent, or one URL into n8n. Your agent can walk you through it. There is no server to install, update or fix.

**Is it safe to connect Timetastic to Cotlet?**

Yes. You sign in to Timetastic yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Timetastic once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

**Is a hosted server safer than a local one? My Timetastic sign-in would leave my computer.**

On Cotlet you sign in inside your own Cloud Browser, which only you open, and its profile is stored encrypted with AES-256-GCM in the EU. Agents get only the apps you enable, and every background request is listed. A local server keeps your Timetastic cookie in a plain file on your computer, readable by any program you run, and stops when your computer is off.

**Why does Cotlet send requests instead of clicking in my browser?**

To be fast, Cotlet doesn't click through Timetastic's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Timetastic sees the same browser and IP you signed in with, and every request is listed in your Background activity.

**What if someone gets my Cotlet API key?**

The key holds no Timetastic login or cookies, it only asks Cotlet to run a tool. It can call only the apps and tools you gave it, and a read-only key changes nothing. Anything that reaches other people, like posts, comments or messages, waits for your OK in the dashboard by default, so a leaked key cannot post or message as you. When you switch approval off for a scheduled job, give that job its own key limited to that one tool. Every call is in your activity log, and deleting the key ends access at once.

**Why a signed-in browser and not OAuth, like other integration platforms?**

Timetastic offers no OAuth token you can simply grant for these tools: its official API leaves them out or needs a developer app, a plan or an approval first (see the official API section above). That is why Cotlet sets the limits itself: per key, per tool, with your approval before anything reaches other people. Cotlet is run by Take Group sp. z o.o., an EU company (VAT PL6342984273).

**Do I need to be a Timetastic admin?**

No. Timetastic gives an API token only to admin users, while Cotlet works in your own account with your own role (source: Timetastic Help, Timetastic API). An approver approves, an employee books their own leave, and the reports need an account that can open Settings > Reporting & Backup.

**Can my agent override a staffing limit?**

Only when you allow it. A department's Maximum absent limit blocks an employee booking for themselves, and shows a manager or admin a warning they can override with Confirm (source: Timetastic Help, Maximum absent). book_time_off stops at that warning unless confirm_override is true.

**Can my agent post or send messages in Timetastic without asking me?**

No. Every call to book_time_off, approve_request, decline_request or cancel_booking waits for your OK by default. For scheduled automations you can switch confirmation off per tool in your dashboard, for example only for approvals.

**Can I use the Timetastic API in n8n?**

Yes. Add https://cotlet.dev/mcp/v1 with your API key in n8n's MCP Client node, or call its endpoints under https://cotlet.dev/api/v1/timetastic from the HTTP Request node.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.