With VS Code’s MCP useful resource help, which incorporates help for useful resource templates, sources returned from MCP device calls turn out to be out there to the mannequin, might be saved in chat, and might be connected as context by way of the Add Context button in chat. Builders can browse sources throughout MCP servers, or for a selected server, through the use of the MCP: Browse Sources command, or utilizing the MCP: Checklist Servers command.
VS Code 1.101 presents experimental help for sampling, which permits MCP servers to make requests again to the mannequin, and now helps MCP servers that require authentication, enabling interplay with an MCP server that operates on behalf of a consumer account for that service. Builders now can allow growth mode to debug MCP servers by including a dev
key to the server config.
Lastly, new MCP extension APIs allow extensions to publish collections of MCP servers. This implies VS Code extension authors can bundle MCP servers with their extensions or construct extensions that dynamically uncover MCP servers from different sources.