What authentication methods are supported?
Two methods: Google Cloud OAuth (recommended, requires a Google Cloud project) and direct authentication (simpler, no Google Cloud setup, but subject to Google’s security policies).
@Jackson88
基本情報
Model Context Protocol (MCP) server for Claude Desktop connecting to Google Calender using Google Calendar API
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"google-calendar": {
"command": "npx",
"args": [
"-y",
"google-calendar-mcp"
],
"env": {
"GOOGLE_CLIENT_ID": "<your-client-id>",
"GOOGLE_CLIENT_SECRET": "<your-client-secret>",
"GOOGLE_REDIRECT_URI": "http://localhost:3000/auth/callback"
},
"description": "Google Calendar MCP server using npx"
}
}
}ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
上のボタンで一時的なサンドボックスでこのサーバーを実行し、ツール一覧を取得できます。
A TypeScript-based Model Context Protocol (MCP) server that allows Claude Desktop to connect to and interact with Google Calendar.
Clone the repository, install dependencies, configure the .env file with the chosen authentication method (Google Cloud OAuth or direct), then run the server in development or production mode. Authenticate with Google via the provided endpoints, and configure Claude Desktop’s settings to connect to the server via MCP.
Two methods: Google Cloud OAuth (recommended, requires a Google Cloud project) and direct authentication (simpler, no Google Cloud setup, but subject to Google’s security policies).
Node.js v16 or higher, npm or yarn, a Google account with Calendar access, and OAuth 2.0 credentials if using the Google Cloud method.
As of April 2025, Claude Desktop may have limited or no support for external MCP connections. Testing indicates the current version does not connect to this server. The server itself functions independently for direct API use.
Tokens are saved locally in files. They should be kept secure and never committed to version control.
Yes. The project includes a Docker Compose configuration for containerized deployment.
Google Cloud OAuth follows standard OAuth 2.0 and is more secure and reliable for production. Direct authentication is simpler for personal/development use but may stop working if Google changes its authentication requirements.

Draft, find, negotiate, analyze and sign contracts in fynk. Create documents via AI, from templates or PDFs, manage parties, signatories and fields, and send for e-signature, all with your own fynk permissions via OAuth.

Built for companies. Ready for AI agents. PaperOffice is the headless DMS your agent can actually operate: one MCP endpoint to search, read, upload, extract and sign business documents — no UI, no glue code. AI-OCR, invo

A remote LinkedIn MCP server. Connect Claude to LinkedIn and run campaigns, content, leads and inbox through 80+ tools — with scoped keys, preview-and-confirm before anything sends, and hard daily caps.

Run your TRMNL ePaper displays from any AI agent: check on devices, plan playlists and build new screens from your own data.
EQIQs brings working-style and compatibility insights into Claude. Managers and coaches can take or send a short assessment, compare two people, get a read on a team of up to 12, prepare for meetings with tips that fit t
コメント