Use MCP apps in Copilot Studio

Model Context Protocol (MCP) apps let an MCP server provide an interactive user interface (UI) for a tool in a supported Copilot experience. The server provides the app, and the host renders it in the conversation. The host is the Copilot experience that displays the app. The app can call tools and read resources from its configured MCP server.

MCP apps are supported in Microsoft 365 Copilot and Copilot Studio preview chat. They're not supported in Teams or web chat.

Connecting an MCP server alone doesn't create an app. The server must declare a UI resource for a tool.

Prerequisites

  • An MCP server configured as a tool for your agent, with a working connection.
  • A tool that declares a UI resource using the MCP apps standard.

For server setup, learn more in Add an MCP server to your agent as a tool.

How MCP apps work

  1. The agent calls an MCP tool that declares a UI resource, such as ui://project/status.html.
  2. The MCP server returns the tool result. The host retrieves the declared resource.
  3. If the resource is valid and available, the host renders the app in the conversation.
  4. The app can call tools or read resources through the configured MCP integration.

A tool declares its UI resource in _meta.ui.resourceUri. The following example shows a tool definition:

{
  "name": "get_project_status",
  "description": "Get the current status of a project.",
  "inputSchema": {
    "type": "object",
    "properties": {}
  },
  "_meta": {
    "ui": {
      "resourceUri": "ui://project/status.html"
    }
  }
}

The server must return valid HTML for that URI by using the MCP apps MIME type text/html;profile=mcp-app. For example, a resources/read response for the resource has the following structure:

{
  "contents": [
    {
      "uri": "ui://project/status.html",
      "mimeType": "text/html;profile=mcp-app",
      "text": "<!DOCTYPE html><html><head><title>Project status</title></head><body><h1>Project status</h1></body></html>"
    }
  ]
}

This example shows the resource response format, not a complete interactive app. Learn more about the protocol requirements at MCP Apps specification.

Supported MCP apps capabilities

The following table summarizes MCP apps capabilities in Microsoft 365 Copilot and Copilot Studio preview chat. Support depends on what the host provides, not only on what the MCP apps standard or software development kit (SDK) defines.

MCP Apps capability Support Details
ui/initialize and ui/notifications/initialized Supported The app and host complete an initialization handshake before exchanging tool data.
Tool input and tool result notifications Supported The app receives the originating tool input and result.
Tool cancellation notification Not supported The app doesn't receive a notification when the originating tool is canceled.
tools/call Supported Calls a tool on the configured MCP server.
resources/read Supported Reads a resource from the configured MCP server.
ui/open-link Supported The host handles requests to open an external link (HTTP and HTTPS only).
ui/message Supported Sends a message from the app to the conversation.
ui/update-model-context Supported Adds text or structured content from the app to agent context, subject to runtime limits.
ui/notifications/size-changed Supported The host uses app size changes to lay out the UI.
Display modes Supported with limits The host supports inline display and fullscreen in the side pane.
Host context Partially supported Theme, language and region, and display mode are provided.
ui/notifications/tool-input-partial Not supported Partial tool-input streaming isn't forwarded to the app.
Canceling an app-originated operation Not supported end to end The client can discard a late response after the app closes, but the operation might continue running.
File download requests Not supported The host doesn't provide the renderer's download-file callback.
MCP logging notifications Not supported The host doesn't expose the renderer's logging callback to the app.

Other MCP apps capabilities might not be available. Check this table before relying on a host API.

Security and access

The host renders app content in a sandboxed, cross-origin iframe and applies content security policy (CSP) restrictions. The app doesn't have direct access to the host page or credentials. Tool calls and resource reads go through the configured MCP integration and remain subject to applicable connection, authentication, and runtime checks.

Declare the external domains the app needs in the UI resource's _meta.ui.csp metadata. Use connectDomains for network requests and resourceDomains for external resources such as scripts, images, and styles. Undeclared external domains are blocked.

Test an MCP app

  1. Open your agent in Microsoft 365 Copilot or Copilot Studio preview chat.
  2. Start a conversation and ask the agent to invoke the MCP tool associated with the app.
  3. Confirm that the app appears and displays the expected content.
  4. Use the app and confirm that its tool calls and resource reads return the expected results.

If the tool result appears but the UI doesn't, check that the tool declares a valid UI resource and the server returns valid HTML with the required MIME type. A resource-read failure can prevent the UI from appearing without changing an otherwise successful tool result.

Frequently asked questions

Does adding an MCP server automatically add an app?

No. The server must declare and provide a UI resource for a tool.

Can an app call MCP tools?

Yes. The host routes app tool calls to the app's configured MCP server.

Does Copilot Studio support every MCP Apps feature?

No. The supported capabilities table lists the capabilities available through the host. The MCP apps standard or SDK might define additional features that Copilot Studio doesn't provide.