Skip to content

UI Warning: "*mcp.GatewayToolset start failed: failed to initialize MCP client" #1347

@egrosdou01

Description

@egrosdou01

Describe the bug

When an MCP toolset is defined under an agent, during execution, the following warning is visible.

*mcp.GatewayToolset start failed: failed to initialize MCP client: calling "initialize": EOF

VS Code is connected to a WSL environment, and from there the cagent is executed. Looking at the code base, there is a comment defined for the calling function. However, I am unsure if this issue needs to be reported.

Version affected

Docker Desktop:

Client:
Version: 29.1.3
API version: 1.52
Go version: go1.25.5
Git commit: f52814d
Built: Fri Dec 12 14:48:47 2025
OS/Arch: linux/amd64
Context: default

Server: Docker Desktop 4.55.0 (213807)
Engine:
Version: 29.1.3
API version: 1.52 (minimum version 1.44)
Go version: go1.25.5
Git commit: fbf3ed2
Built: Fri Dec 12 14:49:51 2025
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: v2.2.0
GitCommit: 1c4457e00facac03ce1d75f7b6777a7a851e5c41
runc:
Version: 1.3.4
GitCommit: v1.3.4-0-gd6d73eb8
docker-init:
Version: 0.19.0
GitCommit: de40ad0

Cagent:

cagent version v1.15.1
Commit: d6af657

Docker MCP:

docker mcp version
v0.34.0

How To Reproduce

Detailed steps to reproduce the behavior:

  1. Dcoker Desktop for Windows 11
  2. Active WSL integration
  3. MCP and DRM enabled
  4. Create an agent that calls the MCP duckduckgo. Took the code from the examples section
  5. cagent execution from WSL
  6. Notice the warning message

Expectation
N/A

Screenshots

Image

OS and Terminal type

Please include what OS and terminal you are using

  • Windows 11
  • VS Code 1.108.0

Any other info you consider useful can be included here

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions