Stop building scheduling logic from scratch.
Quick Start
Add to your mcpServers config:
{
"mcpServers": {
"meeting-scheduler": {
"url": "https://your-cloud-run-url/mcp"
}
}
}
Before / After
Before: Write custom date arithmetic, timezone offset tables, and conflict detection by hand for every scheduling feature.
After:
Input:
{
"date": "2024-03-15",
"duration_minutes": 60,
"busy_blocks": [
{ "start": "2024-03-15T09:00Z", "end": "2024-03-15T10:30Z" },
{ "start": "2024-03-15T13:00Z", "end": "2024-03-15T14:00Z" }
],
"work_start": "09:00",
"work_end": "18:00"
}
Output:
{
"found": true,
"slot_start": "2024-03-15T10:30",
"slot_end": "2024-03-15T11:30"
}
Tools
| Tool | What it does |
|---|---|
schedule_meeting |
Create a validated meeting record with a unique ID and computed ISO timestamps |
check_availability |
Detect whether a proposed time slot conflicts with existing busy blocks |
find_available_slot |
Find the first open slot on a day that fits within working hours |
format_meeting_invite |
Generate a plain-text or HTML invitation ready to send by email or chat |
convert_meeting_time |
Convert a meeting time between any two IANA timezones, returning both and UTC |
calculate_meeting_duration |
Get exact duration in minutes, decimal hours, and a readable label |
generate_recurring_dates |
Generate dates for a recurring series: daily, weekly, biweekly, or monthly |
Who is this for?
- App developers who need scheduling logic in their product without building a calendar engine from scratch
- AI assistants that schedule meetings on behalf of users and need structured, validated time outputs
- Automation builders connecting calendar APIs who need clean, reliable date and time math utilities
Health Check
GET /health
Response:
{ "status": "ok", "server": "meeting-scheduler", "version": "1.0.0", "tools": 7 }
Built by
License
MIT
