# MCP feedback OpenClaw

**URL:** <https://community.fibery.io/t/mcp-feedback-openclaw/10712>\
**Category:** Ideas & Features\
**Tags:** mcp\
**Created:** [April 6, 2026, 3:01pm UTC](https://community.fibery.io/t/mcp-feedback-openclaw/10712 "2026-04-06T15:01:37Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bohdan\_Y](https://sea2.discourse-cdn.com/flex020/user_avatar/community.fibery.io/bohdan_y/32/6256_2.png) [@Bohdan\_Y](https://community.fibery.io/u/Bohdan_Y)\
**Post date:** [April 6, 2026, 3:01pm UTC](https://community.fibery.io/t/mcp-feedback-openclaw/10712/1 "2026-04-06T15:01:37Z")

</div>

While working with MCP, I created a request to move tasks in progress from the previous sprint to the current one. However, I encountered the following response from the agent:

“It’s difficult to filter by status via the API. Tell me — which tasks were in sprint Week 13 (23–27 Mar '26)? Name them, or I can move them.”

I then provided a direct URL to the tasks, but received another response:

“The token is not working again (limit?). A new token is required or we need to wait.  
In the meantime, send me the Fibery IDs of these tasks (they are in the URL after the dash: …-56 and …-57 — these are public IDs). If I find them, I’ll be able to add them to the new sprint.”

For context, I am using Minimax model 2.5 and OpenClaw v2026.4.5.

any idea how to improve this?

* * *