-
|
In the latest MCP release (https://modelcontextprotocol.io/specification/2025-11-25/changelog) there was a new addition for supporting background tasks:
I tried to test this feature and I get |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Response from ADK Answering Agent (experimental, answer may be inaccurate) TLDR: ADK does not currently support the new experimental MCP background tasks feature (SEP-1686). The error you are seeing is not due to a misconfiguration on your part, but because this feature requires specific implementation within the ADK framework which has not been added yet. Hi @jimkont, Thank you for your question. The new experimental support for background tasks (SEP-1686) in the Model Context Protocol (MCP) is a recent addition to the specification. As you've discovered, using a tool that requires this feature results in the error This error indicates that the client-side of the connection (in this case, the ADK) needs to have special handling for the lifecycle of these tasks, such as polling for results and managing deferred retrieval. This functionality is not yet built into the ADK's While ADK has robust support for asynchronous operations and long-running tools [4, 7], this is distinct from the new background task protocol defined in SEP-1686. Therefore, you are not missing any configuration. Support for this new MCP feature will need to be added to the ADK in a future release. I am adding the |
Beta Was this translation helpful? Give feedback.
-
|
Response from ADK Answering Agent (experimental, answer may be inaccurate) TLDR: While ADK has support for long-running operations via Hi @jimkont, Thanks for your question. I see an answer has already been chosen for this discussion, but I'd like to provide some additional information that might be helpful. ADK supports long-running or asynchronous operations through the ADK also has robust support for MCP, allowing it to act as an MCP client to consume tools from an MCP server, or to expose its own tools via an MCP server. [2, 3] The error message you're seeing, I would recommend checking the development version of ADK to see if this feature is included there. You can install the development version using pip: pip install git+https://github.com/google/adk-python.gitFor more details, you can refer to the following documentation: I hope this helps! [1] https://google.github.io/adk-docs/tools-custom/function-tools/ |
Beta Was this translation helpful? Give feedback.
Response from ADK Answering Agent (experimental, answer may be inaccurate)
TLDR: ADK does not currently support the new experimental MCP background tasks feature (SEP-1686). The error you are seeing is not due to a misconfiguration on your part, but because this feature requires specific implementation within the ADK framework which has not been added yet.
Hi @jimkont,
Thank you for your question.
The new experimental support for background tasks (SEP-1686) in the Model Context Protocol (MCP) is a recent addition to the specification. As you've discovered, using a tool that requires this feature results in the error
Tool 'toon-name' requires task-augmented execution.This error indicates…