Overview
What is Google Meet MCP Server?
A Model Context Protocol (MCP) server that allows AI agents to create, retrieve, and manage Google Meet meetings through the Google Calendar API. It is intended for developers and users who want programmatic control over Google Meet via compatible AI systems.
How to use Google Meet MCP Server?
Install via Smithery (npx -y @smithery/cli install @cool-man-vk/google-meet-mcp-server --client claude) or clone the repository, install dependencies, set up Google API OAuth 2.0 credentials, and run npm run setup to authenticate. Then start the server with npm run start. The server exposes tools such as create-meeting, list-meetings, get-meeting-details, update-meeting, and delete-meeting. Add the server configuration to your MCP settings file.
Key features of Google Meet MCP Server
- Create Google Meet meetings with custom settings.
- Retrieve meeting details including join URLs.
- Update existing meetings.
- Delete meetings.
- List upcoming Google Meet meetings.
Use cases of Google Meet MCP Server
- Automating meeting creation in AI-assisted workflows.
- Retrieving meeting details for scheduling or notifications.
- Updating or deleting meetings programmatically via chat agents.
- Integrating meeting management into custom AI tools.
FAQ from Google Meet MCP Server
What does Google Meet MCP Server do?
It provides tools for AI agents to create, list, retrieve, update, and delete Google Meet meetings by interacting with the Google Calendar API.
What dependencies are required?
Node.js, npm, and a Google Cloud project with the Google Calendar API enabled. OAuth 2.0 credentials are needed for authentication.
How is user data handled?
User data (meeting details) is stored in the user's Google Calendar. The server accesses it only through the Google Calendar API after user authorization.
What transport does the server use?
The server uses standard MCP transport via command-line invocation (stdio). No network transport is specified.
Is authentication required?
Yes, OAuth 2.0 authentication is required. Users must set up credentials via Google Cloud Console and run the setup script to generate a token.
