Repository navigation
feat(mcp): asynchronous Tasks across pyATS and 34 integrations - #283
Conversation
🔍 Tessl Skill Review
|
1 participant
{{ message }}
Merged
Merged
6 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Long-running MCP calls can now return a standard task handle while work continues. This follow-up to merged #282 enables 298 tools across 35 integrations: 242 in 30 owned FastMCP servers, 34 in NetBox/SD-WAN/NVD/Wikipedia, and 22 in the pinned pyATS runtime from automateyournetwork/pyATS_MCP#15. Clients without the current Tasks capability retain foreground results.
Selected synchronous reads run in worker threads, with explicit per-tool eligibility and one embedded task worker per server. pyATS persists completed results in SQLite, serializes device access and does not replay unfinished operations after restart. The other integrations default to ephemeral FastMCP task storage; their cancellation/storage guarantees are documented separately. Existing authorization and change-control rules remain.
Spec 142 includes inventory, implementation plan, acceptance evidence and deferred scope. This coordinates specs 141/142 into the still-unpublished 1.5.0 source release. Includes updated release notes, operational guide and a Markdown social post leading with pyATS SSH impact.
Validation
Remote validation is tracked in MCP contracts, release metadata, and skill review. Eight fresh/upgrade external patch scenarios also passed, including idempotent reapplication. Full evidence:
specs/142-mcp-async-tasks/verification.md.Limits and rollout
No live network/device operation, production runtime deployment, Redis failover or measured network speedup claim. Optional credentials/Docker are unavailable locally. Other external Tasks ports remain foreground pending per-tool acceptance; the five unported framework integrations and licensed RADKit exception from #282 remain open. Source release publication does not deploy services.
Guides:
docs/MCP-TASKS.md,docs/FASTMCP-4-WRITEUP.md,docs/releases/1.5.0.md. Paste-ready post:docs/social/MCP-TASKS-POST.md.Published release and completion
95bb17e27a6a2538fcb0168d0b1d0ab5bbe34692.