Schedule MCP Server
Integrates Google Calendar and Notion to enable Claude to manage your schedule, plan tasks, detect conflicts, and keep appointments and tasks synchronized.
README
schedule-mcp
Personal schedule management MCP server. Connects Google Calendar, Notion Appointments, and Notion Tasks so Claude can help you plan your week, detect conflicts, schedule task work blocks, and keep your calendar and Notion in sync.
Architecture
Google Calendar ←→ Claude (sync layer) ←→ Notion Appointments
↓
Notion Tasks
(linked via GCal event description)
Key design decisions:
- Google Calendar is the source of truth for time
- Notion Appointments is the source of truth for context (type, notes, rich metadata)
- Notion Tasks are linked to calendar events via Notion URLs in the event description (no bidirectional sync needed)
- A
GCal Event IDfield on each Notion Appointment prevents duplicate sync - A
GCal Series IDfield for linking Notion Appointments with recurring GCal events
Tools
| Tool | Source | What it does |
|---|---|---|
gcal_list_calendars |
GCal | List all your calendars |
gcal_get_events |
GCal | Fetch events in a date range |
gcal_create_event |
GCal | Create a calendar event |
gcal_update_event |
GCal | Update an existing event |
gcal_delete_event |
GCal | Delete an event |
gcal_find_free_slots |
GCal | Find available time blocks |
notion_get_appointments |
Notion | Query appointments with filters |
notion_create_appointment |
Notion | Add an appointment to Notion |
notion_update_appointment |
Notion | Update an appointment |
notion_get_appointment_by_gcal_id |
Notion | Check if a GCal event is already in Notion |
notion_get_tasks |
Notion | Query tasks with filters |
notion_get_overdue_tasks |
Notion | Get all overdue tasks |
notion_create_task |
Notion | Add a new task |
notion_update_task |
Notion | Update a task |
schedule_week_overview |
All | Unified week view: events, appointments, tasks due, overdue tasks |
schedule_task_block |
GCal + Notion | Schedule a work block for a task |
schedule_find_conflicts |
GCal | Detect overlaps and tight transitions |
Notion Database Schema
Appointments database — expected fields:
| Field | Type | Notes |
|---|---|---|
| Appointment | Title | Appointment name |
| Start | Date | Start datetime |
| End | Date | End datetime |
| Type | Select | Medical, Personal, Work, Other |
| Status | Status | Scheduled, In progress, Completed |
| Canceled | Select | Canceled, Not canceled |
| Recurring | Select | One-Time, Limited Recurring, Recurring |
| Notes | Rich text | Free-form notes |
| GCal Event ID | Rich text | Linked GCal event ID (prevents duplicate sync) |
| GCal Series ID | Rich text | Linked GCal series ID (for recurring events) |
Tasks database — expected fields:
| Field | Type | Notes |
|---|---|---|
| Task name | Title | Task name |
| Task Status | Select | Not started, In progress, Done, Archived, Overdue |
| Due | Date | Due date |
Setup
1. Prerequisites
- Python 3.11+
- uv (recommended) or pip
- A Google Cloud project with the Calendar API enabled
- A Notion integration with access to your Appointments and Tasks databases
2. Google Calendar API
- Go to Google Cloud Console
- Create a project (or use an existing one)
- Enable the Google Calendar API
- Go to APIs & Services → Credentials → Create Credentials → OAuth 2.0 Client ID
- Application type: Desktop app
- Download the JSON file → save as
~/.schedule_mcp/google_credentials.json(Windows:%USERPROFILE%\.schedule_mcp\google_credentials.json)
3. Notion Integration
- Go to https://www.notion.so/my-integrations
- Create a new integration (Internal, Read + Write content)
- Copy the Internal Integration Token
- In Notion, open your Appointments database →
...menu → Connections → add your integration - Do the same for your Tasks database
4. Configure Environment
# Linux/macOS
cp .env.example .env
# Windows (PowerShell)
Copy-Item .env.example .env
Then edit .env with your credentials.
5. Install and Run
# Using uv (recommended)
uv sync
uv run schedule-mcp
# Or with pip
pip install -e .
schedule-mcp
The first run will open a browser window for Google OAuth consent. After that, the token is saved and auto-refreshed.
6. Add to Claude MCP Config
Add this to %APPDATA%\Claude\claude_desktop_config.json (Windows) or ~/Library/Application Support/Claude/claude_desktop_config.json (macOS), merged into the top-level JSON object alongside any existing keys:
{
"mcpServers": {
"schedule": {
"command": "uv",
"args": ["run", "--project", "C:/Users/YOU/source/repos/schedule_mcp", "schedule-mcp"],
"env": {
"GOOGLE_TOKEN_FILE": "C:/Users/YOU/.schedule_mcp/google_token.json",
"GOOGLE_CREDENTIALS_FILE": "C:/Users/YOU/.schedule_mcp/google_credentials.json",
"NOTION_TOKEN": "your_token_here",
"NOTION_APPOINTMENTS_DB_ID": "your_notion_appointments_db_id_here",
"NOTION_TASKS_DB_ID": "your_notion_tasks_db_id_here",
"LOCAL_TIMEZONE": "America/Los_Angeles"
}
}
}
}
Replace YOU with your Windows username. On macOS, use ~ paths instead.
Example Claude Prompts
What does my week look like?
Do I have any conflicts or back-to-backs this week?
Find me 90 minutes of free time tomorrow morning for SeattleCouncilmatic work.
Schedule 2 hours for "Add transit data support to SeattleCouncilmatic"
on Thursday afternoon.
I have a dentist appointment Tuesday at 2pm — add it to both my calendar and Notion.
Show me all my medical appointments this month.
What tasks do I have due this week?
Development
# Verify syntax
python -m py_compile schedule_mcp/server.py
# Run with MCP Inspector for interactive testing
npx @modelcontextprotocol/inspector uv run schedule-mcp
Project Structure
schedule_mcp/
├── pyproject.toml
├── uv.lock
├── .env.example
├── README.md
└── schedule_mcp/
├── __init__.py
├── server.py # MCP server entry point
├── auth/
│ ├── __init__.py
│ └── google_auth.py # Google OAuth2 flow
├── clients/
│ ├── __init__.py
│ ├── gcal.py # Google Calendar API client
│ └── notion.py # Notion API client
└── tools/
├── __init__.py # Exports register_* functions
├── calendar.py # gcal_* MCP tools
├── appointments.py # notion_*appointment* MCP tools
├── tasks.py # notion_*task* MCP tools
└── schedule.py # schedule_* cross-source tools
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.