calendar-mcp-server

Created By
menma-at-herea year ago
MCP server to get google calendar
Overview

what is calendar-mcp-server?

calendar-mcp-server is a server application designed to retrieve event lists from Google Calendar using the MCP (Multi-Channel Protocol).

how to use calendar-mcp-server?

To use the calendar-mcp-server, you need to create an OAuth 2.0 client, obtain the authentication JSON, and configure the server settings as specified in the documentation. After setting up, you can run the server to access your Google Calendar events.

key features of calendar-mcp-server?

  • Retrieves event lists from Google Calendar.
  • Supports OAuth 2.0 for secure authentication.
  • Configurable server settings for integration with other applications.

use cases of calendar-mcp-server?

  1. Integrating Google Calendar events into custom applications.
  2. Automating event retrieval for personal or business use.
  3. Building a dashboard that displays upcoming events from Google Calendar.

FAQ from calendar-mcp-server?

  • What is required to set up the calendar-mcp-server?

You need to create an OAuth 2.0 client and configure the server settings as per the documentation.

  • Is there a specific environment required to run the server?

Yes, you need to have Node.js and TypeScript installed to run the server.

  • Can I use this server for multiple Google Calendar accounts?

Yes, you can configure it to access multiple accounts by setting up different OAuth clients.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
menma-at-here
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

10 hours ago