WhenMeet.me
Server Details
Group meeting scheduler: Rank everyone’s available times across Google and Outlook, book Meet or Teams meetings between different organizations.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 4.2/5 across 8 of 8 tools scored. Lowest: 3.6/5.
Each tool targets a distinct operation: creating meetings, finding slots, manual availability CRUD, reading meetings, group availability, responding to suggestions, and proposing times. No two tools overlap in purpose.
All tool names follow a consistent verb_noun pattern (e.g., create_meeting, get_meeting_availability, set_manual_availability). No mixed conventions or vague verbs.
8 tools is well-scoped for a meeting scheduling service. Each tool serves an essential function without unnecessary bulk or missing critical operations.
Covers core workflows: create, read, find slots, manual availability, suggest/respond. Minor gaps like updating or deleting meetings are absent but not critical for the intended use case.
Available Tools
8 toolscreate_meetingInspect
Confirm a meeting: writes the event into the authenticated host’s calendar with an optional Google Meet/Teams link, emails invites with an ICS attachment, and returns the share URL (/m/). Requires authentication.
| Name | Required | Description | Default |
|---|---|---|---|
| tz | No | IANA zone used to format times in invite emails. | |
| title | No | ||
| endsAt | Yes | unix ms | |
| startsAt | Yes | unix ms | |
| conference | No | Omit for no conference link. | |
| participants | Yes |
find_common_slotsRead-onlyInspect
Rank the best meeting times for the given participants, merging live Google/Microsoft calendar data, hand-marked availability and the heat-map sources. Each participant is filtered (Mon–Fri, waking hours) and scored in their OWN timezone; scores factor in buffer time around existing meetings and prefer sooner slots. Returns up to 8 slots: everyone-free slots first (allFree:true), then — only if there are too few — the best compromise slots (allFree:false) with a freeCount. Defaults to the next 14 days. Requires authentication.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | Window end, unix ms. Default: now + 14 days. | |
| tz | No | Requester IANA zone, e.g. Europe/Warsaw — the fallback zone for participants whose own timezone is unknown, and the zone for the round-hour scoring bonus. | |
| from | No | Window start, unix ms. Default: now. | |
| durationMin | No | Meeting length. Default 30. | |
| participants | Yes | Participant emails (the authenticated user is the host and should be included). |
get_manual_availabilityRead-onlyInspect
Read previously hand-marked free slots for an email within a window.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | ||
| from | Yes | ||
| Yes |
get_meetingRead-onlyInspect
Read a meeting by its share-link id (the UUID from /m/): time, title, conference URL, host, and any proposed alternate times with their status.
| Name | Required | Description | Default |
|---|---|---|---|
| meetingId | Yes |
get_meeting_availabilityRead-onlyInspect
Aggregated group availability for an existing meeting (the symmetric heat-map): per-30-min-slot counts of how many participants are free, plus ranked slots (per-participant timezones, buffer + soonness scoring, allFree:true everyone-free slots and allFree:false compromise slots). Individual calendars are never exposed. No auth needed — the meeting id is the capability.
| Name | Required | Description | Default |
|---|---|---|---|
| to | No | unix ms. Default: now + 14 days. | |
| tz | No | ||
| from | No | unix ms. Default: now. | |
| meetingId | Yes | ||
| durationMin | No |
respond_to_suggestionInspect
Accept or decline a proposed alternate time. Accepting moves the meeting (calendar event included) and re-sends invites. Only the meeting host may call this — requires authentication.
| Name | Required | Description | Default |
|---|---|---|---|
| action | Yes | ||
| meetingId | Yes | ||
| suggestionId | Yes |
set_manual_availabilityInspect
Publish hand-marked FREE time slots for an email address (the no-calendar fallback, e.g. Apple iCloud users). Replaces previously marked slots inside the window; the group heat-map updates immediately. Authenticated callers (Bearer PAT) skip the bot challenge; an anonymous caller must pass a Cloudflare Turnstile token in turnstileToken (only required when the server is configured with a Turnstile secret).
| Name | Required | Description | Default |
|---|---|---|---|
| Yes | |||
| windowTo | Yes | unix ms | |
| freeSlots | Yes | ||
| windowFrom | Yes | unix ms | |
| turnstileToken | No | Cloudflare Turnstile token; required for anonymous callers when a Turnstile secret is configured. |
suggest_timeInspect
Propose a different time for an existing meeting on behalf of a guest. The host is notified by email and can accept or decline. Authenticated callers (Bearer PAT) skip the bot challenge; an anonymous caller must pass a Cloudflare Turnstile token in turnstileToken (only required when the server is configured with a Turnstile secret).
| Name | Required | Description | Default |
|---|---|---|---|
| endsAt | Yes | unix ms | |
| message | No | ||
| startsAt | Yes | unix ms | |
| meetingId | Yes | ||
| suggestedBy | Yes | Email of the person proposing. | |
| turnstileToken | No | Cloudflare Turnstile token; required for anonymous callers when a Turnstile secret is configured. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!