Enterprise DNAEnterprise DNA

MCP Servers

takumi0706/google-calendar-mcp

Google Calendar MCP server for Claude Desktop integration

Our verdict

Not reviewed yet

We have not reviewed takumi0706/google-calendar-mcp yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About takumi0706/google-calendar-mcp

An MCP server that integrates Google Calendar with Claude Desktop via the Model Context Protocol. It enables Claude to read, create, and manage calendar events through natural language commands. Built in TypeScript, it serves as a bridge between Google's calendar API and the Claude Desktop interface.

Best for

Developers and power users who want to manage Google Calendar via natural language in Claude Desktop

Use cases

  • Scheduling events and meetings through chat conversations
  • Checking calendar availability and upcoming events
  • Creating, modifying, or deleting calendar entries on demand

Notes

56 stars on GitHub. Last updated 2025-10-22. Licensed MIT.

Pros

  • Enables direct calendar management from Claude Desktop without switching apps
  • Leverages the full Google Calendar API through a structured MCP interface
  • Simple setup for users already comfortable with OAuth and API credentials

Cons

  • Requires setting up Google API credentials and OAuth consent screen
  • Dependent on the MCP protocol and Claude Desktop (not usable standalone)
  • Limited to the features exposed by the current MCP server implementation

Key facts

What we have checked

Days since the last commit
80
Checked GitHub
GitHub forks
11
Checked GitHub
GitHub stars
59
Checked GitHub
Days to a first reply on issues
579.4
Checked GitHub
Open issues
0
Checked GitHub
Releases in the last 90 days
1
Checked GitHub

Each value shows when we last confirmed it and where it came from. Values we have not confirmed are left out, never guessed.

How to use

How to set it up

As the listing publishes it. We have not run this install.

Install

npx @takumi0706/google-calendar-mcp@2.0.0

Tools exposed

  • getEvents
  • createEvent
  • updateEvent
  • deleteEvent
  • authenticate

Clients the listing names (not checked here)

Claude Desktop

Example client config

{
  "mcpServers": {
    "google-calendar": {
      "command": "npx",
      "args": [
        "-y",
        "@takumi0706/google-calendar-mcp"
      ],
      "env": {
        "GOOGLE_CLIENT_ID": "your_client_id",
        "GOOGLE_CLIENT_SECRET": "your_client_secret",
        "GOOGLE_REDIRECT_URI": "http://localhost:4153/oauth2callback"
      }
    }
  }
}

Install

Add takumi0706/google-calendar-mcp to your client

Not verified yet

No install recipe yet. We write one for Claude Code, Claude Desktop, Cursor, VS Code, Codex and ChatGPT when the server is in the official MCP registry with a package or remote address we can use.

Until then, follow the project's own README, or the setup the listing publishes under How to set it up.

Works with

What takumi0706/google-calendar-mcp connects to

No confirmed connections yet. A product appears here when the server's registry name, repo, homepage or name ties it to that product, and a client appears when we have an install recipe for it.

Stars and usage

How takumi0706/google-calendar-mcp is growing

GitHub stars

59 to 59

stars. 31 Oct 2026 to 6 Nov 2026, 2 readings.

Source: GitHub. Checked .

Health and security

Is takumi0706/google-calendar-mcp looked after, and what do its setup files show

Health score

33 out of 100

Does someone look after this repository? It does not say the code is good or safe. Worked out from GitHub signals checked . How it is worked out

PartPointsWhat we saw
Recent activity25.5 of 30Last push 80 days ago
Releases7.5 of 151 release in 90 days
Issue replies0 of 20First reply in 579.4 days (median)
Maintainer0 of 15Owned by a single user
Official source0 of 20Community server

Security check static checks

100 out of 100

Reads what is published about the server: package advisories, licence, secrets in the documented setup and tool permissions. Nothing is installed or run, so this is not a security assessment. Checked by edna-static-v1 npm:@takumi0706/google-calendar-mcp@2.0.0. What it checks

Licence: MIT

  • Note Asks for GOOGLE_CLIENT_SECRET through environment variables.
  • Note The lab has not recorded this server's tool list yet, so tool permissions were not checked.
Tool permissions (3)
  • GOOGLE_CLIENT_ID, environment variable it asks for
  • GOOGLE_CLIENT_SECRET, environment variable it asks for (a secret)
  • GOOGLE_REDIRECT_URI, environment variable it asks for

Sources

Where this comes from

  • GitHubRegistry

    Checked · Days since the last commit, GitHub forks, GitHub stars, Days to a first reply on issues, Open issues, Releases in the last 90 days

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Pairs with

Other entries in the index that connect to this one. Click through to see the chain.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.