Like tool triggers, resource and prompt triggers are supported in multiple languages including .NET, Java, Python, TypeScript, and JavaScript.<\/p>\n
MCP Apps: interactive UI from your MCP server<\/h2>\n
MCP Apps<\/a> let your tools return interactive user interfaces instead of plain text. Combine tool triggers with resource triggers, and your MCP server can serve rich, rendered experiences to MCP-aware clients.<\/p>\n The Azure Functions MCP extension supports MCP Apps natively, meaning the same function app that exposes tools and resources can also serve UI components. The launch blog post on the Azure Apps Blog<\/a> walked through the pattern in detail.<\/p>\n For .NET developers, the new fluent builder API<\/strong> (available in the latest NuGet release<\/a>) makes it easier to compose MCP Apps by chaining tool and resource definitions in a declarative style.<\/p>\n The extension supports built-in MCP authentication<\/a>, implementing the requirements of the MCP auth spec. All samples in the aka.ms\/remote-mcp<\/a> repo enable built-in MCP auth by default with Microsoft Entra ID as the identity provider.<\/p>\n Samples have also been updated to demonstrate how to exchange tokens in the On-Behalf-Of (OBO) flow, so your MCP tools can access downstream APIs using the invoking user’s identity.<\/p>\n Auth configuration in the Azure portal<\/strong>: Preview at Build is a one-click experience in the Azure portal for configuring built-in MCP auth. No more manual app registration creating, configuration and wiring to the server. Just open your server app on the portal and click to enable MCP auth. Try it out<\/a>!<\/p>\n Beyond the headline primitives and auth, the extension has shipped a steady stream of capabilities the past few months. The following are the notable additions.<\/p>\n Structured content lets you return machine-readable JSON metadata alongside your tool’s response via the Tools aren’t limited to returning plain text. The extension supports the full set of MCP content block types, e.g. A set of fluent builder APIs that let you configure MCP primitives declaratively in Usage of the MCP extension has grown steadily since its preview launch. Tool execution volume has increased 15x over the past six months as more customers move from experimentation to production. As adoption grows, so do the expectations. Developers building production MCP servers are hitting real friction around auth complexity, client configuration, and observability. We’re continuing to invest in the extension to address these gaps and help customers be more successful building and hosting MCP servers on Azure Functions. Here’s where we’re focusing next.<\/p>\n Auth remains the biggest barrier to getting an MCP server into production. We’ll work on:<\/p>\n Our goal: the secure path should be the easy path.<\/p>\n We’ll build tighter integration between Azure Functions MCP servers and Microsoft Foundry<\/a>. This includes surfacing MCP servers in Foundry Toolbox<\/a>, a new feature introduced to help Foundry agents discover and consume tools from a single endpoint. Developers will be able to publish an MCP server from Functions and have it available to Foundry agents through Toolbox without manual endpoint configuration.<\/p>\n We prioritize based on feedback from the community raised in our GitHub repo<\/a>. For example, support for streaming output and pagination are top items in our backlog today based on user demand.<\/p>\n We also track the MCP spec’s evolution closely and will continue shipping support for strategic features as they land. Examples of proposals we’re eyeing on:<\/p>\n Have something you’d like us to prioritize? Let us know by filing a request on GitHub<\/a>.<\/p>\n A roundup of what shipped in the Azure Functions MCP extension since preview: resource and prompt triggers, MCP Apps, built-in MCP authentication, structured and rich content, fluent .NET configuration APIs, and what is coming next.<\/p>\n","protected":false},"author":42940,"featured_media":3910,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[967,734,765,161,160,940,959,965,162,960,733],"class_list":["post-3907","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-azure-sdk","tag-ai-agents","tag-azure","tag-azure-functions","tag-dotnet","tag-java","tag-mcp","tag-model-context-protocol","tag-node-js","tag-python","tag-serverless","tag-typescript"],"acf":[],"blog_post_summary":" A roundup of what shipped in the Azure Functions MCP extension since preview: resource and prompt triggers, MCP Apps, built-in MCP authentication, structured and rich content, fluent .NET configuration APIs, and what is coming next.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/posts\/3907","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/users\/42940"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/comments?post=3907"}],"version-history":[{"count":1,"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/posts\/3907\/revisions"}],"predecessor-version":[{"id":3908,"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/posts\/3907\/revisions\/3908"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/media\/3910"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/media?parent=3907"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/categories?post=3907"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-json\/wp\/v2\/tags?post=3907"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}![\"MCP](\"https:\/\/devblogs.microsoft.com\/azure-sdk\/wp-content\/uploads\/sites\/58\/2026\/06\/06-04-functions-mcp-updates-mcp-apps-demo.gif\")
<\/p>\nMCP authentication<\/h2>\n
Feature enhancements<\/h2>\n
Structured content<\/h3>\n
structuredContent<\/code> field. Clients that support it can programmatically consume the data (e.g. parse fields, render tables, drive downstream logic) rather than just displaying text. Clients that don’t support it still get the regular content blocks as a fallback.<\/p>\nRich content types<\/h3>\n
TextContent<\/code>, ImageContent<\/code>, AudioContent<\/code>, ResourceLink<\/code>, and EmbeddedResource<\/code>, so your tools can return images, audio clips, references to resources, and inline file content alongside text.<\/p>\nInput and output schemas<\/h3>\n
WithInputSchema<\/code> and WithOutputSchema<\/code> give you explicit control over the JSON schemas advertised for your tools. This is especially useful when the auto-generated schema from function parameters doesn’t capture the full contract. For example, when your tool accepts a complex nested object or returns a specific shape that clients depend on. Input and output schemas are currently supported in .NET, with support for other languages coming soon.<\/p>\nbuilder.ConfigureMcpTool(\"SearchDocs\")\r\n .WithOutputSchema(\"\"\"\r\n {\r\n \"type\": \"object\",\r\n \"properties\": {\r\n \"results\": { \"type\": \"array\", \"items\": { \"type\": \"string\" } },\r\n \"query\": { \"type\": \"string\" }\r\n },\r\n \"required\": [\"results\", \"query\"]\r\n }\r\n \"\"\");<\/code><\/pre>\nFluent configuration APIs in .NET<\/h3>\n
Program.cs<\/code>:<\/p>\n\n
ConfigureMcpTool<\/code><\/strong>: add properties, metadata, input\/output schemas, or promote a tool to an MCP App<\/li>\nConfigureMcpResource<\/code><\/strong>: attach metadata to resources<\/li>\nConfigureMcpPrompt<\/code><\/strong>: define prompt arguments and metadata<\/li>\n<\/ul>\nbuilder.ConfigureMcpTool(\"sayhello\")\r\n .WithProperty(\"name\", McpToolPropertyType.String, \"Name of the user\", required: true)\r\n .WithMetadata(\"ui\", new { resourceUri = \"ui:\/\/index.html\" });<\/code><\/pre>\nWhat’s next<\/h2>\n
Continued auth simplification<\/h3>\n
\n
Deeper integration with Microsoft Foundry<\/h3>\n
Continued feature enhancement<\/h3>\n
\n
\nGet started<\/h2>\n
\n