ReadonlydisplayHuman-readable label used as the group header in the view.
Protected ReadonlyfetchProtectedhandlersProtected ReadonlyhoverProtected ReadonlyinstallProtected ReadonlyinstallReadonlyonFired when the contribution's entries change (e.g. after install, refresh, or preference update).
Protected ReadonlyonProtected ReadonlypreferenceReadonlypriorityOrdering hint when multiple contributions yield entries for the same section. Lower numbers come first. Defaults to 0.
Protected ReadonlysearchReadonlysearch@-prefixed token recognised in the search query to scope results to this contribution
alone. Composable with the existing @installed / @builtin / @recommended mode tokens
(e.g. @installed @mcp shows installed servers of type mcp-server only). When no
type token appears in the query, all contributions are shown.
Contributors are expected to start the token with @; without the prefix the search model
may treat the token as a plain word in the free-text part of the query.
Protected ReadonlytoReadonlytypeStable, machine-readable identifier for the artifact type.
ProtectedconfirmPrompts the user for parameters the registry can't decide for them (autostart,
auth token) before writing the entry. Cancelling the dialog aborts the install.
The dialog is created through an injected factory so this contribution doesn't
import the DOM-touching ReactDialog chain directly.
Dispose this object.
ProtectedinitProtectedreadReturns the raw (untyped) servers preference; per-entry validation happens in
toServerDescription, which uses the shared MCPServersPreference.isValue guard
so this view and McpFrontendApplicationContribution apply the same value checks.
Called when the user triggers a refresh on the view toolbar. Contributions
should re-fetch any remote state and fire onDidChange once new data is
available. Optional - contributions without remote data can omit this.
Entries for the "Installed" section. Omit if this type has no installed concept.
Entries matching a user search. Each result carries its own searchableText
so the view can rank hits from all contributions against a single query.
Omit if this type does not participate in search.
Contributions may ignore query when their internal state already reflects the
current query (e.g. the VSX adapter, whose model is kept in sync with the search
bar via the singleton VSXExtensionsSearchModel). In that case the contribution
is expected to yield its current result set and let the view's cross-contribution
fuzzy ranker handle the actual ordering.
ProtectedsafeProtectedto
Contribution point for the Extensions view. Each contribution represents one artifact type (e.g.
extension,mcp-server, futureskill) and supplies entries to the relevant sections of the view.Contributions implement only the modes they participate in. A contribution that has no concept of "built-in", for example, simply omits
resolveBuiltIn.Each returned
TreeElementcarries its ownrender(host)- the contribution controls how its entries look. The view groups results by contribution type (usingdisplayNameas the group header) when more than one contribution yields entries for a section.