Product — LML Technologies S.r.l.

LML MCP Connector

The MCP (Model Context Protocol) server that lets an AI assistant read and manage a user’s schedule, integrating with Google Calendar.

What it is

LML MCP Connector is an MCP server. The Model Context Protocol is an open standard through which an AI assistant connects to external tools in order to carry out concrete operations on behalf of the person using it.

The connector exposes a narrow set of calendar operations to the assistant: reading events already scheduled, checking when time is free, creating a new appointment, updating an existing one. Those operations run on Google Calendar, subject to the user’s explicit authorisation.

It has no interface of its own: it is used through the AI assistant already deployed at the company. Every operation starts from a user request; the connector takes no action on its own initiative and does not run in the background.

Who it is for

Client companies of LML Technologies that already use AI assistants in their workflows and want those assistants to read and update the calendar, rather than merely suggesting what to do.

Sales teams that book appointments while talking to the assistant.
Front office and administrative staff coordinating several people’s calendars.
Professional and technical firms scheduling jobs, visits and site inspections.
Internal teams checking availability and arranging meetings without opening the calendar.

This is not a consumer product: it is activated as part of a contractual relationship with LML Technologies.

What it actually does

Four operations, every one of them triggered by an explicit user request.

Review scheduled commitments

The assistant reads the events within a given time range and summarises them.

Example “What do I have on Thursday afternoon?” — the assistant lists the afternoon events with time, title and attendees.

Check availability

The assistant compares existing commitments and identifies the slots still free.

Example “Do I have two consecutive free hours next week for the project review?” — the assistant proposes the matching slots.

Create events

The assistant adds a new appointment to the calendar chosen by the user.

Example “Book a call with the supplier on Tuesday at 3 p.m., one hour.” — the event is created with title, time and description.

Update events

The assistant updates an existing event: time, duration, title, description.

Example “Move tomorrow’s meeting from 10 to 11.30.” — the event is updated to the new time.

Which data is used, and why

On first use the user authorises the connector through Google. Four permissions are requested: two concern the calendar, two serve only to recognise which account is connected and give access to no content. None is broader than necessary.

The list of calendars the user is subscribed to — read only

https://www.googleapis.com/auth/calendar.calendarlist.readonly

What it reads: The name, identifier and time zone of the user’s calendars. This permission gives the connector no access to event contents.
Why it is needed: It lets the user choose which calendar to work on — personal, work, a shared calendar — instead of the service deciding for them.

Reading and editing events

https://www.googleapis.com/auth/calendar.events

What it reads: The events in the selected calendar: title, date, time, duration, description, location, attendees. It also allows creating new events and updating existing ones.
Why it is needed: It covers both halves of the service: reading the schedule and checking availability (read), creating and updating appointments at the user’s request (write).

The email address of the connected account — read only

https://www.googleapis.com/auth/userinfo.email

What it reads: The primary email address of the authorised Google account, and nothing else. It gives no access to the rest of the profile, nor to the contents of the mailbox.
Why it is needed: It lets the user see which account is connected, so they can notice if they authorised the wrong one. It is not used for marketing communications.

Account identifier (OpenID Connect)

openid

What it reads: The standard identifier Google assigns to the account. It gives access to no content.
Why it is needed: It reliably ties the authorisation to the account that granted it.

The connector does not access the mailbox, contacts, files or any other service on the account. Calendar data is used solely to carry out the user’s request: it is not sold, not disclosed to third parties for their own purposes, not used for advertising, and not used to train artificial intelligence models.

How it is enabled, and how to revoke it

1
Connection
The client’s administrator connects LML MCP Connector to the company AI assistant.
2
Authorisation
On first use the user authorises access from the Google consent screen and selects the account. Without this step the connector can neither read nor write anything.
3
Calendar selection
The user indicates which of their calendars the connector should operate on.

Revoking access

Authorisation can be revoked at any time, without going through LML Technologies, from the Google account permissions page:

https://myaccount.google.com/permissions

From that moment the connector has no further access to the calendar. To have any residual data deleted, write to info@lmltech.it.

Who provides the service

Provider: LML Technologies S.r.l.
Registered office: Via J. F. Kennedy 24 — 70020 Bitritto (BA), Italy
VAT and tax code: IT09002320720
Contact: info@lmltech.it
Website: www.lmltech.it

LML MCP Connector is an independent product of LML Technologies S.r.l. It is not sponsored, endorsed, certified by, or otherwise affiliated with Google LLC. Google Calendar is a trademark of Google LLC; the reference is purely descriptive of the technical integration.

Data processing

The privacy policy sets out which data is processed, for which purposes, for how long, and how to exercise your rights.

https://lmltech.it/mcp-google/privacy