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

# Deputy API and MCP server

> Yes, Deputy has a full REST API, but no official MCP server (checked 20 Oct 2026). Deputy says its API covers nearly all objects and actions and is included in all plans, so an agent needs your own code, an OAuth client and a token for your install.

Workforce management app for shift businesses: rosters, timesheets, leave and team communication in one place for each location.

## What is the Deputy API?

Cotlet's Deputy API exposes 12 endpoints for your own Deputy account: list locations, list employees, list shifts, list timesheets, get a timesheet, list leave requests, create a draft shift, publish draft shifts, approve a timesheet, discard a timesheet, approve a leave request and decline a leave request. The list_locations endpoint returns locations of your Deputy install with their IDs. Each endpoint takes simple JSON inputs like location_id, date_from or date_to and works both as an operation of the deputy_read or deputy_write MCP tool for agents and as a REST call for scripts.

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

Yes, Deputy has a full REST API, but no official MCP server (checked 20 Oct 2026). Cotlet is a hosted MCP server and REST API for Deputy with 12 endpoints (6 read, 6 write): you sign in once in your own cloud browser, your AI agent does the work.

## Does Deputy have an official API?

Yes, Deputy has a full REST API, but no official MCP server (checked 20 Oct 2026). Deputy says its API covers nearly all objects and actions and is included in all plans, so an agent needs your own code, an OAuth client and a token for your install.

| Task | Deputy official | Cotlet |
|---|---|---|
| List timesheets and read one | Yes: Resource API, Timesheet | Yes |
| Approve or discard a timesheet | Yes: Timesheet management calls | Yes |
| List leave requests | Yes: Resource API, Leave | Yes |
| Approve or decline a leave request | Yes: Update on the Leave resource; you work out the hours of each day yourself | Yes |
| List shifts and employees | Yes | Yes |
| Create a draft shift and publish rosters | Yes: Shifts can be draft, open or published | Yes |
| Use Deputy from an AI agent without code | No: No official MCP server | Yes |

Sources: [Deputy Developer: Getting Started with the Deputy API](https://developer.deputy.com/docs/getting-started-with-the-deputy-api), [Deputy Developer: Integration and Data Availability Options](https://developer.deputy.com/docs/integration-and-data-availability-options), [Deputy Developer: Using OAuth 2.0](https://developer.deputy.com/docs/using-oauth-20), [Deputy Developer: Timesheet Management Calls](https://developer.deputy.com/docs/timesheet-management-calls)

## For AI agents

```text
Yes, Deputy has a full REST API, but no official MCP server (checked 20 Oct 2026). Deputy says its API covers nearly all objects and actions and is included in all plans, so an agent needs your own code, an OAuth client and a token for your install.
Cotlet provides a hosted MCP server and REST API for Deputy: 12 tools (6 read, 6 write).
Access       Sign up at https://cotlet.dev/app/signup?app=deputy, then request the app and create API keys in the Cotlet console.

MCP server   https://cotlet.dev/mcp/v1
MCP tools    deputy_read, deputy_write, reads and writes apart; call one with {"operation": "<operation>", "arguments": {...}}
REST base    https://cotlet.dev/api/v1/deputy, each operation at its own route, e.g. POST /api/v1/deputy/timesheets/{timesheet_id}/approve
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_locations, list_employees, list_shifts, list_timesheets, get_timesheet, list_leave_requests, create_shift, publish_shifts, approve_timesheet, discard_timesheet, approve_leave_request, decline_leave_request
Confirm      create_shift, publish_shifts, approve_timesheet, discard_timesheet, approve_leave_request, decline_leave_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/deputy-api-mcp-server.md

How access works:
1. The user signs up at https://cotlet.dev/app/signup?app=deputy, requests Deputy in the Cotlet console and creates an API key there.
2. The user signs in to Deputy once in their Cotlet Cloud Browser (their own Chrome in the cloud, opened from the console) and enables Deputy 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 Deputy 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 Deputy 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 Deputy 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 Deputy 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 Deputy 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 Deputy's terms; Cotlet is not affiliated with Deputy.
```

## What can an AI agent do in Deputy?

Cotlet is best for Deputy managers who want their AI agent to approve timesheets, decide leave and draft rosters without running or fixing a server.

- **[Approve timesheets in bulk](https://cotlet.dev/integrations/deputy-api-mcp-server/approve-timesheets-in-bulk.md)** (runs: daily): "List pending timesheets at Harbour Cafe, oldest first. Approve the ones that match their roster within 15 minutes, discard shifts nobody worked, and leave the rest for me with a reason." → `list_timesheets`, `get_timesheet`, `approve_timesheet`, `discard_timesheet`
- **[Decide leave requests by rule](https://cotlet.dev/integrations/deputy-api-mcp-server/approve-leave-requests.md)** (runs: daily): "Go through pending leave requests. Approve annual leave for at least 14 days ahead when no more than one person at the location is off, decline the rest with a reason and tell me which ones." → `list_leave_requests`, `list_shifts`, `approve_leave_request`, `decline_leave_request`
- **Draft next week's roster and publish it** (runs: weekly): "Draft next week's shifts at Harbour Cafe like this week's, skip anyone on approved leave, show me the draft, then publish it when I say so." → `list_employees`, `list_shifts`, `create_shift`, `publish_shifts`
- **Weekly timesheet exceptions report** (runs: weekly): "Every Monday, list last week's timesheets with no end time or a break shorter than rostered, by location." → `list_locations`, `list_timesheets`, `get_timesheet`

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

Yes. Cotlet does not replace your automation platform: it gives it a Deputy 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 timesheets in bulk, 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/deputy/locations/{location_id}/timesheets. | 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/deputy/locations/{location_id}/timesheets with your API key. | cron or GitHub Actions. |

## Tools

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

### list_locations

Locations of your Deputy install with their IDs. Access: read. REST: `GET /api/v1/deputy/locations`. MCP: `deputy_read → list_locations`.

No parameters.

Returns every location your account can see, with the location_id the other tools take. Run it first when the prompt names a location by its name. A location is the business site a team works at.

Example response:

```json
{
  "locations": [
    {
      "location_id": 1,
      "name": "Harbour Cafe"
    },
    {
      "location_id": 2,
      "name": "Harbour Bakery"
    }
  ]
}
```

### list_employees

Team members of a location with their IDs. Access: read. REST: `GET /api/v1/deputy/employees`. MCP: `deputy_read → list_employees`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | integer | no | Location ID from list_locations. Default: all your locations. |
| `search` | string | no | Part of the name to match. |

Returns team members of one location, or of all your locations when location_id is omitted, with the employee_id other tools take. Terminated employees are left out.

Example response:

```json
{
  "employees": [
    {
      "employee_id": 3,
      "name": "Ana Lopez",
      "location_id": 1
    },
    {
      "employee_id": 4,
      "name": "Tom Becker",
      "location_id": 1
    }
  ]
}
```

### list_shifts

Shifts of a location between two dates, draft, open and published. Access: read. REST: `GET /api/v1/deputy/locations/{location_id}/shifts`. MCP: `deputy_read → list_shifts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | integer | yes | Location ID from list_locations. |
| `date_from` | date | yes | First day, YYYY-MM-DD. |
| `date_to` | date | yes | Last day, YYYY-MM-DD. |
| `employee_id` | integer | no | Only this employee's shifts. |

Returns shifts (Deputy calls them rosters) of one location between two dates, in start order. Each shift says whether it is published, open (no employee yet) or a draft only managers see. Without dates, Deputy returns its default window around now, so pass both dates to read a week.

Example response:

```json
{
  "shifts": [
    {
      "shift_id": 714,
      "date": "2026-10-19",
      "start": "09:00",
      "end": "17:00",
      "employee": "Ana Lopez",
      "state": "published"
    },
    {
      "shift_id": 715,
      "date": "2026-10-19",
      "start": "12:00",
      "end": "20:00",
      "employee": null,
      "state": "open"
    }
  ]
}
```

### list_timesheets

Timesheets of a location, oldest first, pending or approved. Access: read. REST: `GET /api/v1/deputy/locations/{location_id}/timesheets`. MCP: `deputy_read → list_timesheets`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | integer | yes | Location ID from list_locations. |
| `status` | enum | no | pending (default) or approved. |
| `date_from` | date | no | First day, YYYY-MM-DD. |
| `date_to` | date | no | Last day, YYYY-MM-DD. |
| `employee_id` | integer | no | Only this employee's timesheets. |

Returns timesheets of one location in date order, oldest first, the order Deputy recommends for approval. status pending (default) lists those waiting for approval, approved lists the done ones. Each row has start, end and break, and a missing end time is shown as null. Pay figures need the Location Manager or System Administrator role.

Example response:

```json
{
  "timesheets": [
    {
      "timesheet_id": 4821,
      "employee": "Ana Lopez",
      "date": "2026-10-12",
      "start": "09:00",
      "end": "17:30",
      "break_minutes": 30,
      "hours": 8,
      "status": "pending"
    },
    {
      "timesheet_id": 4822,
      "employee": "Tom Becker",
      "date": "2026-10-12",
      "start": "10:00",
      "end": null,
      "break_minutes": 0,
      "hours": null,
      "status": "pending"
    }
  ]
}
```

### get_timesheet

One timesheet with its break, comment and the shift it belongs to. Access: read. REST: `GET /api/v1/deputy/timesheets/{timesheet_id}`. MCP: `deputy_read → get_timesheet`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `timesheet_id` | integer | yes | Timesheet ID from list_timesheets. |

Returns one timesheet with its start, end, break, comment and the scheduled shift next to it, so you can compare worked and rostered time. An unsubmitted timesheet, where nobody clocked in, comes back with no start.

Example response:

```json
{
  "timesheet_id": 4821,
  "employee": "Ana Lopez",
  "date": "2026-10-12",
  "start": "09:00",
  "end": "17:30",
  "break_minutes": 30,
  "hours": 8,
  "comment": null,
  "status": "pending",
  "rostered": {
    "start": "09:00",
    "end": "17:30"
  }
}
```

### list_leave_requests

Pending leave requests with employee, dates, leave type and comment. Access: read. REST: `GET /api/v1/deputy/leave-requests`. MCP: `deputy_read → list_leave_requests`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | integer | no | Location ID from list_locations. Default: all your locations. |
| `status` | enum | no | pending (default), approved or declined. |

Returns leave requests waiting for a decision, oldest first, with the employee, the first and last day, the leave type the employee picked and their comment. The leave type is only a suggestion. status approved or declined lists decided requests instead.

Example response:

```json
{
  "leave_requests": [
    {
      "leave_id": 311,
      "employee": "Tom Becker",
      "date_start": "2026-11-03",
      "date_end": "2026-11-04",
      "leave_type": "Annual leave",
      "comment": "Family trip",
      "status": "pending"
    }
  ]
}
```

### create_shift

Add a shift to a location as a draft that only managers see. Access: write, asks the user first. REST: `POST /api/v1/deputy/locations/{location_id}/shifts`. MCP: `deputy_write → create_shift`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | integer | yes | Location ID from list_locations. |
| `date` | date | yes | Day of the shift, YYYY-MM-DD. |
| `start` | string | yes | Start time, HH:MM. |
| `end` | string | yes | End time, HH:MM. |
| `employee_id` | integer | no | Employee ID from list_employees. Default: open shift. |

Adds one shift as a draft, so it shows to managers and not to the team until publish_shifts runs. Leave employee_id out to create an open shift. Returns the shift_id. It never notifies anyone. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "shift_id": 733,
  "date": "2026-10-26",
  "start": "09:00",
  "end": "17:00",
  "employee": "Ana Lopez",
  "state": "draft"
}
```

### publish_shifts

Publish the draft shifts of a location between two dates to the team. Access: write, asks the user first. REST: `POST /api/v1/deputy/locations/{location_id}/shifts/publish`. MCP: `deputy_write → publish_shifts`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `location_id` | integer | yes | Location ID from list_locations. |
| `date_from` | date | yes | First day, YYYY-MM-DD. |
| `date_to` | date | yes | Last day, YYYY-MM-DD. |

Publishes every draft shift of one location between two dates, so the team sees them. Returns how many were published. Employees may be notified by Deputy, so it waits for you. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "published": 12,
  "location_id": 1,
  "date_from": "2026-10-26",
  "date_to": "2026-11-01"
}
```

### approve_timesheet

Approve one pending timesheet. Access: write, asks the user first. REST: `POST /api/v1/deputy/timesheets/{timesheet_id}/approve`. MCP: `deputy_write → approve_timesheet`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `timesheet_id` | integer | yes | Timesheet ID from list_timesheets. |

Approves one pending timesheet, which then follows Deputy's payment workflow. Needs the Location Manager or System Administrator role for the pay part. A timesheet with no end time is refused; fix it in Deputy first. Cotlet has no unapprove tool, because Deputy unapproves only in its web app. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "timesheet_id": 4821,
  "employee": "Ana Lopez",
  "date": "2026-10-12",
  "start": "09:00",
  "end": "17:30",
  "break_minutes": 30,
  "hours": 8,
  "status": "approved"
}
```

### discard_timesheet

Discard a timesheet for a shift that was not worked. Access: write, asks the user first. REST: `POST /api/v1/deputy/timesheets/{timesheet_id}/discard`. MCP: `deputy_write → discard_timesheet`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `timesheet_id` | integer | yes | Timesheet ID from list_timesheets. |

Discards one timesheet, for example an unsubmitted one where the shift was not worked. The employee's pay for that shift is not created. It affects pay, so it waits for you. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "timesheet_id": 4830,
  "employee": "Sam Okafor",
  "date": "2026-10-11",
  "status": "discarded"
}
```

### approve_leave_request

Approve a pending leave request and set the hours of each day. Access: write, asks the user first. REST: `POST /api/v1/deputy/leaves/{leave_id}/request/approve`. MCP: `deputy_write → approve_leave_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `leave_id` | integer | yes | Leave ID from list_leave_requests. |
| `day_type` | enum | yes | standard_hours, scheduled_hours or non_working_day, applied to every day of the request. |
| `leave_type` | string | no | Leave type name as shown in Deputy. Default: the type the employee picked. |
| `comment` | string | no | Comment the employee sees. |

Approves one leave request. day_type sets every day: standard_hours, scheduled_hours or non_working_day, matching Deputy's Standard hours, Scheduled hours and Non-working day. leave_type changes the type the employee suggested. For past dates Deputy creates the timesheets at once, for future dates as each day passes. The employee is told. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "leave_id": 311,
  "employee": "Tom Becker",
  "status": "approved",
  "leave_type": "Annual leave",
  "day_type": "standard_hours",
  "days": [
    "2026-11-03",
    "2026-11-04"
  ],
  "comment": "Approved, enjoy the break."
}
```

### decline_leave_request

Decline a pending leave request with a reason. Access: write, asks the user first. REST: `POST /api/v1/deputy/leaves/{leave_id}/request/decline`. MCP: `deputy_write → decline_leave_request`.

| Parameter | Type | Required | Description |
|---|---|---|---|
| `leave_id` | integer | yes | Leave ID from list_leave_requests. |
| `comment` | string | yes | Reason the employee sees. |

Declines one leave request. The comment is required, because Deputy requires one to decline, and the employee reads it. The decision reaches the employee, so it waits for you. By default you confirm each call; you can switch that off for this tool.

Example response:

```json
{
  "leave_id": 312,
  "employee": "Ana Lopez",
  "status": "declined",
  "comment": "Two others are off on Nov 10. Could you move it by a day?"
}
```

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

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

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

2. **Sign in to Deputy in your Cloud Browser** Open your Cloud Browser in the console: your own Chrome in the cloud. Sign in to Deputy 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 Deputy 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 pending timesheets at Harbour Cafe, oldest first. Approve the ones that match their roster within 15 minutes, discard shifts nobody worked, and leave the rest for me with a reason.
```

