Homebase MCP by usefulapi

Reviewed 1h ago.

• tools: 16 tools scanned
• metadata: scanned

• mediumReviewRemote tools take credentials as input

  Whatever an agent passes to a remote tool leaves the machine. Never send connection strings, tokens or passwords to a third-party MCP server unless it is the service those credentials belong to.

  homebase_get_company

Tools (16)

• homebase_get_company

  The Homebase company this API key belongs to: name, owner (id, name, email, phone) and created/updated times. GET /company.

• homebase_list_locations

  List the locations (stores or sites) of the account with uuid, name, address, phone, website and time zone. The uuid is the id every other Homebase tool needs. GET /locations.

• homebase_get_location

  One location by uuid: name, address, phone, website, time zone and POS merchant id. GET /locations/{location_uuid}.

• homebase_get_location_plan

  The Homebase subscription plan of a location: plan number, price, last update and trial state. GET /locations/{location_uuid}/plan.

• homebase_list_employees

  List the employees of a location with contact details and their job: level, default role, additional roles, wage type and rate, payroll id and archive date. The time-clock PIN is never returned. GET /locations/{location_uuid}/employees.

• homebase_get_employee

  One employee of a location by user id, with contact details and job (role, wage type and rate, payroll id). The id is the job's user id from homebase_list_employees. GET /locations/{location_uuid}/employees/{id}.

• homebase_list_shifts

  List the scheduled shifts of a location in a date range: employee, role, department, start and end, published/open state, wage rate and scheduled labor hours (regular, overtime). Filter open shifts only. GET /locations/{location_uuid}/shifts.

• homebase_get_shift

  One shift of a location by id, with its labor data and optional note. GET /locations/{location_uuid}/shifts/{id}.

• homebase_list_deleted_shifts

  The ids of shifts deleted in a date range at a location, with their start, end and deletion time. Use it to keep a copy of the schedule in sync. GET /locations/{location_uuid}/shifts/deleted.

• homebase_list_timecards

  List the timecards (worked time) of a location in a date range: employee, role, clock in and out, breaks, hours, labor cost, tips and approval state. Time-off hours are always 0 on timecards; use homebase_get_labor_by_employee for totals with time off. GET /locations/{location_uuid}/timecards.

• homebase_get_timecard

  One timecard of a location by id: clock in and out, breaks, labor hours and cost, tips, approval state. GET /locations/{location_uuid}/timecards/{id}.

• homebase_list_deleted_timecards

  The ids of timecards deleted in a date range at a location, with clock in, clock out and deletion time. Use it to keep a copy of the timecards in sync. GET /locations/{location_uuid}/timecards/deleted.

• homebase_get_labor

  Aggregate labor for a location in a date range, grouped by day or by hour: regular, overtime and paid hours, labor cost, tips, breaks and time off. GET /locations/{location_uuid}/labor.

• homebase_get_labor_by_role

  Aggregate labor (hours, cost, tips, overtime) for a location in a date range, grouped by role. GET /locations/{location_uuid}/labor/by_role.

• homebase_get_labor_by_employee

  Aggregate labor (hours, cost, wage rate, tips, overtime, time off) for a location in a date range, grouped by employee. Use it for payroll totals. GET /locations/{location_uuid}/labor/by_employee.

• homebase_get_timeclock_status

  The current time-clock state of one job (employee at a location): clocked_in, on_break or clocked_out, the current shift, the shifts that can be clocked into and the breaks that can be started. The job id is the `job.id` of an employee from homebase_list_employees. GET /timeclock/status.