Reclaim.ai MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RECLAIM_API_KEY | Yes | Your Reclaim API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| reclaim_list_tasksA | Lists Reclaim.ai tasks. Default filter is 'active'. IMPORTANT NOTE ON 'COMPLETE' STATUS: In Reclaim.ai, tasks marked 'COMPLETE' mean their scheduled time block finished, but the user did NOT necessarily finish the work or mark it done. Treat 'COMPLETE' tasks as ACTIVE and PENDING unless they are also ARCHIVED or CANCELLED. If asked for 'active' or 'open' tasks, YOU MUST INCLUDE tasks with status 'COMPLETE'. |
| reclaim_get_taskA | Retrieves details for a specific Reclaim.ai task by its ID. Note on 'status': If 'COMPLETE', the scheduled time block ended, but the user has NOT marked the task done. It is still considered active/pending. |
| reclaim_create_taskA | Create a new task in Reclaim.ai. Requires at least a 'title'. Other fields like 'timeChunksRequired', 'priority', 'deadline', 'notes', 'eventCategory' are optional but recommended. |
| reclaim_update_taskA | Update specific fields of an existing Reclaim.ai task using its ID. This performs a PATCH operation – only provided fields are changed. IMPORTANT: Updating fields like 'notes' overwrites the existing content. To append to notes, you MUST first use 'reclaim_get_task' to fetch the current notes, then provide the full combined text (old + new) in the 'notes' field of this update call. |
| reclaim_mark_completeA | Marks a specific Reclaim.ai task as completed/done by the user. This usually archives the task. |
| reclaim_mark_incompleteA | Marks a specific Reclaim.ai task as incomplete (e.g., unarchives it, moves it back to the planner). |
| reclaim_delete_taskA | Permanently delete a specific Reclaim.ai task. This action cannot be undone easily. |
| reclaim_add_timeA | Adds scheduled time (in minutes) to a specific Reclaim.ai task. This blocks more time on the user's calendar. Use this if a task needs more time than allocated (e.g., timeChunksRemaining is 0 but work remains) or if a task has status 'COMPLETE' but the user indicates it's not finished. |
| reclaim_start_timerA | Starts the live timer for a specific Reclaim.ai task. This indicates the user is actively working on it now and helps log time accurately. |
| reclaim_stop_timerB | Stops the live timer for a specific Reclaim.ai task. Time tracked is automatically logged. |
| reclaim_log_workA | Logs completed work time (in minutes) against a specific Reclaim.ai task. This reduces the remaining time needed and affects future scheduling. |
| reclaim_clear_exceptionsA | Clears any scheduling exceptions (e.g., manual adjustments, declines) for a specific Reclaim.ai task, allowing it to reschedule normally. |
| reclaim_prioritizeA | Marks a specific Reclaim.ai task for prioritization ('On Deck'), increasing its likelihood of being scheduled sooner. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| reclaim_active_tasks | Provides a list of all active tasks from Reclaim.ai as a JSON array. Active means tasks that are not deleted and whose status is not ARCHIVED or CANCELLED. IMPORTANT NOTE ON 'COMPLETE' STATUS: Tasks with status 'COMPLETE' (meaning scheduled time is finished) ARE INCLUDED here because the user has NOT marked them as done. These should be treated as active, potentially past-due tasks, not finished items. |
TDQS
Scored across 13 tools
Each tool targets a distinct action on Reclaim.ai tasks: creating, reading, updating, deleting, time management, prioritization, and status changes. No two tools overlap in purpose; even similar verbs like 'add_time' and 'log_work' are clearly differentiated.
All tools follow a consistent 'reclaim_verb_noun' pattern (e.g., reclaim_create_task, reclaim_list_tasks, reclaim_start_timer). The naming is uniform, with clear verbs that describe the action, making it easy to predict tool behavior.
With 13 tools, the server is well-scoped for task management. Each tool covers a necessary operation without being overwhelming. The count is typical for a domain-specific MCP server, providing sufficient functionality without redundancy.
The server covers core CRUD, lifecycle (complete/incomplete), time tracking (add, log, start/stop timer), prioritization, and exception handling. Minor gaps exist, such as no bulk operations or filtering by date range, but the essential workflows are supported.