iii worker add mcp fails with missing skills dependency, but config.yaml starts it successfully

[orincolor]

Description

iii worker add mcp fails with a hard dependency error on the skills worker,
which is not published to the registry. However, adding mcp to config.yaml
starts it successfully — same binary, no errors.

Steps to reproduce

Fails:

iii worker add mcp
Error: requires skills worker which is not in the registry.

Works:

# config.yaml
workers:
  - name: mcp
    config:
      api_path: /mcp

Engine starts, iii worker list shows mcp running with a PID.

Expected behavior

iii worker add mcp should work the same way the engine's config-based startup
does — either the dependency is required in both paths, or neither.

Impact

Users cannot install the MCP worker via CLI. The only workaround is manually
adding it to config.yaml, which is undocumented.

[rohitg00]

Hey @orincolor, Thanks for reporting. I have assigned our dedicated engineer to fix this asap.

We're in middle of architecting the mcp, skills, and standard specs in the best way and that caused for overlap.

Sorry for inconvenience.

[sergiofilhowz]

We need to revisit mcp worker, it was modified before a massive refactoring on other workers, will keep you posted here on the timeline

[orincolor]

Thank you @sergiofilhowz !

[chenqianhe]

This problem still exists. Are there any updates?