[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)

# Shiftbase API and MCP server

> Shiftbase has a Public API for employees, schedules, time registration, clocks and reports, but no official MCP server (checked 22 Oct 2026). An admin installs the Public API tile in the App center to get a token, and every integration is code you write and run yourself.

Workforce software for shift-based teams: a schedule, a timesheet with clocking, absence and leave, employee records and reports in one account.

## What is the Shiftbase API?

Cotlet's Shiftbase API exposes 13 endpoints for your own Shiftbase account: list departments, list employees, list shifts, list open shifts, list timesheet entries, list absence requests, list shift exchange requests, add worked hours, set timesheet status, approve absence request, decline absence request, approve shift exchange and decline shift exchange. The list_departments endpoint returns list the departments and teams of the account. Each endpoint takes simple JSON inputs like department_id, request_id or from and works both as an operation of the shiftbase_read or shiftbase_write MCP tool for agents and as a REST call for scripts.

- **Category:** [HR & recruiting](https://cotlet.dev/integrations/category/hr-recruiting.md)
- **Endpoints:** 13 (7 read, 6 write)
- **Updated:** 2026-10-19

Shiftbase has a Public API for employees, schedules, time registration, clocks and reports, but no official MCP server (checked 22 Oct 2026). Cotlet is a hosted MCP server and REST API for Shiftbase with 13 endpoints (7 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Shiftbase have an official API?

Shiftbase has a Public API for employees, schedules, time registration, clocks and reports, but no official MCP server (checked 22 Oct 2026). An admin installs the Public API tile in the App center to get a token, and every integration is code you write and run yourself.

| Task | Shiftbase official | Cotlet |
|---|---|---|
| List employees and contracts | Yes: Employee data is among the API examples Shiftbase lists | Yes |
| List shifts and the schedule | Yes: Work schedule data is among the API examples | Yes |
| List and add timesheet entries | Yes: Time registration data and clocks are among the API examples | Yes |
| Approve or decline timesheet entries | Partly: Not named in the API examples Shiftbase lists | Yes |
| List absence requests | Yes: Absence and leave are among the API examples | Yes |
| Approve or decline absence requests | Partly: Not named in the API examples Shiftbase lists | Yes |
| Approve shift exchange requests | Partly: Not named in the API examples Shiftbase lists | Yes |
| Read open shifts | Yes: Open services are among the schedule examples | Yes |

Sources: [Shiftbase Help: Full API access](https://help.shiftbase.com/full-api-access), [Shiftbase developer docs](https://developer.shiftbase.com/docs/core/59f133358c1fd-shiftbase-api), [Shiftbase: build on the API as a technology partner](https://www.shiftbase.com/partners/technology-partner)

## For AI agents

```text
Shiftbase has a Public API for employees, schedules, time registration, clocks and reports, but no official MCP server (checked 22 Oct 2026). An admin installs the Public API tile in the App center to get a token, and every integration is code you write and run yourself.
Cotlet provides a hosted MCP server and REST API for Shiftbase: 13 tools (7 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=shiftbase, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    shiftbase_read, shiftbase_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/shiftbase, each operation at its own route, e.g. PUT /api/v1/shiftbase/timesheet-status
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_departments, list_employees, list_shifts, list_open_shifts, list_timesheet_entries, list_absence_requests, list_exchange_requests, add_worked_hours, set_timesheet_status, approve_absence_request, decline_absence_request, approve_exchange_request, decline_exchange_request
Confirm      add_worked_hours, set_timesheet_status, approve_absence_request, decline_absence_request, approve_exchange_request, decline_exchange_request (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/shiftbase-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=shiftbase, requests Shiftbase in the Cotlet console and creates an API key there.
2. The user signs in to Shiftbase once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Shiftbase 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 Shiftbase server that someone else maintains, including non-developers.

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 Shiftbase 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 Shiftbase 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 Shiftbase 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 Shiftbase's terms; Cotlet is not affiliated with Shiftbase.
```

## What can an AI agent do in Shiftbase?

Cotlet is best for Shiftbase planners and managers who want an agent to approve hours, leave and shift swaps without running or fixing a server.

- **[Approve pending timesheets](https://cotlet.dev/integrations/shiftbase-api-mcp-server/approve-pending-timesheets.md)** (runs: weekly): "List the pending timesheet entries for last week in Harbor Cafe. Approve the ones without conflicts and send me the rest with the reason." → `list_timesheet_entries`, `set_timesheet_status`
- **[Approve leave requests that fit the rota](https://cotlet.dev/integrations/shiftbase-api-mcp-server/approve-leave-requests.md)** (runs: daily): "Check the pending absence requests in Harbor Cafe. Approve a request if at least 3 colleagues stay on shift every day of it, decline the rest with a short note, and tell me which ones you declined." → `list_absence_requests`, `list_shifts`, `approve_absence_request`, `decline_absence_request`
- **[Approve shift exchange requests](https://cotlet.dev/integrations/shiftbase-api-mcp-server/approve-shift-exchanges.md)** (runs: daily): "List the shift exchanges in Harbor Cafe that a colleague has accepted. Approve the ones where both people are allowed to work the shift and nobody goes over 40 hours that week, and list the rest." → `list_exchange_requests`, `list_shifts`, `approve_exchange_request`, `decline_exchange_request`
- **Report open shifts nobody took** (runs: weekly): "List the open shifts in Harbor Cafe for next week that nobody applied for, and show who has no shift on those days." → `list_open_shifts`, `list_employees`
- **Add hours for a missed clock-out** (runs: daily): "Find yesterday's clocked entries in Harbor Cafe with no end time and add the scheduled end for each employee." → `list_timesheet_entries`, `add_worked_hours`

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

Yes. Cotlet does not replace your automation platform: it gives it a Shiftbase 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 pending timesheets, 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/shiftbase/timesheet-entries. | 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/shiftbase/timesheet-entries with your API key. | cron or GitHub Actions. |

## Tools

**For AI agents:** Every endpoint and its schema is public. The 13 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 Shiftbase.

### list_departments

List the departments and teams of the account. Access: read. REST: `GET /api/v1/shiftbase/departments`. MCP: `shiftbase_read → list_departments`.

No parameters.

Returns each department with its id and the teams in it. Use the ids to filter the other tools. An account sees only the departments its role can open.

Example response:

```json
{
  "departments": [
    {
      "id": "12",
      "name": "Harbor Cafe",
      "teams": [
        {
          "id": "31",
          "name": "Kitchen"
        },
        {
          "id": "32",
          "name": "Floor"
        }
      ]
    }
  ]
}
```

### list_employees

List employees, with their department and contract type. Access: read. REST: `GET /api/v1/shiftbase/employees`. MCP: `shiftbase_read → list_employees`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `department_id` | string | no | Only employees of this department. |
| `query` | string | no | Part of a name. |

Returns the employee id, name, department and contract type. Which employees appear depends on the departments your role can open.

Example response:

```json
{
  "employees": [
    {
      "id": "501",
      "name": "Lena Ortiz",
      "department": "Harbor Cafe",
      "contract_type": "Part-time"
    },
    {
      "id": "502",
      "name": "Sam Okafor",
      "department": "Harbor Cafe",
      "contract_type": "Full-time"
    }
  ]
}
```

### list_shifts

List scheduled shifts for a date range. Access: read. REST: `GET /api/v1/shiftbase/shifts`. MCP: `shiftbase_read → list_shifts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | string | yes | First day, YYYY-MM-DD. |
| `to` | string | yes | Last day, YYYY-MM-DD. |
| `department_id` | string | no | Only this department. |
| `employee_id` | string | no | Only this employee. |

Returns each shift with its date, start, end, team and employee, in date order. Open shifts have no employee. It reads the schedule as the account sees it.

Example response:

```json
{
  "shifts": [
    {
      "id": "90421",
      "date": "2026-10-25",
      "start": "16:00",
      "end": "23:00",
      "team": "Floor",
      "employee": "Lena Ortiz"
    },
    {
      "id": "90433",
      "date": "2026-10-25",
      "start": "10:00",
      "end": "18:00",
      "team": "Kitchen",
      "employee": "Sam Okafor"
    }
  ]
}
```

### list_open_shifts

List open shifts that no employee holds yet. Access: read. REST: `GET /api/v1/shiftbase/open-shifts`. MCP: `shiftbase_read → list_open_shifts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | string | yes | First day, YYYY-MM-DD. |
| `to` | string | yes | Last day, YYYY-MM-DD. |
| `department_id` | string | no | Only this department. |

Returns the open shifts with date, times, team and the employees who applied. An empty applicants list means nobody has asked for the shift. Shifts opened by an approved absence appear here too.

Example response:

```json
{
  "open_shifts": [
    {
      "id": "90512",
      "date": "2026-11-04",
      "start": "09:00",
      "end": "15:00",
      "team": "Kitchen",
      "applicants": []
    }
  ]
}
```

### list_timesheet_entries

List worked hours from the Timesheet tab. Access: read. REST: `GET /api/v1/shiftbase/timesheet-entries`. MCP: `shiftbase_read → list_timesheet_entries`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `from` | string | yes | First day, YYYY-MM-DD. |
| `to` | string | yes | Last day, YYYY-MM-DD. |
| `status` | string | no | One of pending, approved, declined. |
| `department_id` | string | no | Only this department. |
| `conflicts_only` | boolean | no | Only entries Shiftbase flags as conflicts. |

Returns each entry with employee, date, start, end, breaks, hours and status, oldest first. It reads the same list as the Timesheet tab with the same filters. Entries of departments your role cannot open are not returned.

Example response:

```json
{
  "entries": [
    {
      "id": "40118",
      "employee": "Lena Ortiz",
      "date": "2026-10-14",
      "start": "09:00",
      "end": "17:00",
      "unpaid_break_min": 30,
      "hours": 7.5,
      "status": "pending",
      "conflict": false
    },
    {
      "id": "40122",
      "employee": "Sam Okafor",
      "date": "2026-10-18",
      "start": "08:00",
      "end": "19:00",
      "unpaid_break_min": 30,
      "hours": 10.5,
      "status": "pending",
      "conflict": true
    }
  ]
}
```

### list_absence_requests

List absence and leave requests. Access: read. REST: `GET /api/v1/shiftbase/absence-requests`. MCP: `shiftbase_read → list_absence_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `status` | string | no | One of pending, approved, declined. |
| `department_id` | string | no | Only this department. |

Returns each request with employee, dates, absence policy and status, oldest first. Without a status it returns the requests that still wait for a decision. Which requests appear depends on the departments your role can open.

Example response:

```json
{
  "requests": [
    {
      "id": "7731",
      "employee": "Lena Ortiz",
      "department": "Harbor Cafe",
      "from": "2026-11-03",
      "to": "2026-11-07",
      "policy": "Holiday",
      "status": "pending"
    }
  ]
}
```

### list_exchange_requests

List shift exchanges that wait for approval. Access: read. REST: `GET /api/v1/shiftbase/exchange-requests`. MCP: `shiftbase_read → list_exchange_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `department_id` | string | no | Only this department. |

Returns exchanges where a colleague has accepted the shift and a manager still has to decide. Each has the shift, the original owner and the colleague. Offers nobody accepted are left out. Only a user with the Approve exchanges permission sees them.

Example response:

```json
{
  "exchanges": [
    {
      "id": "2290",
      "shift_id": "90421",
      "date": "2026-10-25",
      "start": "16:00",
      "end": "23:00",
      "from_employee": "Lena Ortiz",
      "to_employee": "Sam Okafor"
    }
  ]
}
```

### add_worked_hours

Add a timesheet entry for an employee. Access: write, asks the user first. REST: `POST /api/v1/shiftbase/employees/{employee_id}/worked-hours`. MCP: `shiftbase_write → add_worked_hours`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `employee_id` | string | yes | Employee id from list_employees. |
| `date` | string | yes | Day of the shift, YYYY-MM-DD. |
| `start` | string | yes | Start time, HH:MM. |
| `end` | string | yes | End time, HH:MM. |
| `unpaid_break_min` | number | no | Unpaid break in minutes. It is not counted as worked time. |
| `note` | string | no | Note on the shift. |
| `notify_employee` | boolean | no | Send the employee a notification about the entry. |

Creates one entry in the Timesheet tab with status pending and returns its id and hours. It uses the department and shift of the employee for that day. With notify_employee set, the employee gets a message. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "entry_id": "40130",
  "employee": "Lena Ortiz",
  "date": "2026-10-21",
  "start": "09:00",
  "end": "17:00",
  "hours": 7.5,
  "status": "pending"
}
```

### set_timesheet_status

Approve, decline or restore timesheet entries to pending. Access: write, asks the user first. REST: `PUT /api/v1/shiftbase/timesheet-status`. MCP: `shiftbase_write → set_timesheet_status`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `entry_ids` | array | yes | Entry ids from list_timesheet_entries. |
| `status` | string | yes | One of approved, declined, pending. |

Changes the status of every listed entry and returns the new status of each. Approved hours go on to the payroll report. A closed timesheet period rejects the change. Your role needs the right to approve hours. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "updated": [
    {
      "id": "40118",
      "status": "approved"
    },
    {
      "id": "40119",
      "status": "approved"
    },
    {
      "id": "40122",
      "status": "approved"
    }
  ]
}
```

### approve_absence_request

Approve a pending absence or leave request. Access: write, asks the user first. REST: `POST /api/v1/shiftbase/requests/{request_id}/absence-request/approve`. MCP: `shiftbase_write → approve_absence_request`.

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

Approves the request and returns its new status and the shifts the absence policy changed in that period. The policy decides whether those shifts are removed, kept or opened. The employee is notified by Shiftbase. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "7731",
  "status": "approved",
  "affected_shifts": [
    {
      "id": "90455",
      "date": "2026-11-04",
      "result": "opened"
    },
    {
      "id": "90460",
      "date": "2026-11-06",
      "result": "opened"
    }
  ]
}
```

### decline_absence_request

Decline a pending absence or leave request. Access: write, asks the user first. REST: `POST /api/v1/shiftbase/requests/{request_id}/absence-request/decline`. MCP: `shiftbase_write → decline_absence_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_id` | string | yes | Request id from list_absence_requests. |
| `note` | string | no | Reason shown to the employee. |

Declines the request and returns its status. The schedule does not change. The employee is notified by Shiftbase. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "7732",
  "status": "declined"
}
```

### approve_exchange_request

Approve an accepted shift exchange. Access: write, asks the user first. REST: `POST /api/v1/shiftbase/requests/{request_id}/exchange-request/approve`. MCP: `shiftbase_write → approve_exchange_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_id` | string | yes | Exchange id from list_exchange_requests. |

Moves the shift to the colleague who accepted it and returns the shift with its new owner. Your role needs the Approve exchanges permission. Both employees are notified. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "2290",
  "status": "approved",
  "shift": {
    "id": "90421",
    "date": "2026-10-25",
    "start": "16:00",
    "end": "23:00",
    "employee": "Sam Okafor"
  }
}
```

### decline_exchange_request

Decline an accepted shift exchange. Access: write, asks the user first. REST: `POST /api/v1/shiftbase/requests/{request_id}/exchange-request/decline`. MCP: `shiftbase_write → decline_exchange_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `request_id` | string | yes | Exchange id from list_exchange_requests. |

Rejects the exchange and leaves the shift with its original owner. Both employees are notified. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "request_id": "2291",
  "status": "declined"
}
```

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

Connecting Shiftbase takes three steps: sign up, sign in to Shiftbase 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 Shiftbase to your agent.

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

2. **Sign in to Shiftbase in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Shiftbase 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 Shiftbase 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.

```
List the pending timesheet entries for last week in Harbor Cafe. Approve the ones without conflicts and send me the rest with the reason.
```

### Call Shiftbase 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/shiftbase 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 PUT https://cotlet.dev/api/v1/shiftbase/timesheet-status \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"entry_ids":["40118","40119","40122"],"status":"approved"}'
```

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

```
{
  "updated": [
    {
      "id": "40118",
      "status": "approved"
    },
    {
      "id": "40119",
      "status": "approved"
    },
    {
      "id": "40122",
      "status": "approved"
    }
  ]
}
```

## Why use Cotlet for Shiftbase?

**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 Shiftbase 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 Shiftbase changes, the tool pauses until we fix it.
- Failed calls cost nothing.

## Is it safe to connect Shiftbase to Cotlet?

Yes. You sign in to Shiftbase yourself, in your own Cloud Browser, and we never save your password. Your agents only get Shiftbase 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 Shiftbase integration?**

No, Cotlet is independent of Shiftbase. Shiftbase's own API is too limited for this work. Cotlet works through your own Shiftbase account, the way you use Shiftbase 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 Shiftbase in your console: your agents lose access at once and you stay signed in. Signing out of Shiftbase in the browser works too, and Reset browser deletes the whole profile.

## Is there a Shiftbase MCP server on GitHub?

The direct route is the Shiftbase Public API. An admin creates a token in the App center, and you write and host the code that calls it. Cotlet needs no token and no code: you sign in to Shiftbase once and your agent uses the same screens you do.

|  | Shiftbase API | Cotlet |
|---|---|---|
| Setup | Install the Public API tile in Settings > App center, name a token, write the calls | Sign up, sign in to Shiftbase once, add one MCP server or API key |
| When Shiftbase changes | The API is documented and versioned; your code is yours to update | Our team tests it daily and fixes it for you; failed calls are free |
| Your Shiftbase access | A token you store and rotate yourself | A session in your own Cloud Browser in the EU, encrypted, only for the apps you enable, disabled for agents in one click |
| When access expires | Calls fail until you issue a new token | If Shiftbase logs you out, your agent gets a link to sign in again |
| Upkeep | You host, monitor and debug the code | Nothing to host or update |
| Where it runs | Wherever you deploy your code | Hosted: Claude Code, Codex, Cursor, n8n and scripts, also on a schedule |
| Price | Your developer time to write and run the code | 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 Shiftbase 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 Shiftbase API cost?

Free 7-day trial with 2,000 credits, no card needed. After that, the Shiftbase 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 Shiftbase 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 Shiftbase 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 Shiftbase only after you enable it. When Shiftbase 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 Shiftbase, sign out of Shiftbase 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.
- **Shiftbase's terms:** You use your own Shiftbase account and stay responsible for following Shiftbase's terms. Cotlet is independent and not affiliated with Shiftbase. [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 Shiftbase in the console and press Request access. Then you create your API key and connect Shiftbase there.

**Do I need to be technical?**

No. You sign in to Shiftbase 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 Shiftbase to Cotlet?**

Yes. You sign in to Shiftbase yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Shiftbase 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 Shiftbase 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 Shiftbase 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 Shiftbase's pages. It sends the same requests your browser would, from your browser's IP with its cookies, without opening a window. Shiftbase 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 Shiftbase 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?**

Shiftbase 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).

**Which Shiftbase role does my agent need?**

The role you sign in with. Approving hours needs the right to approve in the Timesheet tab, approving exchanges needs the Approve exchanges permission (the Planner has it by default), and Planners can approve absence requests. A call without the right fails with a permission error.

**Does Cotlet need the Shiftbase Public API token?**

No. The Public API needs a token that an admin installs from Settings > App center > Public API. Cotlet works in your signed-in account instead, so no token is created or stored.

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

No. Every call to add_worked_hours, set_timesheet_status, approve_absence_request, decline_absence_request, approve_exchange_request or decline_exchange_request 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 Shiftbase 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/shiftbase 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.