From Pain Points to Solutions: How VSCode Solved MCP's Biggest ...

Harald Kirschner from VSCode/GitHub shares how they systematically identified and solved the five biggest MCP pain points, transforming the developer experience from frustrating to delightful. ... "I get a lot of complaints," he admitted with a smile, before diving into what he called "the five biggest MCP pain points" that VSCode has systematically addressed. ... ## The Installation Nightmare is Over ‍ The first pain point Harald tackled was one many developers know all too well: the Byzantine process of finding and installing MCP servers. "It started kind of hacky," he explained, "with copying around JSON blobs and maybe hard-coding API keys." This wasn't just inconvenient—it was a barrier to adoption that kept many developers from even trying MCP. … ## Making API Keys Actually Secure ‍ The second major improvement addresses a security headache that has plagued MCP adoption. Many servers still require API keys, and the traditional approach meant dropping these sensitive credentials directly into JSON configuration files—a practice that made security-conscious developers cringe. VSCode now handles API keys as proper inputs, prompting users for them during installation rather than requiring manual JSON editing. This approach makes credential management both more secure and more user-friendly, eliminating one of the most common stumbling blocks for new MCP users. ## Beyond Secret Incantations: Intelligent Tool Discovery Harald's third point struck at something every MCP user has experienced: the frustration of "secret incantations" needed to invoke specific tools. Too often, developers find themselves crafting careful prompts to trigger the right functionality, treating their AI assistants more like command-line interfaces than intelligent agents. VSCode addresses this with a built-in tool picker that lets developers be explicit about which tools they want to use in any given session. But the real innovation goes deeper: developers can save effective tool combinations as reusable "chat modes," creating what Harald called "context engineering building blocks." … ## Scaling to Unlimited Tools The fourth challenge Harald addressed might seem like a luxury problem, but it's actually fundamental to MCP's future: what happens when developers accumulate dozens or hundreds of tools? Traditional approaches break down quickly under this load, forcing difficult choices about which capabilities to keep active. VSCode's latest release tackles this head-on with support for essentially unlimited tools. Harald demonstrated this by loading 171 tools simultaneously—a number that would overwhelm most systems—and then successfully running queries that automatically selected the right tools for the task. … ## Smart Context Management The final major pain point Harald discussed was context bloat—the problem of MCP servers potentially flooding conversations with excessive information from searches or other operations. This issue can quickly exhaust token limits and make conversations unwieldy. VSCode's solution leverages one of MCP's more sophisticated but underutilized capabilities: sampling. When an MCP server performs a search, it can use sampling to summarize results before presenting them to the user. This provides much more condensed, focused answers while still preserving the full context for those who need it. … ## A Pattern for the Future ... Each solution builds on the others: easy installation encourages experimentation, secure credential management removes adoption barriers, intelligent tool discovery makes daily use more pleasant, unlimited tool support enables power users, and excellent developer experience ensures the ecosystem continues to grow.