modelcontextprotocol/python-sdk
Watch
1
0
Fork
You've already forked python-sdk
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

[v1.x] Deprecate the WebSocket transport and the experimental tasks entry points (#2828)

Browse source
This commit is contained in:
Max 2026-06-11 09:20:19 +01:00 • committed by GitHub
commit b8f491724c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
4 changed files with 219 additions and 32 deletions
Download patch file Download diff file Expand all files Collapse all files

15
docs/experimental/index.md
View file

@ -1,12 +1,13 @@
# Experimental Features
!!! warning "Experimental APIs"
!!! warning "Deprecated"
The features in this section are experimental and may change without notice.
They track the evolving MCP specification and are not yet stable.
The experimental tasks API is deprecated and will be removed in mcp 2.0.
Tasks (SEP-1686) were removed from the MCP specification and are expected
to return as a separate MCP extension in a future release.
This section documents experimental features in the MCP Python SDK. These features
implement draft specifications that are still being refined.
are deprecated and remain available on the 1.x line only for existing users.
## Available Experimental Features
@ -36,8 +37,10 @@ async def handle_get_task(request: GetTaskRequest) -> GetTaskResult:
result = await session.experimental.call_tool_as_task("tool_name", {"arg": "value"})
```
Accessing the `.experimental` properties emits a `DeprecationWarning`.
## Providing Feedback
Since these features are experimental, feedback is especially valuable. If you encounter
issues or have suggestions, please open an issue on the
If you rely on these features and have feedback on their deprecation or the planned
MCP extension, please open an issue on the
[python-sdk repository](https://github.com/modelcontextprotocol/python-sdk/issues).

6
docs/experimental/tasks-client.md
View file

@ -1,8 +1,10 @@
# Client Task Usage
!!! warning "Experimental"
!!! warning "Deprecated"
Tasks are an experimental feature. The API may change without notice.
The experimental tasks API is deprecated and will be removed in mcp 2.0.
Tasks (SEP-1686) were removed from the MCP specification and are expected
to return as a separate MCP extension in a future release.
This guide covers calling task-augmented tools from clients, handling the `input_required` status, and advanced patterns like receiving task requests from servers.

6
docs/experimental/tasks-server.md
View file

@ -1,8 +1,10 @@
# Server Task Implementation
!!! warning "Experimental"
!!! warning "Deprecated"
Tasks are an experimental feature. The API may change without notice.
The experimental tasks API is deprecated and will be removed in mcp 2.0.
Tasks (SEP-1686) were removed from the MCP specification and are expected
to return as a separate MCP extension in a future release.
This guide covers implementing task support in MCP servers, from basic setup to advanced patterns like elicitation and sampling within tasks.

7
docs/experimental/tasks.md
View file

@ -1,9 +1,10 @@
# Tasks
!!! warning "Experimental"
!!! warning "Deprecated"
Tasks are an experimental feature tracking the draft MCP specification.
The API may change without notice.
The experimental tasks API is deprecated and will be removed in mcp 2.0.
Tasks (SEP-1686) were removed from the MCP specification and are expected
to return as a separate MCP extension in a future release.
Tasks enable asynchronous request handling in MCP. Instead of blocking until an operation completes, the receiver creates a task, returns immediately, and the requestor polls for the result.