mcpAppDefaults.ts ×1

Frontier kind: Code frontier

unlabeled · c_d36919fa87f8

1710 tests · 12494 LOC · 47 files · introduces 0 tests · 43 LOC · 1 file

Introduces — evidence that enters the hierarchy at this concept

Code
1 range43 lines · 1 files
Tests
0 tests

Contains — complete concept membership

All code (extent)
945 ranges12494 lines · 47 files · Browse complete extent
All tests (intent)
1710 testsBrowse complete intent

Neighbourhood graph

The orange circle is the focus. Violet and green circles are every ancestor and descendant, broader and narrower, at any distance; blue squares and pink diamonds are the introduced files and exact introduced tests of every visible concept, not only the focus's. Arrows point from broader to narrower concepts and bridge only concepts omitted from this view. Undirected links show source or test introduction. Concept and file size follows LOC; exact test nodes use test-count units.

Introduced files, introduced tests, and structurally relevant concept specialization

In the embedded map, ordinary wheel input scrolls the page; use the visible controls to zoom and drag to pan. Open the full-screen map for canvas navigation: wheel pans, Ctrl/Command plus wheel zooms, and arrow keys pan when this region is focused. On touch screens, open the full-screen map to pan or pinch. If JavaScript or WebGL is unavailable, use the native relationship evidence on this page.

Graph controls are ready.

Interactive rendering requires JavaScript and WebGL. Use the native relationship evidence on this page while the interactive map is unavailable.

Native relationship evidence

Every exact file and test below is linked only from the concept that introduces it.

Introduced tests

Every collected test enters the hierarchy at exactly one concept.

No tests are introduced at this concept. Its intent tests are introduced by other concepts.

Introduced code

Every collected source range enters the hierarchy at exactly one concept.

1 file ranked by introduced lines: 43 introduced LOC across 1 ranges. Expand a file to inspect source; the > gutter marks introduced lines.

src/vs/platform/agentHost/common/state/protocol/mcpAppDefaults.ts 43 introduced LOC · 1 range

Open complete file

1 > /*--------------------------------------------------------------------------------------------- mcpAppDefaults.ts
2 > * Copyright (c) Microsoft Corporation. All rights reserved.
3 > * Licensed under the MIT License. See License.txt in the project root for license information.
4 > *--------------------------------------------------------------------------------------------*/
5 >
6 > import type { AhpMcpUiHostCapabilities, McpServerCustomizationApps } from './channels-session/state.js';
7 >
8 > /**
9 > * MCP App capabilities the agent host proxies for every MCP server it
10 > * advertises over the `mcp://` side-channel.
11 > *
12 > * - `serverTools.listChanged` is `true`: we forward
13 > * `notifications/tools/list_changed` whenever the SDK signals that the
14 > * tool inventory has refreshed (see `CopilotAgentSession`).
15 > * - `serverResources` is advertised as an empty object: we serve the
16 > * `resources/*` methods over the channel but do not promise
17 > * `notifications/resources/list_changed` forwarding (no `listChanged`).
18 > * - `sampling` is advertised as an empty object: we serve
19 > * `sampling/createMessage` requests from the App over the `mcp://`
20 > * channel (the agent host handler forwards them to
21 > * `session.rpc.mcp.executeSampling`). The SEP-1577 `tools`
22 > * sub-flag is NOT set — we don't pass through tool content blocks.
23 > *
24 > * Per the AHP spec, `mcpApp` is a static capability declaration —
25 > * "SHOULD be present whenever the server can host Apps" — so this
26 > * constant is set on every MCP customization at construction time,
27 > * regardless of the server's current lifecycle state.
28 > */
29 > export const DEFAULT_MCP_APP_CAPABILITIES: AhpMcpUiHostCapabilities = {
30 > serverTools: { listChanged: true },
31 > serverResources: {},
32 > sampling: {},
33 > };
34 >
35 > /**
36 > * The full `mcpApp` shape applied to a {@link McpServerCustomization}.
37 > * Wraps {@link DEFAULT_MCP_APP_CAPABILITIES} so callers can drop it in
38 > * directly without re-allocating the same wrapper object at every call
39 > * site.
40 > */
41 > export const DEFAULT_MCP_APP: McpServerCustomizationApps = {
42 > capabilities: DEFAULT_MCP_APP_CAPABILITIES,
43 > };