A Model Context Protocol (MCP) server for interacting with Google Meet through the Google Calendar API
A Model Context Protocol (MCP) server for interacting with Google Meet through the Google Calendar API
This project implements an MCP server that allows AI agents to interact with Google Meet by creating, retrieving, and managing meetings through the Google Calendar API. It leverages the MCP (Model Context Protocol) specification to expose these capabilities as tools that can be used by compatible AI systems.
Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| create-meeting | Create a new Google Meet meeting |
| list-meetings | List upcoming Google Meet meetings |
| get-meeting-details | Get details about a specific meeting |
| update-meeting | Update an existing meeting |
| delete-meeting | Delete a meeting |
{
"mcpServers": {
"google-meet": {
"command": "node",
"args": [
"path/to/google-meet-mcp/src/index.js"
],
"env": {},
"disabled": false
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
Store entities, relations and observations in a local knowledge graph with the reference Memory MCP server.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.