Schedule meetings on Breaker1 over MCP

Endpoint

https://ssesweekhcliexsnshum.supabase.co/functions/v1/mcp

JSON-RPC 2.0 over HTTP POST (MCP Streamable HTTP). Send Accept: application/json, text/event-stream and Content-Type: application/json on every request.

Tools

• find_user

  Look up a Breaker1 host by email or @username. Returns their booking URL, available meeting durations, and whether they require approval.

• get_availability

  Return mutually-free meeting slots in UTC for a host, given a duration and date range. Working hours, time zone, buffers, and existing bookings are already applied.

• propose_times

  Return N mutually-free slots already formatted for a natural-language reply ("Tue 2pm PT, Wed 10am PT…"). Use when a user says "find a time with @matt next week".

• create_booking

  Book a slot. Status returns 'confirmed' or 'pending' if the host requires approval. Creates the calendar event + Google Meet link and emails both sides.

• cancel_booking

  Cancel a booking using its id + the guest_email it was booked under. Sends the cancellation email and cleans up the host's calendar event.

Quick test

curl -X POST https://ssesweekhcliexsnshum.supabase.co/functions/v1/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/list"
  }'

Discovery

• /.well-known/mcp.json — MCP server descriptor
• /.well-known/agent.json — agent-friendliness declaration & rate limits
• /llms.txt — short summary for LLMs

Rate limits & etiquette

• 120 calls/hour per IP across all tools
• 10 booking attempts/hour per IP
• 30 calls/hour per IP per target host
• Pass agent_id on create_booking (e.g. "claude.ai") so hosts can see who booked them
• Web Bot Auth (RFC 9421) Signature-Agent headers are recorded for observability; full key verification is on the roadmap