MCP server (Model Context Protocol, Streamable HTTP)
JSON-RPC 2.0: initialize (protocol versions 2025-06-18, 2025-03-26, 2024-11-05; the client's version is echoed when supported, else the latest), tools/list (annotations, outputSchema), tools/call (structuredContent). Tools: find_common_slots, create_meeting, get_meeting, get_meeting_availability, suggest_time, respond_to_suggestion, set_manual_availability, get_manual_availability, list_my_meetings, list_my_event_types, get_booking_slots, book_slot, list_my_bookings, cancel_booking, reschedule_booking. Every request (initialize and tools/list included) needs a Bearer mn_… token; without one the answer is HTTP 401 with WWW-Authenticate: Bearer resource_metadata="<origin>/.well-known/oauth-protected-resource/mcp". Tools that change data need the write scope (insufficient_scope tool error otherwise). Connectors (Claude.ai, ChatGPT) sign in with OAuth 2.1 (see /.well-known/oauth-protected-resource/mcp); header clients (Claude Code, Cursor) send a PAT.
Request
- Base URL: https://whenmeet.me
- URL: https://whenmeet.me/mcp
- Auth: HTTP bearer
Response
JSON-RPC response.
Changes
No recorded changes to this operation across all 1 revision of this API.