Which AI clients work with the WhenMeet.me MCP server?
Any MCP client that can connect to a remote (Streamable HTTP) server and send a bearer token header. Scripts can use the HTTP API instead.
Schedule with AI agents — remote MCP server and HTTP API
WhenMeet.me runs a remote MCP server at /mcp and a documented HTTP API (/docs, /openapi.json), so AI assistants and scripts can find common free times, create meetings, negotiate alternatives and book through anyone’s booking link.
What WhenMeet.me does with MCP & API for AI agents
- Remote MCP server at /mcp (Streamable HTTP, JSON-RPC).
- Tools: find_common_slots, create_meeting, get_meeting, get_meeting_availability, suggest_time, respond_to_suggestion, set_manual_availability, get_manual_availability, list_my_event_types, get_booking_slots and book_slot.
- Authenticated with a personal access token sent as “Authorization: Bearer …”; create one under Settings → API tokens & MCP.
- Tools that would be meaningless without a connected calendar (find_common_slots, create_meeting, book_slot) refuse to run without a token.
- The same operations are available over HTTP: OpenAPI 3.1 at /openapi.json, human docs at /docs.
How to set it up
- Sign in and connect your calendar.
- Create a personal access token under Settings → API tokens & MCP.
- Add https://whenmeet.me/mcp as a remote MCP server in your AI client, with the header Authorization: Bearer <token>.
- Ask the assistant to find a time or book a slot.
MCP & API for AI agents integration FAQ
Can an agent see my calendar events?
No. Tools work on availability and meeting data from WhenMeet.me, not calendar event lists. Google and Microsoft availability uses Free/Busy; public iCloud feeds are parsed temporarily and only busy intervals are retained.