Invite someone to a calendar event by phone number and get their real email back when they accept.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
Scored across 2 tools
The two tools have clearly distinct responsibilities: one initiates the invite, the other retrieves its status. There is no overlap in purpose, so an agent can easily choose the right tool.
Both tools follow a consistent verb_noun pattern: send_calendar_invite and get_invite_status. The verbs are clear and the nouns describe the target, making the naming predictable and readable.
With only two tools, the set is minimal but directly covers the server's intended functionality of sending invites and checking their status. This is slightly under the typical 3-15 range but reasonable for a narrow use case.
The workflow of sending an invite and then checking/receiving the result is fully covered. Missing operations like cancellation are not explicitly required for this domain, so only minor gaps exist.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
send_calendar_invite3 fields changedInput schema / properties / phone / descriptionPrevious value: -"Recipient phone number, US/Canada. Accepts +15551234567, 15551234567, 5551234567, or (555) 123-4567."New value: +"Recipient phone number, US only. Accepts +15551234567, 15551234567, 5551234567, or (555) 123-4567."Input schema / properties / start / descriptionPrevious value: -"Event start. ISO 8601 datetime (e.g. 2026-06-15T14:00:00Z) or a date (2026-06-15) for an all-day event."New value: +"Event start. ISO 8601 datetime, or a date (2026-06-15) for an all-day event. PREFERRED for a timed event: local wall-clock time plus `timezone` (e.g. start \"2026-06-15T14:00:00\" with timezone \"America/Chicago\" = 2pm in Chicago). An offset (\"2026-06-15T14:00:00-05:00\") or UTC (\"2026-06-15T19:00:00Z\") is also accepted. A bare local time with NO timezone is read as UTC."Input schema / properties / timezoneAdded value: +{
+ "description": "IANA time zone of the event, e.g. \"America/Chicago\". Strongly recommended for any timed event: the invite SMS shows the time in this zone with its abbreviation (\"Mon, Jun 15, 2026 at 2:00 PM CDT\"), so the recipient reads the time the organizer actually meant. Without it a UTC time is shown labelled \"UTC\", which is correct but rarely what the recipient expects.",
+ "type": "string"
+}get_invite_statussend_calendar_inviteEvents by text: plan, invite people and groups, send reminders, track RSVPs. US and Canada numbers.
Outlook.com, Microsoft 365, Google calendars: free time, events, invitations, booking pages, polls.
Merged free/busy, find mutual time, propose bookings with human approval. Never event contents.
Manage Google, Outlook & Apple calendars and create private sync rules from chat.
Add one secure layer between your agents and this server.
