A developer has built a Model Context Protocol (MCP) server that exposes inventory lookup tools for a Copilot Studio agent. The MCP server is hosted at https://api.contoso.com/mcp and requires Bearer token authentication. When registering this MCP server in Copilot Studio, which combination of values must be provided during the registration process?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Registering an MCP server is like giving someone a friend's home address plus the key to get through the door — you need where it lives (the endpoint URL) and how to prove you belong (the auth config). The tool list is discovered automatically from the server's manifest, not entered by hand.
Full explanation below image
Full Explanation
When adding a Model Context Protocol server as a knowledge or action source in Copilot Studio, the platform needs two things: the server's endpoint URL and the authentication method to use when calling it. The endpoint URL tells Copilot Studio where to send its discovery request (which retrieves the tool schema list automatically via the MCP protocol). The auth configuration tells the runtime how to attach credentials to every subsequent tool call — in this case, a Bearer token.
Copilot Studio does not require the developer to manually enumerate tool names. The MCP protocol's discovery mechanism (the server manifest) returns all available tools, their schemas, and descriptions automatically when the endpoint is first registered. This is a fundamental design principle of MCP: tools are self-describing.
Option A is incorrect because IP address and port are not required — the full URL already contains routing information. Tool names are discovered, not manually entered.
Option B is incorrect because MCP registration does not use an OpenAPI specification URL. OpenAPI is used for custom connectors and HTTP actions, not MCP servers. While Azure Key Vault can store secrets, it is not part of the MCP registration form itself.
Option D is incorrect because MCP server registration does not use Azure resource IDs or managed identity principal IDs. Managed identity is relevant to Azure-hosted connectors and services but is not the auth model used in MCP bearer token authentication flows.
Exam tip: Know the distinction between MCP server registration (URL + auth) versus custom connector registration (OpenAPI spec). These are often tested side-by-side as distractors.