Skip to content

fix(mcp): the registry entry asks which profiles to serve - #190

Merged
leemour merged 1 commit into
mainfrom
fix/registry-profiles-required
Nov 17, 2026
Merged

leemour merged 1 commit into
mainfrom
fix/registry-profiles-required

Conversation

@leemour

@leemour leemour commented Nov 17, 2026

Copy link
Copy Markdown
Member

The MCP Registry entry started mcp serve --profiles all, so a client installed from the registry served every account on the computer without the owner choosing. Now --profiles is a required argument with the placeholder personal, as ydisk ships it (WC-MCP-9).

  • mcp serve --profiles <names|all> comes from cli-core's shared MCP group, so the server takes this shape as is.
  • mcp-publisher validate (1.8.5, as in release.yml) passes on the new file.
  • Changelog fragment under "Changed — may break callers". No release: the next regular one carries it.

🤖 Generated with Claude Code

server.json started `mcp serve --profiles all`, so a client installed from
the MCP Registry reached every account on the computer without the owner
choosing one. That breaks "never pick an account for the owner" (WC-MCP-9).

--profiles is now a required named argument with the placeholder
`personal`, as yandex-disk-cli ships it. mcp serve already takes one name,
a comma-separated list or all (cli-core mcpGroup). The version stays
0.0.0: release.yml sets it at publish time. Checked with mcp-publisher
1.8.5 validate.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@leemour
leemour merged commit cc8ed73 into main Nov 17, 2026
13 checks passed
@leemour
leemour deleted the fix/registry-profiles-required branch November 17, 2026 22:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant