[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 MCP tools

> The Deputy MCP tools on the Cotlet server: every operation with its input schema, a tools/call example and an example result.

Source: https://cotlet.dev/docs/mcp/deputy

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Deputy has 12 operations on the Cotlet MCP server, in deputy_read and deputy_write. Your agent picks one in `operation`; the tool carries each operation's input schema. Open an operation for its schema and an example call.

- MCP server: `https://cotlet.dev/mcp/v1`
- MCP tools: `deputy_read`, `deputy_write`
- Connects with: Your own Deputy account (Location Manager or System Administrator to approve time and pay, Supervisor for the time part only)
- Integration page: https://cotlet.dev/integrations/deputy-api-mcp-server

## Read

Return data and change nothing in the account.

| Operation | Description |
|---|---|
| [`list_locations`](https://cotlet.dev/docs/mcp/deputy/list_locations.md) | Locations of your Deputy install with their IDs. |
| [`list_employees`](https://cotlet.dev/docs/mcp/deputy/list_employees.md) | Team members of a location with their IDs. |
| [`list_shifts`](https://cotlet.dev/docs/mcp/deputy/list_shifts.md) | Shifts of a location between two dates, draft, open and published. |
| [`list_timesheets`](https://cotlet.dev/docs/mcp/deputy/list_timesheets.md) | Timesheets of a location, oldest first, pending or approved. |
| [`get_timesheet`](https://cotlet.dev/docs/mcp/deputy/get_timesheet.md) | One timesheet with its break, comment and the shift it belongs to. |
| [`list_leave_requests`](https://cotlet.dev/docs/mcp/deputy/list_leave_requests.md) | Pending leave requests with employee, dates, leave type and comment. |

## Write

Change the account. Calls marked Confirm wait for the user to approve them.

| Operation | Description |
|---|---|
| [`create_shift`](https://cotlet.dev/docs/mcp/deputy/create_shift.md) (Confirm) | Add a shift to a location as a draft that only managers see. |
| [`publish_shifts`](https://cotlet.dev/docs/mcp/deputy/publish_shifts.md) (Confirm) | Publish the draft shifts of a location between two dates to the team. |
| [`approve_timesheet`](https://cotlet.dev/docs/mcp/deputy/approve_timesheet.md) (Confirm) | Approve one pending timesheet. |
| [`discard_timesheet`](https://cotlet.dev/docs/mcp/deputy/discard_timesheet.md) (Confirm) | Discard a timesheet for a shift that was not worked. |
| [`approve_leave_request`](https://cotlet.dev/docs/mcp/deputy/approve_leave_request.md) (Confirm) | Approve a pending leave request and set the hours of each day. |
| [`decline_leave_request`](https://cotlet.dev/docs/mcp/deputy/decline_leave_request.md) (Confirm) | Decline a pending leave request with a reason. |

---

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.