6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Let an AI agent reschedule, cancel and create real Calendar and Outlook events.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Reclaim.ai MCP server gives Claude, ChatGPT or any MCP-compatible agent write access to your real Google Calendar or Outlook calendar. Its 28 tools create, move and cancel events, protect focus time and manage tasks. Every calendar change is staged in Reclaim's Preview Mode and reaches attendees only when you approve it.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
apply_changes is 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.write, with no delete or per-feature axis.readOnlyHint and no destructiveHint are published here. Tool names come from Anthropic's directory snapshot; behaviour comes from Reclaim's documentation.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.
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.
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.
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.
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.
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.
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.
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.
llms.txt (retrieved 2026-08-21). robots.txt on the same host permits these paths. · retrieved 2026-08-21https://mcp.reclaim.ai/.well-known/oauth-protected-resource — HTTP 200 anonymously, 2026-08-21 · retrieved 2026-08-21https://mcp.reclaim.ai/.well-known/oauth-authorization-server and /.well-known/openid-configuration — both HTTP 200, 2026-08-21 · retrieved 2026-08-21Connect Reclaim.ai once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.