Skip to main content
Glama
PranayChowdhury00

MCP Google Calendar Integration

📅 MCP Google Calendar Integration

This project is a Model Context Protocol (MCP) tool that connects with the Google Calendar API to fetch calendar events for a given date. It integrates seamlessly with AI-driven editors like Cursor to enhance your productivity by bringing live calendar data right into your coding environment.


🔧 Features

  • 📆 Get calendar events for a specific date

  • ⚡ Real-time integration using MCP

  • 🧠 Natural language tool commands from inside your editor

  • ✅ Simple schema validation using zod

  • 🔒 Uses environment variables to keep sensitive info secure


Related MCP server: Google Calendar MCP Server

📁 Project Structure

/MCP_SERVER │ ├── server.js # MCP server setup and calendar tool ├── .env # Environment variables (not committed) ├── package.json # Dependencies and scripts └── .mcp # MCP configuration file


📦 Technologies Used


🚀 Getting Started

1. Clone the repository

git clone https://github.com/your-username/mcp-calendar-tool.git
cd mcp-calendar-tool
  1. Install dependencies npm install

  2. Create a .env file GOOGLE_API_KEY=your_google_calendar_api_key CALENDAR_ID=your_calendar_id_or_email

  3. Run the server npm start


Usage Example (in Cursor)

🛠 MCP Configuration (.mcp)

{ "mcpServers": { "myCalenderData": { "command": "node", "args": ["server.js"], "env": { "GOOGLE_API_KEY": "your_api_key_here", "CALENDAR_ID": "your_calendar_id_here" } } } }

🔐 Notes on API Access

Make sure the Google Calendar API is enabled in your Google Cloud Console.

The calendar should be public or shared properly if using an API key.

🧭 Future Improvements

Add OAuth2 authentication for multiple users

Support recurring events and event descriptions

Integrate Google Tasks and reminders

📄 License

This project is open-source and available under the MIT License.

🙋‍♂️ Author

Pranay Chowdhury Frontend Developer | MERN Stack Enthusiast LinkedIn • GitHub

Available Tools

1 tool
getMyCalendarDataByDateD
ParametersJSON Schema
NameRequiredDescriptionDefault
dateYes

TDQS

D1/5.0
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedgetMyCalendarDataByDate

TDQS

D1.7/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool stands alone without any competing or confusing alternatives.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The naming pattern cannot be inconsistent when only one exists.

Tool Count2/5

A single tool for a Google Calendar integration is too few for the apparent scope. Calendar integrations typically require multiple operations like creating, updating, deleting events, and listing calendars, making this server severely under-equipped.

Completeness1/5

The tool surface is severely incomplete for a Google Calendar domain. With only a date-based data retrieval tool, there are obvious gaps in CRUD operations, event management, and other essential calendar functionalities, which will cause agent failures.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/PranayChowdhury00/MCP_SERVER'

If you have feedback or need assistance with the MCP directory API, please join our Discord server