mcp

The latest version of Visual Studio Code Insiders now shows a prompt before you bring in a third-party MCP server. Neat! No more one-click command execution.

The official MCP C# SDK now supports OAuth 2.0 authentication and RFC 9728 Protected Resource Metadata, making secure AI integrations simpler for .NET developers.

Tired of agents making wrong assumptions about user input? Visual Studio Code now supports MCP elicitations, where servers can request structured input through the client’s native UI, completely eliminating guesswork and tedium of interpreting LLM input.

The Model Context Protocol got auth right, but that doesn’t mean you should implement it yourself. Here’s why API gateways are usually the better choice, and what that really costs you.

MCP authorization spec now requires RFC 8707 implementation to prevent token misuse and phishing attacks. Here’s how the resource parameter works and why it matters for your MCP deployments.

Recent experiences with Model Context Protocol development, including conferences, security work, and community updates from Build, MCP Developer Summit, and AI Engineer World’s Fair.

AI agents aren’t replacing developers - they’re amplifying what skilled engineers can accomplish. The job replacement panic might just be the wrong place to channel our energy into.

See how the latest Visual Studio Code Insiders builds seamlessly integrate with both new and legacy MCP authorization specs, offering a frictionless developer experience for accessing protected MCP servers with any OAuth provider.

Learn how to protect Model Context Protocol (MCP) servers from confused deputy attacks when implementing Dynamic Client Registration, and how Azure API Management can help mitigate these security risks.

A super-quick overview of the new MCP authorization specification and how it improves security and flexibility for MCP servers.