You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat(registry): add remove path for user-added custom registries (#592)
Custom registry sources added via `registry add-source` could not be
removed through any supported surface — the only recourse was hand-editing
config.db and restarting the daemon. Add the inverse remove operation:
- DELETE /api/v1/registries/{id} — removes a custom/unverified source,
refusing built-ins via the same registry_shadows_builtin guard and
returning registry_not_found (404) for unknown ids. Persisted
copy-on-write like add-source.
- `mcpproxy registry remove <id>` CLI (aliases: rm, remove-source),
daemon-required, with remove-specific error guidance.
- cliclient.RemoveRegistrySource wrapping the DELETE endpoint.
- Shared server-side derivation (removeRegistrySourceFromConfig) so CLI
and REST produce identical persisted config.
Docs (registries.md, rest-api.md) and OpenAPI spec updated in the same PR.
The Web UI affordance is tracked as a separate frontend follow-up.
Related #MCP-1057
0 commit comments