Skip to main content
Glama

MCP Server Setup

The server.js file contains the implementation of the Google Calendar MCP server.

Note: The MCP configuration may vary depending on the editor or MCP client you are using. The following instructions are for Cursor.

Prerequisites

Before configuring the MCP server, ensure you have:

  • Node.js installed

  • Cursor Editor installed and signed in

  • A Google Calendar API key

  • Your Google Calendar ID

Setup in Cursor

  1. Open Cursor.

  2. Go to Settings.

  3. Navigate to Tools → MCP.

  4. Add a new MCP server using the following configuration:

{
  "mcpServers": {
    "filesystem": {
      "command": "node",
      "args": [
        "PATH_TO_SERVER_JS"
      ],
      "env": {
        "GOOGLE_PUBLIC_API_KEY": "YOUR_GOOGLE_API_KEY",
        "CALENDAR_ID": "YOUR_CALENDAR_ID"
      }
    }
  }
}

Configuration

Replace the placeholders below with your own values:

  • PATH_TO_SERVER_JS – Absolute path to the server.js file.

  • YOUR_GOOGLE_API_KEY – Your Google Calendar API key.

  • YOUR_CALENDAR_ID – Your Google Calendar ID (typically your Gmail address for your primary calendar).

After saving the configuration, restart Cursor (if required). Your MCP server will then be available for use.


Related MCP server: googlecalendar-mcp

Important Note

This project currently uses a Google Calendar API Key, which can only access public Google Calendars.

If your calendar is private, the server will not be able to retrieve event details such as the title, description, or attendees. To access private calendars or support creating, updating, and deleting events, you must replace the API key authentication with OAuth 2.0.

Current Features (API Key)

  • Read events from public Google Calendars

  • Retrieve events by date

  • Read private calendars

  • Create calendar events

  • Update calendar events

  • Delete calendar events

For full Google Calendar functionality, OAuth 2.0 authentication is recommended.

Resources

For a detailed guide on building custom MCP servers with TypeScript, check out the following article:

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

Only one tool exists, so there is no risk of confusing between tools.

Naming Consistency5/5

With a single tool, naming consistency is inherently maintained.

Tool Count2/5

A Google Calendar server with only one tool is too few for its apparent scope, failing to cover basic operations.

Completeness1/5

The tool has no description and likely only fetches data by date, missing essential CRUD operations for a calendar service.

Maintenance

ActivityStale
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

  • F
    license
    Not graded
    quality
    D
    maintenance
    An MCP server that provides integration with Google Calendar, allowing users to list calendars and manage events. It enables searching, creating, and modifying calendar entries through tools designed for the Model Context Protocol.
    -
  • A
    license
    A
    quality
    C
    maintenance
    A Google Calendar MCP server built with FastMCP, providing tools for event CRUD, calendar management, and availability queries via the Google Calendar API.
    9
    MIT

Appeared in Searches

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/umachandra-30/GoogleCalenderMCP'

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