lacita

by app.lacita.api

Ownership verified

Server Details

MCP server for lacita - appointment management software

Status: Healthy
Last Tested: 2026-04-08 12:31
Transport: Streamable HTTP
URL

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client

Glama

MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.

Tool Definition Quality

Score is being calculated. Check back soon.

Available Tools

28 tools

add_calendar_reminderInspect

Add a reminder configuration to a calendar. Supports two types: "relative" (X minutes before) or "specific_time" (specific time on day before). Max 5 reminders per calendar.

ParametersJSON Schema

Name	Required	Description
`calendarId`	Yes	The calendar ID
`daysBefore`	No	For specific_time reminders: days before appointment (0 = same day, 1 = day before). Max 30.
`reminderType`	Yes	Type of reminder: "relative" for X minutes before, "specific_time" for specific time of day
`specificTime`	No	For specific_time reminders: time in HH:mm format (e.g., "20:00" for 8 PM)
`minutesBefore`	No	For relative reminders: minutes before appointment (e.g., 1440 = 24 hours, 60 = 1 hour). Min 5, max 43200 (30 days).

cancel_appointment

Destructive

Inspect

Cancel an existing appointment. Requires full scope.

ParametersJSON Schema

Name	Required	Description	Default
`reason`	No	Cancellation reason
`appointmentId`	Yes	The appointment ID

create_calendarInspect

Create a new booking calendar with optional settings.

ParametersJSON Schema

Name	Required	Description
`name`	Yes	Calendar name (required)
`duration`	No	Session duration in minutes (15-480, default: 45)
`minNotice`	No	Minimum booking notice in minutes (default: 240 = 4 hours)
`maxAdvance`	No	Maximum advance booking in minutes (default: 43200 = 30 days)
`bufferAfter`	No	Buffer after appointment in minutes (default: 15)
`description`	No	Calendar description
`bufferBefore`	No	Buffer before appointment in minutes (default: 0)
`defaultLocation`	No	Default location for appointments
`confirmationMode`	No	Confirmation mode (default: manual)
`remindersEnabled`	No	Enable appointment reminders (default: false)

create_calendar_overrideInspect

Create an availability override for a specific date (e.g., block a day off or modify hours).

ParametersJSON Schema

Name	Required	Description
`date`	Yes	Date in YYYY-MM-DD format
`reason`	No	Reason for the override
`endTime`	No	Override end time in HH:mm format (if not blocked)
`isBlocked`	Yes	If true, entire day is blocked
`startTime`	No	Override start time in HH:mm format (if not blocked)
`calendarId`	Yes	The calendar ID

create_contactInspect

Create a new contact. Requires write scope.

ParametersJSON Schema

Name	Required	Description
`email`	No	Email address
`phone`	No	Phone number
`lastName`	No	Last name
`firstName`	Yes	First name

delete_calendar

Destructive

Inspect

Delete a calendar and all its appointments. Requires full scope. This action is irreversible.

ParametersJSON Schema

Name	Required	Description	Default
`calendarId`	Yes	The calendar ID

delete_calendar_overrideInspect

Delete an availability override.

ParametersJSON Schema

Name	Required	Description	Default
`calendarId`	Yes	The calendar ID
`overrideId`	Yes	The override ID

delete_calendar_reminderInspect

Delete a reminder configuration from a calendar.

ParametersJSON Schema

Name	Required	Description	Default
`calendarId`	Yes	The calendar ID
`reminderId`	Yes	The reminder ID to delete

delete_contact

Destructive

Inspect

Delete a contact. Requires full scope.

ParametersJSON Schema

Name	Required	Description	Default
`contactId`	Yes	The contact ID

get_appointment

Read-onlyIdempotent

Inspect

Get detailed information about a specific appointment.

ParametersJSON Schema

Name	Required	Description	Default
`appointmentId`	Yes	The appointment ID

get_appointments

Read-onlyIdempotent

Inspect

List appointments with optional filtering by status and date.

ParametersJSON Schema

Name	Required	Description
`to`	No	End date in YYYY-MM-DD format
`from`	No	Start date in YYYY-MM-DD format
`limit`	No	Maximum number of results
`status`	No

get_calendar

Read-onlyIdempotent

Inspect

Get detailed information about a specific calendar including all settings.

ParametersJSON Schema

Name	Required	Description	Default
`calendarId`	Yes	The calendar ID

get_calendar_availability

Read-onlyIdempotent

Inspect

Get available time slots for a specific calendar on a given date. Use this to check what times are open for booking.

ParametersJSON Schema

Name	Required	Description
`date`	Yes	Date in YYYY-MM-DD format
`timezone`	No	Timezone (e.g., America/New_York). Defaults to UTC.
`calendarId`	Yes	The calendar ID

get_calendar_overrides

Read-onlyIdempotent

Inspect

Get availability overrides for a calendar (specific dates with modified or blocked availability).

ParametersJSON Schema

Name	Required	Description	Default
`calendarId`	Yes	The calendar ID

get_calendar_reminders

Read-onlyIdempotent

Inspect

