Meeting MCP Servers

This API creates a new meeting with specified details such as title, start time, duration, participants, and host information. The request body must include the title, startDateTime, and durationInSeconds as required fields. Participants and host details can also be provided, including their email addresses, which are required. Optional fields include meetingProviderURL, language, and metaData. The API returns a unique meetingId for the newly created meeting.

The 'Delete an Existing Meeting' API allows users to delete a meeting by specifying the meeting ID in the path parameters. This API does not require any headers, query parameters, or request body. Upon successful deletion, the API does not return any response body.

This API retrieves a list of all users in the system. It accepts an optional query parameter 'pageToken' for pagination. The response includes a 'pageToken' for the next set of records and a list of users with details such as user ID, first and last names, emails, phone numbers, title, role, language, creation and last login timestamps, team IDs, manager ID, active status, and personal meeting URLs.

The 'Get Transcript For A Meeting' API retrieves the full transcript for a specified meeting. It requires a 'meetingId' as a query parameter to identify the meeting. The response includes an array of 'meetingTranscripts', each containing a 'speakerId' and an array of 'sentences'. Each sentence has a 'start' and 'end' timestamp in ISO 8601 UTC format and the 'text' of the sentence.

The Get Transcript Metadata for a Meeting API retrieves metadata for a given meeting transcript. It requires the meeting ID as a mandatory query parameter and optionally accepts a transcript ID to specify which transcript's metadata is needed. The response includes an array of meeting transcripts, each containing the transcript ID, URL, and text content.

This API retrieves the details of a user based on the provided user ID. The request requires a path parameter 'userId' which is the ID of the user whose details are being fetched. The response includes detailed information about the user such as their ID, first and last name, emails, phone numbers, title, role, language, creation and last login timestamps, team IDs, manager ID, active status, and personal meeting URLs.

This API retrieves comprehensive details of a meeting given its ID. It includes information such as the meeting title, participants, scheduled and actual start times, duration, download URL for the recording, language, host details, agenda, and whether the meeting is internal or external. The request requires a 'meetingId' as a query parameter to identify the meeting. The response provides a detailed JSON object with all the meeting information.

This API retrieves comprehensive meeting details for a specified time range. It allows filtering of meetings based on optional parameters such as pagination cursor (pageToken), start and end date/time (startDateTime and endDateTime), and user IDs (userIds). The response includes detailed information about each meeting, such as the meeting ID, title, participants, scheduled and actual start/end times, duration, download URL, calendar event ID, language, host details, agenda, meeting type, and media type. This API is useful for obtaining a complete overview of meetings within a specified timeframe.