Developers
building MCP servers on Azure Functions can expose tools but not resources.
Now, Azure Functions supports MCP resource triggers, enabling
developers to expose resources directly from an Azure Functions–hosted Model
Context Protocol (MCP) server. Resources can include static or dynamic files,
application metadata, and MCP App UI content such as HTML-based widgets
rendered natively by MCP hosts. This capability is available in the Azure
Functions MCP extension for Python, TypeScript, .NET, and Java.
With MCP
resource triggers, developers can now build and host MCP servers on Azure
Functions that provide richer context, interactive experiences, and structured
data alongside tools.
Learn more.