mcp

mcp server

Installation

Run this command in your terminal to add the MCP server to Claude Code.

Run in terminal:

Command

claude mcp add --transport stdio pranavmanoj1-mcp-server node path/to/server.js \
  --env GOOGLE_CLIENT_ID="Your Google Cloud Console client ID" \
  --env GOOGLE_REDIRECT_URI="Your configured redirect URI" \
  --env GOOGLE_CLIENT_SECRET="Your Google Cloud Console client secret"

How to use

This MCP server integrates Google Calendar with the Model Context Protocol to enable context-aware calendar management. It supports listing upcoming events, creating new events with titles, locations, and attendees, updating existing events, and deleting events across multiple calendars. The server maintains context across operations and uses OAuth 2.0 for secure authentication, storing credentials and tokens securely. To use it, obtain Google OAuth credentials and configure the environment variables as described, then start the server and interact with it through natural language prompts. Typical workflows include asking to show upcoming events, scheduling new meetings with attendees, rescheduling, or updating event details, all while benefiting from context-aware formatting and validation provided by the MCP layer.

How to install

Prerequisites:

Node.js v16 or higher
npm (comes with Node.js)
Google Cloud Platform account and a project with Google Calendar API enabled
OAuth 2.0 credentials (client ID, client secret, and redirect URI) configured for your app

Installation steps:

Clone the repository: git clone https://github.com/yourusername/google-calendar-mcp.git cd google-calendar-mcp
Install dependencies: npm install
Create a .env file (optional if you prefer env vars in the config): cp .env.example .env
Configure Google OAuth credentials in the environment:
- In .env or your environment, set: GOOGLE_CLIENT_ID, GOOGLE_CLIENT_SECRET, GOOGLE_REDIRECT_URI
Build the project (if applicable): npm run build
Start the server: npm start
Verify and authenticate:
- Follow the OAuth flow as prompted to grant access to Google Calendar.
- Ensure the tokens are stored securely by the MCP server.

Additional notes

Tips and common considerations:

Ensure the Google Calendar API is enabled in your Google Cloud project and that OAuth consent screen is configured.
Store Google OAuth tokens securely; the server should not commit credentials to version control.
If you rotate credentials, update the environment variables and redeploy.
The MCP server can handle multiple calendars; ensure the authenticated account has access to the calendars you intend to manage.
When testing, use a dedicated test calendar to avoid impacting production data.
Check logs for authentication errors or API quota issues; ensure you have appropriate OAuth scopes for read/write access to calendars.

Related MCP Servers

zen

1.1k

Selfhosted notes app. Single golang binary, notes stored as markdown within SQLite, full-text search, very low resource usage

MCP -Deepseek_R1

A Model Context Protocol (MCP) server implementation connecting Claude Desktop with DeepSeek's language models (R1/V3)

mcp-fhir

A Model Context Protocol implementation for FHIR

mcp

Inkdrop Model Context Protocol Server

mcp-appium-gestures

This is a Model Context Protocol (MCP) server providing resources and tools for Appium mobile gestures using Actions API..

dubco -npm

The (Unofficial) dubco-mcp-server enables AI assistants to manage Dub.co short links via the Model Context Protocol. It provides three MCP tools: create_link for generating new short URLs, update_link for modifying existing links, and delete_link for removing short links.