Enterpret fork. This repository tracks
nspady/google-calendar-mcp
and adds a headless broker-token mode for Enterpret Agent. The upstream
interactive OAuth and multi-account flows remain available when broker mode
is not enabled. Enterpret package version is based on upstream
version and is versioned independently to avoid inherited Git tag
collisions.
Enterpret fork of the Google Calendar MCP server with broker-supplied OAuth bearer support
2026-11-11
Estrelas
—
Ferramentas
—
Disponibilidade
—
0.1.0
2.6.2
Enterpret broker-token mode
Enterpret Agent owns Google OAuth through Nango and starts this package as an
ephemeral stdio MCP subprocess. Set one environment variable:
does not read OAuth client credentials or token files;
does not start a browser or OAuth callback server;
supports stdio transport only;
performs a real calendarList.list probe before advertising tools;
omits manage-accounts, create-events, and list-colors from discovery.
Nango is responsible for refreshing the token before each subprocess run. The
broker-token mode must never receive or persist a refresh token.
If GOOGLE_CALENDAR_OAUTH_BEARER is present but empty or whitespace-only, the
server fails closed instead of falling back to interactive OAuth. Interactive
OAuth is selected only when the variable is absent.
The enabled tool set is list-calendars, list-events, search-events,
get-event, get-freebusy, get-current-time, create-event, update-event,
delete-event, and respond-to-event.
A Model Context Protocol (MCP) server that provides Google Calendar integration for AI assistants like Claude.
Features
Multi-Account Support: Connect multiple Google accounts (e.g., work, personal) and query them simultaneously
Multi-Calendar Support: List events from multiple calendars in a single request
Cross-Account Conflicts: Detect overlapping events across any combination of calendars
Event Management: Create, update, delete, and search calendar events
Recurring Events: Advanced modification capabilities for recurring events
Free/Busy Queries: Check availability across calendars
Smart Scheduling: Natural language understanding for dates and times
Intelligent Import: Add calendar events from images, PDFs, or web links
Quick Start
Prerequisites
A Google Cloud project with the Calendar API enabled
Enable the Google Calendar API for your project. Ensure that the right project is selected from the top bar before enabling the API.
Create OAuth 2.0 credentials:
Go to Credentials
Click "Create Credentials" > "OAuth client ID"
Choose "User data" for the type of data that the app will be accessing
Add your app name and contact information
Add the following scopes (optional):
https://www.googleapis.com/auth/calendar.events and https://www.googleapis.com/auth/calendar
Select "Desktop app" as the application type (Important!)
Save the auth key, you'll need to add its path to the JSON in the next step
Add your email address as a test user under the Audience screen
Note: it might take a few minutes for the test user to be added. The OAuth consent will not allow you to proceed until the test user has propagated.
Note about test mode: While an app is in test mode the auth tokens will expire after 1 week and need to be refreshed (see Re-authentication section below).
⚠️ Important Note for npx Users: When using npx, you must specify the credentials file path using the GOOGLE_OAUTH_CREDENTIALS environment variable.
Option 2: Local Installation
git clone https://github.com/aavaz-ai/google-calendar-mcp.git
cd google-calendar-mcp
npm install
npm run build
Then add to Claude Desktop config using the local path or by specifying the path with the GOOGLE_OAUTH_CREDENTIALS environment variable.
Option 3: Docker Installation
git clone https://github.com/aavaz-ai/google-calendar-mcp.git
cd google-calendar-mcp
cp /path/to/your/gcp-oauth.keys.json .
docker compose up
See the Docker deployment guide for detailed configuration options including HTTP transport mode.
First Run
Start Claude Desktop
Ask Claude to authenticate with the Google Calendar MCP server (e.g., "Authenticate with Google Calendar"). This step is required before using any calendar tool — without it, requests will fail with a -32600 error.
Complete the OAuth flow in your browser
You're ready to use calendar features!
Using Claude Code? The same steps apply — just ask Claude to authenticate with the Google Calendar MCP server from your CLI session before using any calendar tool.
Re-authentication
If you're in test mode (default), tokens expire after 7 days. If you are using a client like Claude Desktop it should open up a browser window to automatically re-auth. However, if you see authentication errors you can also resolve by following these steps:
Connect multiple Google accounts and use them simultaneously.
In chat (recommended): Use the manage-accounts tool to add, list, or remove accounts directly from your AI assistant - no terminal needed. See the Authentication Guide for details.
CLI: For initial setup, use npm run account auth <nickname> (e.g., npm run account auth work).
HTTP / Docker: Visit http://localhost:3000/accounts to manage accounts in the browser.
When no account parameter is supplied to a tool, read-only tools merge results from all accounts, while write tools auto-select the account with appropriate permissions.
Example Usage
Along with the normal capabilities you would expect for a calendar integration you can also do really dynamic, multi-step processes like:
Cross-calendar availability:
Please provide availability looking at both my personal and work calendar for this upcoming week.
I am looking for a good time to meet with someone in London for 1 hr.
Add events from screenshots, images and other data sources:
Add this event to my calendar based on the attached screenshot.
Supported image formats: PNG, JPEG, GIF
Images can contain event details like date, time, location, and description
Calendar analysis:
What events do I have coming up this week that aren't part of my usual routine?
Check attendance:
Which events tomorrow have attendees who have not accepted the invitation?
Respond to invitations:
Accept the team meeting invitation on my calendar for tomorrow at 2pm
Decline with a note:
Decline the Friday meeting with a note that I have a scheduling conflict
Respond to recurring events:
Accept just this week's standup, but keep future instances as tentative
Decline all future Monday planning meetings
Auto coordinate events:
Here's some availability that was provided to me by someone. {available times}
Take a look at the times provided and let me know which ones are open on my calendar.
Available Tools
Tool
Description
list-calendars
List all available calendars
list-events
List events with date filtering
get-event
Get details of a specific event by ID
search-events
Search events by text query
create-event
Create new calendar events
update-event
Update existing events
delete-event
Delete events
respond-to-event
Respond to event invitations (Accept, Decline, Maybe, No Response)
get-freebusy
Check availability across calendars, including external calendars
Note: The manage-accounts tool is always available regardless of filtering, as it's needed for authentication management.
Broker-token mode intentionally uses the fixed ten-tool surface documented
above and does not apply --enable-tools or ENABLED_TOOLS filtering.
When tool filtering is active, the server provides instructions to the AI assistant listing which tools are disabled. This allows the AI to inform users that additional functionality exists but is currently unavailable, without consuming the full token cost of those tool schemas.
If the list is empty or contains only commas, the server will fail to start with an error.
If an invalid tool name is specified, the server will fail to start with an error listing all available tools.
Security
Interactive OAuth tokens are stored securely in your system's config directory
Broker-supplied access tokens remain in process memory and never use token storage
Broker credentials are process configuration, never MCP tool arguments
Authentication material is not written to MCP responses or logs
All calendar operations require explicit user consent
Troubleshooting
OAuth Credentials File Not Found:
For npx users: You must specify the credentials file path using GOOGLE_OAUTH_CREDENTIALS
Verify file paths are absolute and accessible
Authentication Errors:
Ensure your credentials file contains credentials for a Desktop App type
Verify your user email is added as a Test User in the Google Cloud OAuth Consent screen
Try deleting saved tokens and re-authenticating
Check that no other process is blocking ports 3500-3505
Build Errors:
Run npm install && npm run build again
Check Node.js version (use LTS)
Delete the build/ directory and run npm run build
"Something went wrong" screen during browser authentication
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Perguntas
Como instalo @enterpret/google Calendar?
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
@enterpret/google Calendar precisa de uma chave de API?
Este registro não lista nenhuma variável de ambiente obrigatória.
Qual transporte @enterpret/google Calendar usa?
@enterpret/google Calendar roda localmente via stdio.
Quando @enterpret/google Calendar foi verificado pela última vez?
Última verificação: 2026-11-11. Enterpret fork of the Google Calendar MCP server with broker-supplied OAuth bearer support