# Match calendar invitees and read meetings through MCP

Meeting access used calendar attendee email records directly, and scoped meeting\-reading tools took shape for AI connectors\.

- Schema version: 1
- ID: meetso\-2026\-06\-08
- Slug: 2026\-06\-08\-match\-attendee\-access\-directly\-read\-meetings\-through\-an\-ai\-connector
- Period: 2026-06-08 to 2026-06-08
- Published: 2026-06-08
- Updated: None
- History: Development history
- Tags: integration

Dates describe development history and do not verify when changes became available.

- Banner asset: identity\-matching
- Banner alt: Participant names in a meeting record

![Participant names in a meeting record](/_next/static/media/identity-matching.2ecqk5lsmu8h6.svg)

## Match calendar attendee email addresses directly

- ID: match\-attendee\-access\-directly
- Type: fixed
- Area: meetings
- Availability: unverified

Fixed meeting access for people whose email address appeared on the calendar invitation\.

A calendar invitation could establish access without showing whether the person attended the call\.

## Read meetings through an AI connector

- ID: read\-meetings\-through\-an\-ai\-connector
- Type: added
- Area: integrations
- Availability: unverified

Added MCP tools to list meetings and read a meeting’s details within the caller’s permitted access\.

Meeting lists were paginated\. Both listing and opening a meeting checked the caller’s scope and meeting visibility, so connecting an AI tool did not grant access to every meeting in a workspace\.

### Technical notes

- MCP list\_meetings and get\_meeting recheck tool scope and apply caller\-specific meeting access\.