-
Notifications
You must be signed in to change notification settings - Fork 17
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
Recent ADK releases were failing due to outdated MCP SDK types, fragile tool-metadata handling, and inconsistent conversion of MCP content into ADK parts.
Steps to reproduce
- Install ADK with (older) MCP SDK.
- Connect ADK to an MCP server that exposes tools.
- Try running ADK sampling that triggers MCP tool conversion.
- Release workflow fails.
Expected behavior
Upgrade the MCP SDK, improving transport and type safety, and strengthening content-conversion logic. It also introduces a repository-wide utility script to clean lockfiles and prevent dependency-related breakages during releases.
Ensure ADK releases run reliably across the codebase with consistent behavior from MCP tools, transports, and sampling flows.
- Upgrade MCP SDK.
- Replace legacy transport.
- Strengthen type safety for MCP tools.
- Improve MCP content conversion.
- Add repository utility ccript.
Goal:
- To upgrade MCP SDK ensuring long-term compatibility with ongoing ecosystem changes.
ADK-TS Version
0.3.30
Environment
Node.js
Node.js Version (if applicable)
No response
Relevant log output
N/AAdditional context
N/A
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working