Frequently Asked Questions (FAQ) - Google Calendar MCP Server

Q: What is the Google Calendar MCP Server? A: It’s a Python-based server that allows Large Language Models (LLMs) to interact with the Google Calendar API through natural language, enabling AI agents to manage schedules and events.

Q: What is MCP? A: MCP stands for Model Context Protocol. It’s an open standard that defines how applications provide context and functionality to LLMs.

Q: What features does the MCP Server offer? A: It provides features like secure authentication, calendar listing/creation, event finding/creation/updating/deletion, attendee management, free/busy time queries, and automated meeting scheduling.

Q: How does the authentication work? A: It uses OAuth 2.0 for secure access to the Google Calendar API. It utilizes the Desktop App Flow with automatic token storage and refresh.

Q: What are the prerequisites for setting up the server? A: You need Python 3.8+, Git, and access to a Google Cloud Platform project with the Google Calendar API enabled.

Q: How do I install the dependencies? A: Navigate to the project directory in your terminal and run pip install -r requirements.txt.

Q: How do I configure the server to work with my MCP client? A: You need to configure your MCP client to run the run_server.py script, providing the full path to the Python executable and the script.

Q: Where are the Google Client ID and Secret stored? A: They are stored in the .env file in your project directory. Do not include them directly in your MCP client configuration.

Q: What is the UBOS platform, and how does this MCP Server integrate with it? A: UBOS is a full-stack AI Agent Development Platform focused on helping businesses orchestrate AI Agents, connect them with enterprise data, build custom AI Agents with LLMs, and create Multi-Agent Systems. This MCP server provides a way for those agents to interact with Google Calendar.

Q: What license is the project released under? A: It’s dual-licensed under the GNU Affero General Public License v3.0 (AGPL-3.0) and a commercial license.

Q: How do I obtain a commercial license? A: Contact deciduusleaf@gmail.com for inquiries regarding commercial licensing options.

Q: I see a Task 3.5 and other task numbers mentioned in the documentation. What do these refer to? A: These refer to internal development tasks and milestones within the project’s roadmap. They are generally not relevant to end-users.

Q: Can I use this to read-only access to calendars? A: Yes, you can modify the CALENDAR_SCOPES variable in the .env file to 'https://www.googleapis.com/auth/calendar.readonly' for read-only access.

Q: The documentation mentions a timeout setting for the MCP client. What value should I use? A: The appropriate timeout value depends on the expected duration of calendar operations. Start with a value like 30000 (30 seconds) and adjust as needed based on observed performance.