IonBin
All pages
Search

Reclaim

Scheduling
SOPsOps MCPAPI/CLI

Independent review. Unpaid; no partnership with Reclaim. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.

Schedules focus time, tasks and habits around meetings. Reclaim 2.0 has an official MCP server for supported AI clients; proposed scheduling changes go to Preview Mode for review before application.

The Ion perspective

The five-point review

Judgment, not a score. Documentation checked 2026-10-18.

Value
Schedules focus time, tasks and habits around meetings. Reclaim 2.0 has an official MCP server for supported AI clients; proposed scheduling changes go to Preview Mode for review before application.
Differentiation
Documented fit: Busy operators whose task list never fits their calendar. Uniqueness is not established.
Replaceability and switching
Compare Cal.com. Not drop-in replacements. Export completeness and migration effort remain unverified.
Ease and technical aptitude
Consider the fit limits: People who only need a basic booking link and do not need automatic calendar planning. Setup effort has not been scored.
Interoperability and portability
See documented MCP, API and import routes below. Import does not prove export; API access does not prove a complete migration path. Check action scope, plans and portability.

Connections: MCP connections · APIs · Portability and vendor lock-in.

Best for
  • Busy operators whose task list never fits their calendar
Not for
  • People who only need a basic booking link and do not need automatic calendar planning

Top use cases

In depth

Plans

Lite is free. Annual billing lists Starter at US$10, Business at US$15 and Enterprise at US$22 per seat/month; monthly Starter and Business are US$12 and US$18. Starter supports up to 10 seats, Business up to 100, and Enterprise over 100. Business includes webhooks. Promotional banners may have separate eligibility and expiry terms. Checked 2026-10-18. source ↗

Preview Mode

The MCP guide applies to Reclaim 2.0: scheduling changes are staged for review before application. Reclaim’s Claude guide lists Starter, Business and Enterprise access and distinguishes the client’s per-tool permission controls from Reclaim’s Preview Mode. Confirm the app version and plan before connecting. source ↗

How to use it with AI

How Reclaim connects to each AI platform: native connector or MCP, API through code the agent writes, browser control, or file upload.

PlatformMCP / connectorAPI (agent-written code)BrowserUpload / export
Claude (incl. Claude Code) Not documented Documented Claude web, Desktop and Code integration; Reclaim 2.0 and eligible plan required. A named plugin, skill or CLI does not by itself establish an MCP/native connector pairing. Verify the route and client setup. Reclaim named integration docs ↗Reclaim MCP / connector evidence ↗Claude (incl. Claude Code) MCP docs ↗ Not documented Claude (incl. Claude Code): Claude Code edits files and runs commands Reclaim publishes an API, but this pairing still needs network, authentication and execution-scope checks. Reclaim API ↗Claude (incl. Claude Code) docs ↗ Inferred Claude Code with the Claude in Chrome extension (Chrome, Edge and other Chromium browsers). Reclaim is a web app; the pairing itself is not documented. Claude (incl. Claude Code) browser docs ↗ Not documented Verify which side exports and which imports, supported formats and permissions. Reclaim's recorded upload/import status is to-verify; Claude (incl. Claude Code)'s file status is yes. These flags do not establish a file-transfer route. Claude (incl. Claude Code) file docs ↗
OpenAI Codex Not documented Reclaim has an official MCP server and OpenAI Codex supports MCP, but Reclaim's docs don't name this pairing. Auth setup may differ. Reclaim MCP docs ↗OpenAI Codex MCP docs ↗ Not documented OpenAI Codex: Edits files and runs commands locally; cloud tasks run in isolated workspaces Reclaim publishes an API, but this pairing still needs network, authentication and execution-scope checks. Reclaim API ↗OpenAI Codex docs ↗ Inferred Only in the ChatGPT desktop app; not in the Codex CLI or IDE extension. Reclaim is a web app; the pairing itself is not documented. OpenAI Codex browser docs ↗ Not documented Verify which side exports and which imports, supported formats and permissions. Reclaim's recorded upload/import status is to-verify; OpenAI Codex's file status is yes. These flags do not establish a file-transfer route. OpenAI Codex file docs ↗
Google Antigravity Not documented Reclaim has an official MCP server and Google Antigravity supports MCP, but Reclaim's docs don't name this pairing. Auth setup may differ. Reclaim MCP docs ↗Google Antigravity MCP docs ↗ Not documented Google Antigravity: Agents edit code and run tasks Reclaim publishes an API, but this pairing still needs network, authentication and execution-scope checks. Reclaim API ↗Google Antigravity docs ↗ Inferred The /browser guide documents App and CLI support through Chrome DevTools MCP; the overview comparison conflicts on CLI availability. IDE browser features are separate. Reclaim is a web app; the pairing itself is not documented. Google Antigravity browser docs ↗ Not documented Verify which side exports and which imports, supported formats and permissions. Reclaim's recorded upload/import status is to-verify; Google Antigravity's file status is yes. These flags do not establish a file-transfer route. Google Antigravity file docs ↗

Reclaim's docs also name: ChatGPT.

Confirmed is reserved for evidence of the specific connection route. The current named integrations include plugins, skills and CLIs, so a named platform alone does not confirm MCP or a native connector. Inferred means each side documents a relevant capability, but no document describes the pairing. Code execution still needs network and credential access; file handling still needs a compatible format and transfer direction. Not documented means the records do not establish the route. IonBin has not tested these pairings. Recorded Oct 18, 2026.

Agent compatibility

MCPAPI/CLI File import?
LevelStatusDetail / source
Native connector / MCPYes Official docs ↗ (server https://mcp.reclaim.ai; changes staged in Preview Mode)
API / CLIYes Official docs ↗ (public OpenAPI 3.0.1 specification, API version 0.1; account permissions and supported third-party use need confirmation)
Browser / manualNo Browser access is recorded alongside a documented programmatic route.
File upload / importTo verify A file-import route was not established in the reviewed documentation; task integrations are separate from file upload.

Recorded Oct 18, 2026. Setup and plan limits vary; check the vendor's docs. How levels are assigned.

Appears in these proposed stacks

Connection capabilities to compare

An official MCP server is documented for this tool. These platforms separately document MCP client support: ChatGPT, Claude, Cursor, Gemini (Google), Google Antigravity, Grok, Grok Bot, Lindy, LM Studio, Mistral Vibe, OpenAI Codex. This inventory does not establish compatible transport, authentication or actions for a pairing. Check the connection matrix and linked sources.

Automation hubs to assess for a custom API connection: Gumloop, Make, n8n, Zapier. Verify credentials, supported requests, limits and error handling; no configured integration is implied.

Workflows using this tool

Review

No long-form review yet. Verdict is based on research, not hands-on testing.

Alternatives

Cal.com

Scheduling

Scheduling with booking pages, routing forms and an API. Its hosted or local MCP server lets authorized AI assistants list, create, reschedule or cancel bookings. Cal.diy is a separate community edition with different capabilities.

MCPAPI/CLIFile import
Sales