Connect your AI to Lucca API V3

What your AI can do with Lucca API V3

Once connected, these tools appear automatically in your AI assistant:

• list_usersread-only

  List users from the directory. Optionally filter by email and include former employees.

• get_userread-only

  Get one user's details. Pass a comma-separated `fields` list to customize.

• list_departmentsread-only

  List the organization's departments.

• list_leave_requestsread-only

  List leave requests (Timmi Absences), pending or already decided.

• list_leavesread-only

  List actually-booked leaves over a date range (Timmi Absences).

• decide_leave_requestwrite · needs approval

  Approve or deny a pending leave request. A comment is required when denying.

• list_expense_claimsread-only

  List Cleemy expense claims, optionally filtered by owner and status.

• list_timesheetsread-only

  List timesheets (Timmi), optionally filtered by owner and date range.

• list_time_entriesread-only

  List time entries (Timmi), optionally filtered by owner and date range.

• list_user_locationsread-only

  List where employees are working (Timmi Office) over a date range.

• list_work_locationsread-only

  List the available work locations / sites (Timmi Office).

• create_userwrite · needs approval

  Create a user in the directory. Pass the full Lucca user object in `user` (Lucca requires firstName, lastName, login, mail, dtContractStart, legalEntityId, employeeNumber, departmentId, managerId, rolePrincipalId, habilitedRoles, birthDate, calendarId, cultureID).

• update_userwrite · needs approval

  Update a user (full replace — PUT). Pass the complete Lucca user object in `user`; omitted required fields will be cleared, so include all of them.

Example prompts

Just ask your AI in plain language — it picks the right Lucca API V3 tool:

• “List users from the directory. Optionally filter by email and include former employees — from Lucca API V3, in plain language.”
• “Get one user's details. Pass a comma-separated `fields` list to customize — from Lucca API V3, in plain language.”
• “List the organization's departments — from Lucca API V3, in plain language.”
• “List leave requests (Timmi Absences), pending or already decided — from Lucca API V3, in plain language.”

How it works

1. Create your Proxoria account and add your MCP endpoint to Claude or ChatGPT.
2. Connect Lucca API V3 with your API key — each user connects their own account, credentials encrypted at rest.
3. Your AI instantly gets the Lucca API V3 tools. Write actions wait for your approval in the dashboard before anything changes.

Frequently asked questions

Does Lucca API V3 have an official MCP server?

You don't need one. Proxoria exposes Lucca API V3 to your AI through the Model Context Protocol, so you can use it from Claude, ChatGPT, Mistral or any MCP-compatible client — no official Lucca API V3 MCP server required.

What can my AI do with Lucca API V3 through Proxoria?

It gets 13 tools: list_users, get_user, list_departments, list_leave_requests, list_leaves, decide_leave_request, list_expense_claims, list_timesheets, list_time_entries, list_user_locations, list_work_locations, create_user, update_user. For example, list users from the directory. optionally filter by email and include former employees.

Is the Lucca API V3 connector read-only?

No — it can also make changes. Write actions go through Proxoria's confirmation guardrail by default: your AI proposes them, and you approve each one from your dashboard before anything is written to Lucca API V3.

How do I connect Lucca API V3 to my AI?

Create a Proxoria account, connect Lucca API V3 with your API key, and add your Proxoria MCP endpoint to Claude or ChatGPT. Your AI instantly gains the Lucca API V3 tools.