satelia-mcp-lucca
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LUCCA_API_KEY | Yes | Your Lucca API key | |
| LUCCA_BASE_URL | No | Optional full URL to override the default (e.g., for test environment) | |
| LUCCA_INSTANCE | Yes | The subdomain of your Lucca instance (e.g., 'satelia') |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lister-collaborateursA | Liste les collaborateurs (salaries) de l'instance Lucca. Permet de rechercher une personne par prenom, nom ou email et de recuperer son identifiant (id), utile pour ensuite consulter ses absences. |
| lister-departementsA | Liste les departements (services / equipes) de l'organisation Lucca, avec leur identifiant (id) et leur code. Utile pour filtrer les absences par departement. |
| lister-absencesA | Liste les absences (conges, RTT, etc.) sur une periode donnee, pour UN collaborateur (via son id) OU pour un departement (via son id). Les dates sont au format AAAA-MM-JJ. Chaque ligne correspond a une demi-journee. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct entity: absences, collaborators, and departments. There is no overlap as they handle different data types, making disambiguation straightforward for an agent.
All tools follow a consistent 'lister-' verb-noun pattern in French, with clear and predictable naming. No mixing of conventions.
With only 3 tools, the server is focused and uncluttered. The count is slightly below typical ranges but appropriate for a minimal read-only HR data access server.
The set covers listing of three core entities, but lacks write operations (create, update, delete) and more advanced filters. For a read-only server it's acceptable, but there are notable gaps in full lifecycle coverage.