Google Calendar runs on your own machine — the client starts it, so there is no endpoint to ping. 144 installs a week from npm. Last commit 30 Aug 2026.
MCP server for Google Calendar integration with service account support and domain-wide delegation.
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
этот файл ставится пользователю, но в репозитории его нет
const initProcess = spawn(this.claudeCodePath, args, {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add google-calendar -e 'GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL=<GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL>' -e 'GCAL_SERVICE_ACCOUNT_PRIVATE_KEY=<GCAL_SERVICE_ACCOUNT_PRIVATE_KEY>' -e 'GCAL_IMPERSONATE_EMAIL=<GCAL_IMPERSONATE_EMAIL>' -- npx -y google-calendar-workspace-mcp-server
{
"mcpServers": {
"google-calendar": {
"command": "npx",
"args": [
"-y",
"google-calendar-workspace-mcp-server"
],
"env": {
"GCAL_IMPERSONATE_EMAIL": "<GCAL_IMPERSONATE_EMAIL>",
"GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL": "<GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL>",
"GCAL_SERVICE_ACCOUNT_PRIVATE_KEY": "<GCAL_SERVICE_ACCOUNT_PRIVATE_KEY>"
}
}
}
}
[mcp_servers.google-calendar]
command = "npx"
args = ["-y", "google-calendar-workspace-mcp-server"]
env = { GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL = "<GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL>", GCAL_SERVICE_ACCOUNT_PRIVATE_KEY = "<GCAL_SERVICE_ACCOUNT_PRIVATE_KEY>", GCAL_IMPERSONATE_EMAIL = "<GCAL_IMPERSONATE_EMAIL>" }
{
"mcpServers": {
"google-calendar": {
"command": "npx",
"args": [
"-y",
"google-calendar-workspace-mcp-server"
],
"env": {
"GCAL_IMPERSONATE_EMAIL": "<GCAL_IMPERSONATE_EMAIL>",
"GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL": "<GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL>",
"GCAL_SERVICE_ACCOUNT_PRIVATE_KEY": "<GCAL_SERVICE_ACCOUNT_PRIVATE_KEY>"
}
}
}
}
{
"servers": {
"google-calendar": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"google-calendar-workspace-mcp-server"
],
"env": {
"GCAL_IMPERSONATE_EMAIL": "<GCAL_IMPERSONATE_EMAIL>",
"GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL": "<GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL>",
"GCAL_SERVICE_ACCOUNT_PRIVATE_KEY": "<GCAL_SERVICE_ACCOUNT_PRIVATE_KEY>"
}
}
}
}
Put your own values in place of
<GCAL_SERVICE_ACCOUNT_CLIENT_EMAIL> (Service account email address from Google Cloud Console), <GCAL_SERVICE_ACCOUNT_PRIVATE_KEY> (Service account private key in PEM format from Google Cloud Console), <GCAL_IMPERSONATE_EMAIL> (Email address of the user whose calendar to access via domain-wide delegation).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
ENABLED_TOOLGROUPS (Comma-separated list of tool groups to enable (readonly or readwrite)).
MCP server for Google Docs integration with OAuth2 and service account support.
Streamable HTTP MCP server for Google Calendar and Sheets with OAuth login.
Google Workspace MCP server for Gmail, Calendar, Drive, Docs, Sheets, Slides, Contacts, and more
MCP server for Google Workspace — Sheets, Drive, Docs (HTML or Markdown), Calendar, and Gmail.
Google Docs MCP server with full tab support, markdown extraction, and batch updates.
Read and write Google Sheets with your own service account: list tabs, read, append, update, export.
Hosted Google Ads MCP server for Claude, ChatGPT and Cursor, with each action switched per account.
Multi-account Google Workspace MCP — Gmail, Calendar, Drive, Sheets, Docs with smart routing.
Answers built from our own checks of this server.