-
Notifications
You must be signed in to change notification settings - Fork 171
Open
Description
When using custom catalogs with Docker MCP, docker mcp server inspect <server> fails with "server not found in catalog" even though:
docker mcp catalog show <custom-catalog>correctly lists the serverdocker mcp server listshows the server as enableddocker mcp server enable/disable <server>works correctly
This appears to be the same issue that was fixed for enable in v0.19.0 (#138), but the fix was not applied to inspect.
Steps to Reproduce
- Create a custom catalog with a server definition:
version: 2
name: custom-servers
displayName: Custom MCP Servers
registry:
myserver:
description: "My custom server"
title: My Server
type: server
image: myorg/myserver:latest
tools:
- name: mytool- Import the catalog:
docker mcp catalog import ./custom-servers.yaml- Enable the server:
docker mcp server enable myserver
# Works: ✓ Server enabled- Try to inspect:
docker mcp server inspect myserver
# Fails: server "myserver" not found in catalogExpected Behavior
docker mcp server inspect should search all registered catalogs, not just docker-mcp.
Actual Behavior
inspect only searches the official docker-mcp catalog, ignoring custom catalogs.
Impact
- Custom servers don't appear in Docker Desktop MCP Toolkit UI
- Users can't view tool details for custom servers
- Inconsistent behavior between
enable(works) andinspect(fails)
Environment
- Docker Desktop: 4.x with MCP Toolkit
- docker mcp version: v0.28.0
- OS: Windows 11 + WSL2
Related Issues
- Cant enable mcp server from custom catalog #138 (fixed for
enable, same issue exists forinspect)
Metadata
Metadata
Assignees
Labels
No labels