Deputy logo deputy.com

Live

Deputy API and MCP server

The Deputy API needs your own code and an OAuth token to approve timesheets, decide leave or build rosters. Sign in to Deputy once in your own Cloud Browser, and your AI agent does the work there for you. The same tools work over MCP for agents and as a REST API for scripts.

Sign up free View as Markdown

Not affiliated with Deputy.

Deputy has no API for this. So we run one for you.

Deputy's own API, a GitHub MCP server and Cotlet compared
What you need Deputy's APIGitHub MCP serverCotlet
Timesheet approvals, leave decisions, rostering No Partly Yes, 12 tools
Acts as you, signed in 24/7 No No Yes, Cloud Browser
Fixed for you when Deputy changes N/A No Yes, tested every 6h
Runs with your laptop off N/A No Yes, hosted

Checked Oct 20, 2026. Sources: Deputy Developer: Getting Started with the Deputy API · Deputy Developer: Integration and Data Availability Options · Deputy Developer: Using OAuth 2.0 · Deputy Developer: Timesheet Management Calls

Your own Cloud Browser, on 24/7. Sign in once. We keep it connected.

  1. 01Sign in to Deputy in your own Cloud Browser

  2. 02Connect it for your agents

  3. 03Cotlet keeps it signed in and working

How do I connect Deputy to Claude, ChatGPT or my code?

AI agents connect over MCP, scripts call the REST API. Both reach the same 12 tools with one API key.

For AI agents: MCP

Add Cotlet to your agent once. Deputy and every other app you connect show up as its tools.

  • Claude
  • ChatGPT
  • OpenClaw
  • Hermes
  • GrokBot
  • Cursor
  • n8n
  • Any MCP client
  1. 1

    Add Cotlet to your agent

    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"

    Paste the snippet for your client. The same server and key serve every app you connect, so you do this once.

For scripts: REST API

Every tool is an endpoint under /api/v1/deputy with its own method and path, such as POST /api/v1/deputy/timesheets/{timesheet_id}/approve, with the same API key. Our open-source repo has ready scripts to start from.

REST API docs

What can the Deputy API and MCP server do?

12 tools on your own Deputy account. Agents call them as operations of the MCP tools deputy_read and deputy_write; scripts call each one at its own REST endpoint, with the same inputs and answers.

API reference
Deputy tools in Cotlet's MCP server and REST API
Tool What it does Access
list_locations Locations of your Deputy install with their IDs. read
list_employees Team members of a location with their IDs. read
list_shifts Shifts of a location between two dates, draft, open and published. read
list_timesheets Timesheets of a location, oldest first, pending or approved. read
get_timesheet One timesheet with its break, comment and the shift it belongs to. read
list_leave_requests Pending leave requests with employee, dates, leave type and comment. read
create_shift Add a shift to a location as a draft that only managers see. writeasks first
publish_shifts Publish the draft shifts of a location between two dates to the team. writeasks first
approve_timesheet Approve one pending timesheet. writeasks first
discard_timesheet Discard a timesheet for a shift that was not worked. writeasks first
approve_leave_request Approve a pending leave request and set the hours of each day. writeasks first
decline_leave_request Decline a pending leave request with a reason. writeasks first

Scroll the table for all 12 tools.

Ask in plain words. Your agent does the rest.

All Deputy use cases

Is it safe to connect Deputy?

You sign in yourself in your own Cloud Browser, we never save your password, and anything that reaches your readers waits for your OK. The browser profile is encrypted in the EU. Independent scanners grade cotlet.dev A+.

Security overview

How much do the Deputy API and MCP server cost?

One price for both: a tool call costs the same over MCP or REST. Free 7-day trial with 2,000 credits, no card needed. Then one-time credit packs, no subscription, valid 12 months. Most calls use 25 credits, and your Cloud Browser uses 50 credits a day while Deputy is enabled for agents, so 20 calls a day come to 550 credits.

See full pricing
Cotlet credit packs: price, credits and calls at 25 credits each
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.

Questions

Does Deputy have an 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.

How do I get access?

Sign up free, open Deputy under Integrations in the console and press Request access. Your free trial starts with your account, no card needed.

Is the MCP server different from the API?

No, only the way in. Cotlet builds each integration as a REST API and puts an MCP server on top, so both have the same 12 tools, the same inputs and answers, one API key and one price. AI agents such as Claude, ChatGPT or Cursor use MCP; scripts, cron jobs and HTTP steps in n8n, Make or Zapier use the REST API.

What is the Cloud Browser?

Your own Chrome that Cotlet runs for you in the EU, around the clock. You open it from the console, sign in to Deputy yourself and press Enable for agents. Your agent's calls go through it, from its IP with its cookies, so Deputy sees the browser you signed in with. Password saving is off and the profile is stored encrypted with AES-256-GCM.

Can my agent act without asking me?

Not on anything that reaches other people: create_shift, publish_shifts, approve_timesheet, discard_timesheet, approve_leave_request, decline_leave_request wait for your OK by default. You can switch that off per tool for scheduled runs.

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.

Should I use a Deputy MCP server from GitHub instead?

Pick one if you want the code on your own computer and do not mind the upkeep: you install it, sign it in and fix it when Deputy changes. Pick Cotlet if you want it hosted and kept working for you.

Can I use it in n8n, Make or Zapier?

Yes. Add https://cotlet.dev/mcp/v1 in n8n's MCP Client node, or call the REST endpoints from an HTTP step in Make or Zapier.

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 Cotlet affiliated with Deputy?

No. Cotlet is independent and not affiliated with Deputy.

Give your agent access to Deputy.

Free 7-day trial with 2,000 credits, no card needed.

Sign up free