modelcontextprotocol / modelcontextprotocol/ext-tasks
Stalled tasks
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46
- Forks
- 9
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Description
Assume an client loses control over the outstanding tasks running on MCP server.
- There is no tasks/list call. How would a stale tasks that may still run on the MCP server be known by the client ?
- When should an MCP server stop a task ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the MCP tasks extension specification and its current task-lifecycle entry points; the issue names no files or tests. Determine how clients discover stale tasks and when servers stop them, then document the agreed behavior and add coverage for those cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100