Outlook Calendar MCP Tool

Created By
merajmehrabia year ago
A Model Context Protocol (MCP) server that allows Claude to access and manage your local Microsfot Outlook calendar (Windows only).
Overview

What is Outlook Calendar MCP Tool?

The Outlook Calendar MCP Tool is a Model Context Protocol (MCP) server that enables Claude to access and manage your local Microsoft Outlook calendar on Windows systems.

How to use Outlook Calendar MCP Tool?

To use the tool, install it via npm or run it directly using npx. Configure it in your MCP settings for Claude, and then you can interact with your Outlook calendar through various commands.

Key features of Outlook Calendar MCP Tool?

  • View calendar events and details, including attendee status.
  • Create and manage calendar events and meetings.
  • Find free time slots for scheduling and identify optimal meeting times.
  • Support for multiple calendars within your Outlook profile.

Use cases of Outlook Calendar MCP Tool?

  1. Scheduling meetings by finding free time slots.
  2. Managing multiple calendars for different projects or teams.
  3. Automating event creation and updates through commands.

FAQ from Outlook Calendar MCP Tool?

  • Is this tool compatible with all versions of Outlook?

The tool is designed for the Microsoft Outlook desktop client on Windows only.

  • Do I need to install anything else?

Yes, you need Node.js and npm installed on your system.

  • Is my calendar data sent to external servers?

No, all operations are performed locally on your computer without sending data externally.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
merajmehrabi
Star
2
Language
VBScript
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
Crevio

2 days ago