### Call Deputy 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/deputy 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/deputy/timesheets/4821/approve \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

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

```
{
  "timesheet_id": 4821,
  "employee": "Ana Lopez",
  "date": "2026-10-12",
  "start": "09:00",
  "end": "17:30",
  "break_minutes": 30,
  "hours": 8,
  "status": "approved"
}
```

## Why use Cotlet for Deputy?

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

## Is it safe to connect Deputy to Cotlet?

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

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

## Is there a Deputy MCP server on GitHub?

Yes. Community Deputy MCP servers exist on GitHub, some of them read-only, usually maintained by one person. You install one on your own computer, give it a token and keep it running yourself; when the API or your install changes, you or the maintainer fix it. Cotlet hosts the same kind of server for you, and our team keeps it working.

|  | GitHub MCP server | Cotlet |
|---|---|---|
| Setup | Clone the repo, install it, create an OAuth client and token in Deputy, add it to each MCP client | Sign up, sign in to Deputy once, add one MCP server or API key |
| When Deputy changes | It breaks until you or the maintainer fix it | Our team runs automatic checks and fixes it for you |
| Your Deputy session | A token in a file on your computer, readable by any program you run | In your own Cloud Browser in the EU, profile encrypted, only for the apps you enable, disabled for agents in one click |
| When the session expires | Tools fail until you refresh the token or sign in again by hand | Your Cloud Browser keeps you signed in; if Deputy logs you out, your agent gets a link to sign in again |
| Upkeep | You update, monitor and debug it yourself | Nothing to host or update |
| 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 Deputy 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 Deputy API cost?

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

**Do I need to be technical?**

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

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

Deputy 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 Deputy role does my agent need?**

Deputy lets Location Managers and System Administrators approve both the time and pay part of a timesheet, and Supervisors only the time part. Leave is decided by a Location Manager or System Administrator. Your agent works with the role of the account you sign in with, so use a manager account for approvals.

**Can my agent undo an approved timesheet?**

No. Deputy unapproves a timesheet only in its web app, and Cotlet has no tool for it. Approvals wait for your OK by default, so check the list before you confirm.

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

No. Every call to create_shift, publish_shifts, approve_timesheet, discard_timesheet, approve_leave_request or decline_leave_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 Deputy 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/deputy 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.