The whole point of this one is that the join URL comes back in the conversation, so an assistant that just booked a meeting can also paste the link into the message it is drafting. The setup cost is real and front-loaded: your own Google Cloud project, your own OAuth client, one browser authorisation. After that it is five operations and no further ceremony.
An MCP server that manages Google Meet meetings through the Google Calendar API. Meetings are calendar events with a Meet link attached, so the five operations here are the ones scheduling actually needs: create, list, read, update, delete.
- A new Google Meet meeting created with your settings — `create-meeting`
- Your upcoming meetings listed — `list-meetings`
- The details of one meeting, including its join URL — `get-meeting-details`
- An existing meeting changed — `update-meeting`
- A meeting deleted — `delete-meeting`
A Google account and your own OAuth client. In the Google Cloud Console: create or pick a project, enable the Google Calendar API, create OAuth 2.0 credentials of type Desktop application, and save the downloaded JSON as `credentials.json` in the project root. Then `npm install` and `npm run setup`, which opens a browser for you to authorise access to your calendar and writes the token. `npm run start` runs the server, and a client entry points node at `src/index.js`. The npm package name is `google-meet-mcp` (1.0.0). A Smithery installer wires the Claude Desktop entry for you.
One command plus a key — npx -y @smithery/cli install @cool-man-vk/google-meet-mcp-server --client claude, then supply credentials