Connect to an existing MCP server
A Model Context Protocol (MCP) server gives an agent access to a shared collection of tools and data. Your organization might use one when several agents need the same capabilities.
Understand how an MCP server works
Note
MCP integration for agents powered by the Microsoft Copilot harness is a preview feature. Availability and connection requirements can vary by server and environment.
An MCP server describes each available tool, including its name, purpose, inputs, and outputs. Agents that connect to the server read those descriptions. If the server's URL, authentication, or exposed tools change, edit its entry in the Tools dialog to refresh the connection and reread the tool list. Then retest affected requests in Preview rather than assuming the changes apply automatically.
MCP can reduce repeated setup when an organization provides many related tools to several agents. However, a maker has less control over descriptions defined by the server than over a connector tool configured directly in the agent.
Treat an MCP server as a shared technical service managed outside the agent. Before using one, confirm who owns it, what it can do, how users sign in, what data it can access, and who supports it. Creating a server or troubleshooting custom authentication usually requires an administrator, integration specialist, or developer.
Add an existing MCP server by URL
Servers published for your organization can also appear on the MCP tab in Add a tool. For those servers, select the gallery entry and follow its connection prompts. The following procedure covers an existing server that you add by URL instead.
When your organization provides a managed MCP server, ask the server owner for its HTTPS address and sign-in requirements. Then add it to an agent:
- On the agent's Build tab, select Tools.
- Select Add a tool, select Add, and then select Model Context Protocol (MCP).
- Enter a clear name and description, the server address, and the authentication details supplied by the server owner.
- Add the server and review the tools it makes available. Each tool should have a clear name and description so the agent knows when to use it.
- Save the server, and then use Preview to test a request that should use one of its tools.
- Check the activity details to confirm that the agent selected the expected tool and received the expected result.
This quick check confirms that the server and tool are available to the agent. Later, you learn how to test tool selection and diagnose problems across all tool types. If the connection fails or a tool's purpose isn't clear, work with the server owner rather than changing settings without guidance.
For more information, see Add an MCP server to your agent as a tool (preview).