MCP.so
Sign In

MCP Google Calendar Server

@markelaugust74

About MCP Google Calendar Server

A Model Context Protocol (MCP) server implementation for Google Calendar integration. Create and manage calendar events directly through Claude or other AI assistants.

Basic information

Category

Productivity

License

MIT

Runtime

node

Transports

stdio

Publisher

markelaugust74

Config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Google Calendar Server?

A Model Context Protocol (MCP) server implementation that enables AI assistants like Claude to create and manage Google Calendar events.

How to use MCP Google Calendar Server?

Clone the repository, install dependencies, configure OAuth2 credentials in a .env file, run npm run auth to obtain a refresh token, update the token in index.js, then start the server with npm start.

Key features of MCP Google Calendar Server

  • Create calendar events with title, description, start/end times.
  • Support for adding event attendees.
  • OAuth2 authentication with Google Calendar API.
  • Full MCP protocol implementation.
  • Debug logging for troubleshooting.

Use cases of MCP Google Calendar Server

  • AI assistants scheduling events on behalf of users.
  • Automating calendar event creation through natural language prompts.
  • Integrating Google Calendar management into MCP-compatible tools.

FAQ from MCP Google Calendar Server

What are the prerequisites for running the server?

Node.js v18 or later, a Google Cloud Console project with the Calendar API enabled, and OAuth2 credentials (Client ID and Client Secret).

How does authentication work?

The server uses OAuth2. You must obtain a refresh token by running npm run auth and then add it to your configuration.

Where are credentials stored?

Google OAuth2 credentials are stored in a .env file, and the refresh token is updated directly in index.js.

Does the server support any transports other than stdio?

The README does not mention alternative transports; it defaults to MCP over stdio.

Are there any known limitations?

The README does not document specific limitations beyond the dependencies and setup requirements.

Comments

More Productivity MCP servers