Reclaim.ai
by Reclaim.ai
Let an AI agent reschedule, cancel and create real Google Calendar and Outlook events — including meetings other people are attending. 28 tools, half of them writes, behind a staging gate that holds every change until you approve it in Reclaim's own app.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Reclaim.ai via MCP
https://mcp.reclaim.aiWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Reclaim.ai Tools & Capabilities (28)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The approval gate is a batch commit in another application. Reclaim states that applying sends all remaining staged changes at once. You can discard individual changes first, but there is no documented per-change confirmation at the moment of sending.
apply_changesis in the tool list, and the documentation does not explain it. Reclaim describes applying as an action you take in the Reclaim app and never describes committing through MCP, yet the tool is listed. Because the endpoint is gated we could not read its description, so whether an agent can commit its own staged changes is unresolved.- Smart Meetings are capped at five attendees. Reclaim documents them as designed for meetings with up to five people, and advises keeping large or fixed meetings as regular calendar events.
- Once applied, notifications are the calendar provider's, not Reclaim's. Reclaim describes standard Google Calendar notification emails to attendees when meetings are moved, rescheduled or cancelled, and states that meeting-change notifications cannot be disabled for Outlook users. Neither Reclaim nor the connector can suppress them after the fact.
- Staged changes go stale. Reclaim notes there is no hard limit on how many changes you stage or how far ahead they span, but recommends smaller batches applied promptly, because your live calendar and other people's availability keep changing while edits sit in preview.
- The permission grant cannot be narrowed meaningfully. Three scopes, one of which is
write, with no delete or per-feature axis. - We could not read tool schemas or safety annotations. The endpoint requires OAuth, so no parameter detail, no
readOnlyHintand nodestructiveHintare published here. Tool names come from Anthropic's directory snapshot; behaviour comes from Reclaim's documentation. - Reclaim 2.0 is in private beta. Reclaim's own overview states that 2.0 is currently in private beta and actively evolving, and its help centre files the 2.0 articles, including the Claude integration guide, under Beta features. The MCP connector is a 2.0 feature.
- Some Reclaim documentation describes version 1.0. Articles on rescheduling, locks and notifications carry an explicit banner stating they refer to 1.0 features. We have drawn the connector's behaviour from the 2.0 articles and flagged where a 1.0 source is used.
- Plan gates are not documented for the connector. Reclaim states it offers a free plan and that paid plans unlock additional features, but its 2.0 documentation does not name a plan requirement for MCP access specifically. We could not establish one either way.
Frequently asked questions
Can the Reclaim MCP server move a meeting that other people are attending?
Yes, when you ask it to. The tools reschedule_event, update_event and cancel_event reach real Google Calendar and Outlook events, and Reclaim lists scheduling on behalf of others as an MCP use case. What it will not do is move such a meeting unprompted: Reclaim states that Smart Meetings never reschedule automatically, because rescheduling involves other people.
Do attendees get an email when an AI agent moves my meeting?
Not until you apply the change, and then yes. Reclaim states that changes staged in Preview Mode are never written to Google or Outlook, so no notifications go out to attendees until you click Apply changes. Once applied, the calendar provider sends its standard invitation update to every attendee, exactly as a manual reschedule would.
Does everything an AI agent does go through an approval step first?
Yes for calendar changes. Reclaim documents that all changes made through MCP are staged in Preview Mode for review in the Reclaim app before applying, and the gate is automatic rather than opt-in. One caveat: an apply_changes tool exists in the connector's listing, and Reclaim's documentation never describes committing through MCP, so we could not establish what calling it does.
Can I approve some proposed changes and reject others?
Partly. Reclaim's Review and apply changes dialog lists every staged change as Added, Moved or Cancelled, and you can discard individual changes you do not want. But Reclaim states plainly that applying sends all remaining changes at once, so the final action is one batch commit rather than a per-change confirmation.
What can the Reclaim MCP server read from my calendar?
A great deal, including other people's information. The read tools cover your schedule, individual event details, contacts, organisational relationships, focus statistics and preferences. Because a work calendar holds meetings organised by colleagues, reading it exposes their meeting titles and attendee lists. Reclaim documents reading event titles, required and optional attendees, and Zoom AI Companion summaries.
Does the Reclaim MCP server work with Outlook as well as Google Calendar?
Yes, both. Reclaim's Claude setup guide lists a connected Google Calendar or Microsoft Outlook calendar as a requirement and states that Reclaim supports both. The same connector and the same endpoint serve either. One difference matters: Reclaim documents that meeting-change notifications cannot be disabled for Outlook users.
What OAuth permissions does Reclaim request for the MCP server?
Three, and they are coarse. Reading the server's own protected-resource descriptor on 2026-08-21 returned read, write and mcp. Reclaim's authorization server metadata advertises the same three. There is no separate delete scope and no per-feature scope, so a consent screen offers little to narrow beyond declining write entirely.
Is Reclaim 2.0 generally available, or still in beta?
Still in beta. Reclaim's overview states that 2.0 is currently in private beta and actively evolving, its help centre files the 2.0 articles under Beta features, and 1.0 users are told to contact support for early access. Older 1.0 articles remain published and are labelled as such, so behaviour described there may not match 2.0.
Sources
- Reclaim 2.0 + Claude integration (retrieved 2026-08-21) · retrieved 2026-08-21
- Reclaim 2.0 FAQ, including the MCP and Preview Mode sections (retrieved 2026-08-21) · retrieved 2026-08-21
- Reclaim.ai 2.0 overview (retrieved 2026-08-21) · retrieved 2026-08-21
- Reclaim 2.0 + ChatGPT integration (retrieved 2026-08-21) · retrieved 2026-08-21
- Manage notifications for Reclaim events (labelled Reclaim 1.0) (retrieved 2026-08-21) · retrieved 2026-08-21
- Reclaim help centre machine index,
llms.txt(retrieved 2026-08-21).robots.txton the same host permits these paths. · retrieved 2026-08-21 - Live OAuth posture check, RFC 9728 metadata at
https://mcp.reclaim.ai/.well-known/oauth-protected-resource— HTTP 200 anonymously, 2026-08-21 · retrieved 2026-08-21 - Authorization server metadata at
https://mcp.reclaim.ai/.well-known/oauth-authorization-serverand/.well-known/openid-configuration— both HTTP 200, 2026-08-21 · retrieved 2026-08-21 - Anthropic Connectors Directory entry (snapshot 2026-08-16) · retrieved 2026-08-16
- Reclaim support — support@reclaim.ai · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Productivity
- Developer
- Reclaim.ai
- Tools
- 28
- Domain
- mcp.reclaim.ai
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.