You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 28, 2026. It is now read-only.
When using a User MCP Token (created via https://open.teambition.com/user-mcp), calling any API endpoint to mark a task as done returns 401 InvalidUserToken:
User MCP Token should be able to mark tasks as done, as this is a basic task management operation. The update_task.py script in this repo supports --taskflowstatus-id, but for projects without a custom taskflow, there's no way to complete a task via the API.
Suggested Fix
Either:
Include isDone write permission in the User MCP Token scope
Document which operations are supported by User MCP Token vs other token types
Provide an alternative API endpoint that works with User MCP Token
Problem
When using a User MCP Token (created via https://open.teambition.com/user-mcp), calling any API endpoint to mark a task as done returns
401 InvalidUserToken:PUT /api/v3/task/{taskId}/isDone→ 401POST /api/v3/task/{taskId}/done→ 401PUT /api/v2/task/{taskId}/isDone→ 401The same token works fine for:
Expected Behavior
User MCP Token should be able to mark tasks as done, as this is a basic task management operation. The
update_task.pyscript in this repo supports--taskflowstatus-id, but for projects without a custom taskflow, there's no way to complete a task via the API.Suggested Fix
Either:
isDonewrite permission in the User MCP Token scopeEnvironment
dingtalk-teambitionfrom this repo