reclaim_list_tasksLABSCO SUMMARY
Reclaim's task list, writable from wherever you are already talking.
The tools cover the loop that matters day to day — create the task, give it scheduled time, start and stop the timer, log the work, mark it done — so something that comes out of a conversation lands in the planner instead of a note. One behaviour will catch you out if you do not know it: Reclaim marks a task COMPLETE when its scheduled block ends rather than when the work is finished, so ask explicitly for COMPLETE tasks to be included when you want everything genuinely still open.
What it is
A community client for Reclaim.ai's public API, covering task operations: listing, creating, updating, completing and deleting tasks, adding scheduled time, running the timer, and logging work. Active tasks are also exposed as a resource at tasks://active.
What you get
- Tasks listed, filtered to active or all, and one task fetched by its ID
- A task created, updated, marked complete, or marked incomplete again
- A task deleted permanently — the one destructive tool in the set
- Scheduled minutes added to a task
- The timer started and stopped on a task, and work time logged with an end time
- Scheduling exceptions cleared, and a task prioritised in the planner
- Active tasks available as a resource at tasks://active, not only through a tool call
Requirements
Node.js 18 or newer and a Reclaim API key from your developer settings, passed as RECLAIM_API_KEY. Runs over stdio through npx reclaim-mcp-server, or from a source build. It is a community project on Reclaim's public API and is unaffiliated with Reclaim.ai, which runs an official remote server of its own at https://mcp.reclaim.ai — worth comparing before you commit to either.
Setup effort
One command plus a key — npx reclaim-mcp-server, then supply credentials
USE CASES
01
Capturing work that came out of a conversation
Create the task with its properties, then give it the scheduled minutes it needs.
02
Seeing what is genuinely still open
List the active tasks, asking for COMPLETE ones as well, since Reclaim sets that when the block ends rather than when the work is done.
03
Timing what you are doing now
Start the timer on the task, and stop it when you move to something else.
04
Recording time you already spent
Log the minutes against the task with the time they actually finished.
05
Closing something out
Mark it complete — or reopen it when it turns out not to be.
06
Getting the planner to behave
Prioritise the task, and clear the scheduling exceptions that were pinning it where it was.
13 tools
Listed in project docs. Your client may show a different list.
reclaim_get_taskreclaim_create_taskreclaim_update_taskreclaim_mark_completereclaim_mark_incompletereclaim_delete_taskreclaim_add_timereclaim_start_timerreclaim_stop_timerreclaim_log_workreclaim_clear_exceptionsreclaim_prioritizeBEFORE YOU INSTALL
What to know first
Tools you get
13 tools named in the project's documentation.
Requires
- npx on PATH
- Node.js ≥ 18
- RECLAIM_API_KEY in your environment
Where it runs
Both documented setups run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npx reclaim-mcp-serverMCP Clients
Claude Desktop — npx
CLAUDE DESKTOP — NPX · JSON
{
"mcpServers": {
"reclaim": {
"command": "npx",
"args": [
"reclaim-mcp-server"
],
"env": {
"RECLAIM_API_KEY": "<YOUR_RECLAIM_API_KEY>"
}
}
}
}Claude Desktop — absolute paths
CLAUDE DESKTOP — ABSOLUTE PATHS · JSON
{
"mcpServers": {
"reclaim": {
"command": "<YOUR_PATH_TO_NODE> (run `which node` in terminal)",
"args": [
"<YOUR_PATH_TO_RECLAIM_MCP_SERVER>/dist/index.js"
],
"env": {
"RECLAIM_API_KEY": "<YOUR_RECLAIM_API_KEY>"
}
}
}
}
