google-meet

The Google Meet MCP Server provides a set of MCP-compatible tools to manage Google Meet meetings via the Google Calendar API. It exposes operations to create, retrieve, update, list, and delete Google Meet meetings, including access to join URLs and meeting metadata. Once the server is up and authenticated with Google credentials, an AI agent can invoke the provided tools such as create-meeting, list-meetings, get-meeting-details, update-meeting, and delete-meeting to orchestrate conference scheduling and attendance workflows within an automation or agent system.

Prerequisites:

• Node.js and npm installed on your system
• Google Cloud project with Calendar API enabled
• OAuth 2.0 credentials (Desktop) downloaded as credentials.json

Manual installation steps:

1. Clone the repository:

# Clone the repository
git clone https://github.com/yourusername/google-meet-mcp.git

2. Navigate to the project directory:

cd google-meet-mcp

3. Install dependencies:

npm install

4. Place Google credentials in the project root:

• Save the Google OAuth credentials as credentials.json in the project root.

5. Setup and authenticate with Google Calendar:

npm run setup

This will open a browser to authorize access and generate the token.

6. Start the MCP server:

npm run start

6. Alternatively, install via Smithery (if you use Smithery):

npx -y @smithery/cli install @cool-man-vk/google-meet-mcp-server --client claude

Environment tips:

• Ensure credentials.json is kept private and not committed to version control.
• If the token expires, re-run npm run setup to refresh authentication.
• The MCP tools support typical CRUD operations for meetings; ensure you pass valid meeting data and Google Meet settings.
• When deploying, consider setting environment variables for client credentials, redirect URIs, and any domain-wide delegation if applicable. Common issues:
• Authentication errors: verify credentials.json and the generated token; ensure calendar API is enabled for the project.
• API quota limits: monitor Google API usage and apply for higher quotas if needed.
• Path correctness: ensure the index.js path provided in the mcp config matches your repository structure.