Deputy MCP server

What the model can do

Deputy workforce management: employees, timesheets, rostered shifts, leave and leave rules, locations and areas; can raise a leave request and approve, decline or cancel one, clock an employee in or out, approve or discard a timesheet, post a memo to staff, and add a journal note to an employee.

Reads

• deputy_employeesPeople in Deputy: employee id, name, position, location id and whether active.
• deputy_timesheetsTimesheets (hours actually worked): employee, date, start and end, hours, in progress, approved, area and location, and total hours.
• deputy_shiftsRostered shifts: employee (or open), date, start and end, hours, published or draft, area and location.
• deputy_leaveLeave that overlaps a period: employee, leave rule id, first and last day, start and end, and Deputy's status code.
• deputy_leave_rulesDeputy leave rules (leave types such as annual, sick or unpaid): id, name, type, whether paid and whether employees see it.
• deputy_locationsDeputy locations (what Deputy calls a Company) and the areas within them (an OperationalUnit), with ids.

Acts, when you ask

These change something in Deputy. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• deputy_request_leaveRaises a leave request in Deputy for an employee, waiting for a manager to approve it…
• deputy_set_leave_statusApproves, declines or cancels a Deputy leave request, optionally with a comment from the approver.
• deputy_start_timesheetClocks a Deputy employee in now, starting a timesheet in the given area.
• deputy_end_timesheetClocks a Deputy employee out now, ending their in-progress timesheet, with an optional unscheduled meal break in minutes.
• deputy_approve_timesheetApproves a completed Deputy timesheet, so it goes into the next payroll export.
• deputy_discard_timesheetDiscards a Deputy timesheet, permanently: the hours are not paid and the employee sees it was discarded by a supervisor.
• deputy_create_memoPosts a memo in Deputy that the staff of a location (and any other named locations or users) see in their news feed and app.
• deputy_add_journal_noteAdds a journal note to a Deputy employee's record, which managers with access to that employee can read.

Connect it

First connect Deputy on Dashboard → Connections, then add Memtro to your client once. The Deputy tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Deputy connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › Who is rostered on Saturday at the Manchester store?
• › How many hours did Dan Fletcher work this week?
• › Which timesheets from last week are not yet approved?
• › Approve Priya Sharma's leave request for 12 to 14 December
• › Post a memo to the Leeds staff that the store opens at 10 on Boxing Day

Questions

Is this an official Deputy MCP server?

No. It is Memtro's MCP server with Memtro's Deputy connector behind it: the connector reads Deputy through its API with the credentials you connect on Dashboard → Connections, and Deputy publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Deputy?

Only when you ask, and only what it has been granted: raise a leave request in Deputy for an employee, awaiting manager approval; approve, decline or cancel a Deputy leave request; clock a Deputy employee in (start a timesheet); clock a Deputy employee out (end a timesheet), with an optional meal break; approve a Deputy timesheet for payroll; discard a Deputy timesheet, permanently; post a memo in Deputy to a location's staff or named users; add a journal note to a Deputy employee's record. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · People and HR

• BambooHR MCP server
• Personio MCP server
• Microsoft Entra ID MCP server
• Google Workspace MCP server
• HiBob MCP server
• Greenhouse MCP server