MCP server for cross-organisation meeting scheduling via Google and Microsoft calendars
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"meeting-scheduler-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# meeting-scheduler-mcp An MCP server that schedules meetings across organisations by querying free/busy calendars from Google and Microsoft accounts — without exposing anyone's calendar data to the other party. Works with Claude Desktop, Cursor, and any MCP-compatible client. --- ## How it works You configure one **primary** account (the calendar where events are created and invites sent) and one or more **shadow** accounts (read-only access to query free/busy within another org's tenant). Claude uses the MCP tools to: 1. Find slots where everyone is free 2. Book the meeting from your primary calendar 3. Reschedule or cancel if plans change --- ## Prerequisites ### Google account 1. Go to [Google Cloud Console → APIs & Services → Credentials](https://console.cloud.google.com/apis/credentials) 2. Create a project (or use an existing one) 3. Enable the **Google Calendar API** 4. Create an **OAuth client ID** — application type: **Desktop app** 5. Download the client ID and client secret ### Microsoft / Outlook account 1. Go to [Azure Portal → App registrations](https://portal.azure.com/#view/Microsoft_AAD_RegisteredApps) 2. Register a new application — supported account types: **Accounts in any organizational directory and personal Microsoft accounts** 3. Under **Authentication**, add a **Mobile and desktop application** redirect URI: `http://localhost` 4. Note the **Application (client) ID** — no client secret needed for delegated auth --- ## Installation ### Recommended — zero install via uvx ```bash uvx meeting-scheduler-mcp setup ``` This runs the setup wizard without permanently installing anything. Once configured, Claude Desktop launches the server automatically using the same `uvx` command. ### Alternative — pip ```bash pip install meeting-scheduler-mcp meeting-scheduler setup ``` --- ## Setup wizard Run the wizard once to configure your accounts and authorise them: ``` $ uvx meeting-scheduler-mcp setup Meeting Scheduler — Setup Wizar…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.