Get all reminder configurations for a calendar. Each calendar can have up to 5 reminders.

ParametersJSON Schema

Name	Required	Description	Default
`calendarId`	Yes	The calendar ID

get_calendars

Read-onlyIdempotent

Inspect

List all booking calendars owned by the user. Returns an array of calendars with their settings including remindersEnabled, duration, buffers, etc.

ParametersJSON Schema

Name	Required	Description	Default
No parameters

get_calendar_weekly_availability

Read-onlyIdempotent

Inspect

Get the weekly availability schedule for a calendar (recurring slots for each day of the week).

ParametersJSON Schema

Name	Required	Description	Default
`calendarId`	Yes	The calendar ID

get_confirmation_settings

Read-onlyIdempotent

Inspect

Get confirmation settings for a calendar (confirmation mode and communication channel).

ParametersJSON Schema

Name	Required	Description	Default
`calendarId`	Yes	The calendar ID

get_contact

Read-onlyIdempotent

Inspect

Get detailed information about a specific contact.

ParametersJSON Schema

Name	Required	Description	Default
`contactId`	Yes	The contact ID

get_contacts

Read-onlyIdempotent

Inspect

List contacts with optional search.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results
`search`	No	Search term

get_notifications

Read-onlyIdempotent

Inspect

Get recent in-app notifications.

ParametersJSON Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results

reschedule_appointmentInspect

Initiate a reschedule request for an appointment. Requires write scope.

ParametersJSON Schema

Name	Required	Description
`reason`	No	Reason for rescheduling
`newStartTime`	Yes	New start time in ISO 8601 format
`appointmentId`	Yes	The appointment ID

send_invitationInspect

Send an appointment invitation to a client on behalf of the service provider. The visitor will receive a confirmation request. Check availability first using get_calendar_availability. You can reference an existing contact by contactId, or provide firstName/email/phone directly.

ParametersJSON Schema

Name	Required	Description
`email`	No	Email of the client
`notes`	No	Optional notes
`phone`	No	Phone of the client
`endTime`	Yes	End time in ISO 8601 format (e.g., 2025-01-15T10:45:00Z)
`lastName`	No	Last name of the client
`location`	No	Optional meeting location
`contactId`	No	Existing contact ID (optional — if provided, firstName/email/phone are used from the contact)
`firstName`	Yes	First name of the client
`startTime`	Yes	Start time in ISO 8601 format (e.g., 2025-01-15T10:00:00Z)
`calendarId`	Yes	The calendar ID

update_booking_settingsInspect

Update booking constraints for a calendar (min notice, max advance, buffers).

ParametersJSON Schema

Name	Required	Description
`minNotice`	No	Minimum booking notice in minutes
`calendarId`	Yes	The calendar ID
`maxAdvance`	No	Maximum advance booking in minutes
`bufferAfter`	No	Buffer after appointment in minutes
`bufferBefore`	No	Buffer before appointment in minutes
`minGapBetweenAppointments`	No	Minimum gap between appointments in minutes

update_calendarInspect

Update calendar settings including name, description, duration, buffers, reminders, etc.

ParametersJSON Schema

Name	Required	Description
`name`	No	Calendar name
`duration`	No	Session duration in minutes (15-480)
`isActive`	No	Whether calendar is active
`minNotice`	No	Minimum booking notice in minutes
`calendarId`	Yes	The calendar ID
`maxAdvance`	No	Maximum advance booking in minutes
`bufferAfter`	No	Buffer after appointment in minutes
`description`	No	Calendar description
`bufferBefore`	No	Buffer before appointment in minutes
`conflictMode`	No	Conflict checking mode
`defaultLocation`	No	Default location for appointments
`remindersEnabled`	No	Enable/disable appointment reminders
`conflictCalendarIds`	No	Calendar IDs to check for conflicts (when conflictMode is "selected")
`minGapBetweenAppointments`	No	Minimum gap between appointments in minutes

update_calendar_weekly_availabilityInspect

Update the weekly availability schedule for a calendar. This replaces all existing slots.

ParametersJSON Schema

Name	Required	Description	Default
`slots`	Yes	Array of availability slots
`calendarId`	Yes	The calendar ID

update_confirmation_settingsInspect

Update confirmation settings for a calendar (manual vs auto-verify, email vs SMS).

ParametersJSON Schema

Name	Required	Description
`calendarId`	Yes	The calendar ID
`confirmationMode`	No	manual requires provider confirmation, auto_verify auto-confirms
`communicationChannel`	No	Communication channel for confirmations

update_contactInspect

Update an existing contact. Requires write scope.

ParametersJSON Schema

Name	Required	Description
`email`	No	Email address
`phone`	No	Phone number
`lastName`	No	Last name
`contactId`	Yes	The contact ID
`firstName`	No	First name
`defaultLocation`	No	Default meeting location for this contact

Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:

{
  "$schema": "https://glama.ai/mcp/schemas/connector.json",
  "maintainers": [{ "email": "your-email@example.com" }]
}

The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.

Discussions

No comments yet. Be the first to start the discussion!

Try in Browser

Your Connectors

Resources

Need Help?