Skip to main content
Glama
QA-Shivam

google-calendar-mcp

by QA-Shivam
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

sk-mcp-server-google-calendar

A lightweight Model Context Protocol (MCP) server for reading Google Calendar events by date. This package is intended to be published to npm and run through an MCP client with npx.

What it does

This server exposes one tool:

  • getMyCalendarDataByDate - fetches calendar events and meetings for a specific date

It returns matching events as simple text entries in the form:

  • Meeting title at 2026-06-16T11:30:00Z

Related MCP server: Google Calendar MCP Server

Requirements

  • Node.js 18 or newer

  • A Google Calendar API key

  • A Google Calendar ID

Installation

npm install

If you want to test the published package directly, you can run it with:

npx -y sk-mcp-server-google-calendar

Environment Variables

Create a .env file in the project root with:

GOOGLE_PUBLIC_API_KEY=your_google_api_key
CALENDAR_ID=your_calendar_id

Running the server

Start the MCP server with:

npm start

Or run the executable directly:

node server.js

If installed globally or linked as a package bin, the command is:

google-calendar-mcp

MCP Tool

getMyCalendarDataByDate

Retrieves Google Calendar events for a given date.

Input

  • date - a valid date string, such as 2026-06-16

Output

Returns JSON text with either:

  • meetings: an array of event strings

  • error: an error message if the request fails

Example MCP Client Configuration

If you are connecting this server from an MCP client after publishing it to npm, use the package name as the command target.

Example:

{
  "mcpServers": {
    "My Calendar": {
      "command": "npx",
      "args": [
        "-y",
        "sk-mcp-server-google-calendar"
      ],
      "env": {
        "GOOGLE_PUBLIC_API_KEY": "your_google_api_key",
        "CALENDAR_ID": "your_calendar_id"
      }
    }
  }
}

Notes

  • Event lookup is performed using UTC day boundaries.

  • The tool returns up to 10 events for the requested date.

  • The server uses standard input/output transport for MCP compatibility.

License

ISC

Available Tools

1 tool
getMyCalendarDataByDateB

Retrieve Google Calendar events and meetings for a specified date.

ParametersJSON Schema
NameRequiredDescriptionDefault
dateYes

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Retrieve' implies read-only, the description does not mention side effects, authorization needs, rate limits, or response format. This is insufficient for an agent to fully understand the tool's behavior.

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

Conciseness4/5

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

The description is a single sentence with no wasted words. It is front-loaded and efficient. However, it could be slightly expanded to include parameter format without becoming verbose.

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

Completeness3/5

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

Given the tool's simplicity (one parameter, no output schema, no siblings), the description provides the core purpose. However, it lacks details about the date format and what the response contains. This is minimally adequate but leaves gaps for an agent to make assumptions.

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

Parameters2/5

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

The input schema lists one parameter 'date' with no description (0% coverage). The description vaguely says 'for a specified date' but does not clarify the expected format (e.g., 'YYYY-MM-DD') or any constraints like timezone or allowed values. This adds minimal value beyond the schema.

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

Purpose5/5

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

The description clearly states the action ('Retrieve'), the resource ('Google Calendar events and meetings'), and the condition ('for a specified date'). It is specific and unambiguous, and with no sibling tools, no further differentiation is needed.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives is provided, but since there are no sibling tools, the usage context is implied to be any situation requiring calendar events for a specific date. However, no constraints or prerequisites are mentioned.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusion between tools.

Naming Consistency5/5

Single tool uses a clear camelCase convention with no inconsistencies.

Tool Count1/5

A Google Calendar server with only one tool is extremely limited; expected at least CRUD and list operations.

Completeness1/5

Only retrieval by date is provided; missing create, update, delete, listing, and other common calendar operations.

Maintenance

ActivityInactive
ResponsivenessSyncing

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/QA-Shivam/google-calendar-mcp'

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