Skip to content

Fix issues with releases failing on ADK #406

@jwc2023

Description

@jwc2023

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

  1. Install ADK with (older) MCP SDK.
  2. Connect ADK to an MCP server that exposes tools.
  3. Try running ADK sampling that triggers MCP tool conversion.
  4. 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/A

Additional context

N/A

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions