Reported issues for reclaim-mcp-server
Pod holds 15 of 15 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.
Back to reclaim-mcp-server.
Most discussed
reschedule_focus_block returns "API error 400: No details provided"
Mirror. Canonical issue: https://gitlab.com/universalamateur1/reclaim-mcp-server/-/work_items/15 (The reclaim-mcp-server PyPI package points at GitLab as homepage / repository / bug tracker. This GitHub copy mirrors it for visibility — file comments on the GitLab issue if you want the maintainer to see them.)
Summary
reschedule_focus_block always returns "API error 400: No details provided" in both explicit-time and AI-reschedule modes, making the tool completely unusable and pro
Read the thread · 2026-05-14 · open · external user · 0 comments
plan_work returns HTTP 400 with no error context
Mirror. Canonical issue: https://gitlab.com/universalamateur1/reclaim-mcp-server/-/work_items/7 (The reclaim-mcp-server PyPI package points at GitLab as homepage / repository / bug tracker. This GitHub copy mirrors it for visibility — file comments on the GitLab issue if you want the maintainer to see them.)
Summary
plan_work returns a bare "HTTP 400: Bad Request" with no actionable error body, making it impossible for callers to determine what scheduling constraint was violated.
Read the thread · 2026-05-14 · open · external user · 0 comments
add_time_to_task docstring should explain it represents active work (intentionally starts the task)
Mirror. Canonical issue: https://gitlab.com/universalamateur1/reclaim-mcp-server/-/work_items/6 (The reclaim-mcp-server PyPI package points at GitLab as homepage / repository / bug tracker. This GitHub copy mirrors it for visibility — file comments on the GitLab issue if you want the maintainer to see them.)
Summary
The add_time_to_task tool description doesn't make clear that this is an active-work operation that intentionally starts the task and creates a calendar event. Call
Read the thread · 2026-05-14 · open · external user · 0 comments
add_time_to_task notes param overwrites task body field
Mirror. Canonical issue: https://gitlab.com/universalamateur1/reclaim-mcp-server/-/work_items/5 (The reclaim-mcp-server PyPI package points at GitLab as homepage / repository / bug tracker. This GitHub copy mirrors it for visibility — file comments on the GitLab issue if you want the maintainer to see them.)
Summary
add_time_to_task's notes parameter silently overwrites the task's entire description body, destroying existing content. Given that the operation represents an active
Read the thread · 2026-05-14 · open · external user · 0 comments
prioritize_task docstring says "elevates priority" but priority enum unchanged
Mirror. Canonical issue: https://gitlab.com/universalamateur1/reclaim-mcp-server/-/work_items/4 (The reclaim-mcp-server PyPI package points at GitLab as homepage / repository / bug tracker. This GitHub copy mirrors it for visibility — file comments on the GitLab issue if you want the maintainer to see them.)
Summary
prioritize_task docstring says it "elevates to high priority" but only changes the task's sort index — the priority enum field (P1/P2/P3/P4) remains unchanged, mislea
Read the thread · 2026-05-14 · open · external user · 0 comments
get_user_analytics returns {"status":"PENDING"} with no polling docs
Mirror. Canonical issue: https://gitlab.com/universalamateur1/reclaim-mcp-server/-/work_items/3 (The reclaim-mcp-server PyPI package points at GitLab as homepage / repository / bug tracker. This GitHub copy mirrors it for visibility — file comments on the GitLab issue if you want the maintainer to see them.)
Summary
get_user_analytics returns {"status":"PENDING"} on first call with no indication that the caller should poll, no job ID to track, and no documented retry protocol — m
Read the thread · 2026-05-14 · open · external user · 0 comments
list_completed_tasks limit param ignored or per-task payload too large
Mirror. Canonical issue: https://gitlab.com/universalamateur1/reclaim-mcp-server/-/work_items/2 (The reclaim-mcp-server PyPI package points at GitLab as homepage / repository / bug tracker. This GitHub copy mirrors it for visibility — file comments on the GitLab issue if you want the maintainer to see them.)
Summary
list_completed_tasks returns ~125KB even with limit=3, causing tool-result overflow in agent contexts. Each completed recurring task carries its full instance history
Read the thread · 2026-05-14 · open · external user · 0 comments
list_habits has no pagination — overflows on every call
Mirror. Canonical issue: https://gitlab.com/universalamateur1/reclaim-mcp-server/-/work_items/1 (The reclaim-mcp-server PyPI package points at GitLab as homepage / repository / bug tracker. This GitHub copy mirrors it for visibility — file comments on the GitLab issue if you want the maintainer to see them.)
Summary
list_habits has no pagination and returns every habit's full data in a single response, causing tool-result overflow on accounts with many habits.
Reproduction
- C
Read the thread · 2026-05-14 · open · external user · 0 comments
Most recent
convert_event_to_habit returns "API error 400: No details provided"— error body swallowed
Mirror. Canonical issue: https://gitlab.com/universalamateur1/reclaim-mcp-server/-/work_items/14 (The reclaim-mcp-server PyPI package points at GitLab as homepage / repository / bug tracker. This GitHub copy mirrors it for visibility — file comments on the GitLab issue if you want the maintainer to see them.)
Summary
convert_event_to_habit always fails with "API error 400: No details provided" regardless of input, and the actual Reclaim API error body is never surfaced, making it
Read the thread · 2026-05-14 · open · external user · 0 comments
set_event_rsvp returns HTTP 500 for self-organized event with no other attendees
Mirror. Canonical issue: https://gitlab.com/universalamateur1/reclaim-mcp-server/-/work_items/13 (The reclaim-mcp-server PyPI package points at GitLab as homepage / repository / bug tracker. This GitHub copy mirrors it for visibility — file comments on the GitLab issue if you want the maintainer to see them.)
Summary
set_event_rsvp returns HTTP 500 ("internal_error") when called on a self-organized event with no other attendees — a logical pre-condition violation that should be cau
Read the thread · 2026-05-14 · open · external user · 0 comments
set_event_rsvp docstring enum mismatches API expectation
Mirror. Canonical issue: https://gitlab.com/universalamateur1/reclaim-mcp-server/-/work_items/12 (The reclaim-mcp-server PyPI package points at GitLab as homepage / repository / bug tracker. This GitHub copy mirrors it for visibility — file comments on the GitLab issue if you want the maintainer to see them.)
Summary
set_event_rsvp's docstring lists SCREAMING_CASE values (ACCEPTED, DECLINED, TENTATIVE, NEEDS_ACTION) but the Pydantic schema requires PascalCase (Accepted, `
Read the thread · 2026-05-14 · open · external user · 0 comments
list_events event_type parameter is broken for all values, not just RECLAIM_MANAGED
Mirror. Canonical issue: https://gitlab.com/universalamateur1/reclaim-mcp-server/-/work_items/11 (The reclaim-mcp-server PyPI package points at GitLab as homepage / repository / bug tracker. This GitHub copy mirrors it for visibility — file comments on the GitLab issue if you want the maintainer to see them.)
Summary
The event_type parameter on list_events returns HTTP 400 for every value tested, including values listed in the docstring as examples and values observed in the actu
Read the thread · 2026-05-14 · open · external user · 0 comments
clear_task_snooze leaves stale snoozeUntil in response
Mirror. Canonical issue: https://gitlab.com/universalamateur1/reclaim-mcp-server/-/work_items/10 (The reclaim-mcp-server PyPI package points at GitLab as homepage / repository / bug tracker. This GitHub copy mirrors it for visibility — file comments on the GitLab issue if you want the maintainer to see them.)
Summary
clear_task_snooze correctly un-snoozes the task (status returns to SCHEDULED) but the response still contains a stale non-null snoozeUntil value instead of null, m
Read the thread · 2026-05-14 · open · external user · 0 comments
enable_habit and disable_habit return inconsistent response shapes
Mirror. Canonical issue: https://gitlab.com/universalamateur1/reclaim-mcp-server/-/work_items/9 (The reclaim-mcp-server PyPI package points at GitLab as homepage / repository / bug tracker. This GitHub copy mirrors it for visibility — file comments on the GitLab issue if you want the maintainer to see them.)
Summary
enable_habit and disable_habit return inconsistent response shapes — {} vs {"result": true} — making it impossible to reliably verify success with the same code p
Read the thread · 2026-05-14 · open · external user · 0 comments
restart_task is no-op — task remains ARCHIVED
Mirror. Canonical issue: https://gitlab.com/universalamateur1/reclaim-mcp-server/-/work_items/8 (The reclaim-mcp-server PyPI package points at GitLab as homepage / repository / bug tracker. This GitHub copy mirrors it for visibility — file comments on the GitLab issue if you want the maintainer to see them.)
Summary
restart_task is a no-op on archived tasks — it returns the task in unchanged ARCHIVED state despite the docstring claiming it "returns it to active scheduling." The wor
Read the thread · 2026-05-14 · open · external user · 0 comments
The remaining reports are on the project's issue tracker.