lucca
lucca.
An employee of the Lucca directory — the roster, or one employee.
setup & usage
⚠ your lucca api access
lucca uses a static api key and your instance's subdomain; each firm/employer enters their own, their data is only visible to them. generate the key from your lucca account or via your lucca contact.
api_key — api key generated in settings → apidomain — only the subdomain of your instance (e.g. acme for acme.ilucca.net), not the full urlenter these two fields in your oto connector keys under lucca
▸ browse the directory, absences, expenses and organization
read-only.
lucca_employee(op="list") lists the reachable employees, lucca_employee(op="get") the detail of an employee by idlucca_absence(op="list") the absences posted over a period (date required; the free-text comment is cut by default, fields=["*"] returns it), lucca_absence(op="get") the detail of an absencelucca_leave_request(op="list") the leave requests (the approval workflow), lucca_leave_request(op="get") the detail of a requestlucca_expense_claim() the expense claims — no detail by id, lucca only exposes the listlucca_department(op="list") the departments (employee lists are cut by default, fields=["*"] returns them), lucca_department(op="get") the detail of a departmentlucca_establishment() the establishments — no detail by id, base and pagination different from the rest; the nested legal entity is cut by default⚙ multiple comptes
this connector accepts multiple comptes: each stored credential becomes a named account (one name per compte), at your level, your team's or your org's.
_account="<name>" on the tool; list them: oto_identity(op='list', connector='lucca') (scope='org' or scope='group' for the org's or team's)oto_identity(op='set', connector='lucca', identity_id='<name>'); rename: op='rename' with new_name_account) and adding upoutils
chargement…
utilisation
claude code — installe le plugin oto —
claude plugin marketplace add otomata-tech/oto-plugin — mcp + skill configurés.cli —
pipx install oto-cli puis oto lucca …