MCP iCal Server

Created By
Omar-V2a year ago
A Model Context Protocol Server that allows you to interact with your MacOS Calendar through natural language.
Overview

What is MCP iCal Server?

MCP iCal Server is a Model Context Protocol Server that allows users to interact with their macOS Calendar using natural language, transforming calendar management into a conversational experience.

How to use MCP iCal Server?

To use MCP iCal Server, set it up with an MCP-compatible client like Claude for Desktop, and then you can issue natural language commands to manage your calendar.

Key features of MCP iCal Server?

  • Natural language event creation and modification
  • Smart schedule management and availability queries
  • Support for multiple calendars and recurring events
  • Integration with Google Calendar when configured with iCloud

Use cases of MCP iCal Server?

  1. Scheduling meetings and events using simple language commands.
  2. Checking availability and upcoming events quickly.
  3. Modifying existing calendar events with natural language.

FAQ from MCP iCal Server?

  • Can I use MCP iCal Server with any calendar?

Yes! It works with macOS Calendar and can integrate with Google Calendar through iCloud.

  • Is there a specific client I need to use?

While it can work with any MCP-compatible client, Claude for Desktop is recommended for the best experience.

  • What are the prerequisites for using MCP iCal Server?

You need macOS with the Calendar app configured, the uv package manager, and an MCP client.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Omar-V2
Star
64
Language
Python
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)

a day ago