MCP spec unlocks powerful browser capabilities

In the ever-evolving landscape of web development, browser capabilities continue to expand in ways that many developers haven't fully realized. A recent talk by Harald Kirschner from Microsoft's VSCode team reveals how the Multi-Channel Permissions (MCP) specification opens up powerful new possibilities for web applications. This under-utilized standard allows browsers to expose advanced system capabilities to web applications while maintaining robust security controls.

Key insights from Kirschner's presentation:

• The MCP spec creates a standardized permission model that enables web apps to access advanced device capabilities previously limited to native applications
• VSCode's web version leverages MCP to provide seamless integration with local filesystems, terminal access, and more
• The permission architecture balances security with user control through fine-grained permission requests and intuitive user interfaces

The overlooked potential of MCP

What stands out most from Kirschner's talk is how MCP fundamentally changes what's possible in browser-based applications. By providing a consistent framework for requesting and managing permissions to system resources, MCP enables web applications to bridge the gap with native apps in unprecedented ways.

This matters because the distinction between web and native applications continues to blur. Enterprises increasingly favor browser-based solutions for their cross-platform consistency and reduced deployment overhead. MCP addresses one of the final frontiers—access to system capabilities—that has historically kept web apps from fully replacing native applications in professional environments.

Beyond the presentation: Real-world applications

While Kirschner focuses primarily on VSCode's implementation, the implications extend much further. Consider the emergence of browser-based creative tools like Figma and Canva. These platforms have disrupted traditional desktop software by moving complex workflows to the web. With MCP, we could see the next generation of professional tools making similar transitions.

For example, video editing platforms could leverage MCP to access local media files and processing capabilities more efficiently. Imagine a web-based DaVinci Resolve that maintains most functionality without installation requirements. Similarly, development environments beyond VSCode could provide seamless integration with local development tools, git repositories, and deployment pipelines.

Financial institutions present another compelling use case. MCP could enable secure access to cryptographic hardware or authentication devices directly through web interfaces, potentially eliminating custom software installations while maintaining security standards.