<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>MCP on Dapr Docs</title><link>https://v1-18.docs.dapr.io/developing-ai/mcp/</link><description>Recent content in MCP on Dapr Docs</description><generator>Hugo</generator><language>en</language><atom:link href="https://v1-18.docs.dapr.io/developing-ai/mcp/index.xml" rel="self" type="application/rss+xml"/><item><title>Authenticating an MCP server</title><link>https://v1-18.docs.dapr.io/developing-ai/mcp/mcp-authentication/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://v1-18.docs.dapr.io/developing-ai/mcp/mcp-authentication/</guid><description>&lt;h2 id="overview">Overview&lt;/h2>
&lt;p>The &lt;a href="https://modelcontextprotocol.io/specification/">MCP specification&lt;/a> does not mandate any form of authentication between an MCP client and server. The security model is left to the user to plan and implement. This creates a maintenance burden on developers and opens up MCP servers to various attack surfaces.&lt;/p>
&lt;p>While MCP servers lack identity, OAuth2 is a well established standard that can be used to properly authenticate MCP clients to MCP servers.&lt;/p>
&lt;p>OAuth2 becomes essential when MCP servers are:&lt;/p></description></item></channel></rss>