- Get started
- Build
- Deploy and run
- Examples
- Reference
MCP
Look up the MCP connector: its Run a Tool action, when to use it instead of giving MCP tools to an agent, and the sign-in methods of an MCP connection.
The MCP connector lets a workflow run a tool of a Model Context Protocol (MCP) server, any server that follows the MCP standard. In the Add node panel, it's in the Connector category, under MCP. How connector nodes work describes how a connector node is set up.
Actions
| Action | What it does |
|---|---|
| Run a Tool | Run a tool of the connected MCP server and return its output. |
The first field of Run a Tool is MCP connection. Until you select a connection, it's the only field on the node. In the list, select an existing connection to an MCP server, or select Add new connection to create one.
Run a Tool or MCP tools for an agent
There are two ways to use an MCP server in a workflow:
| Use | When |
|---|---|
| Run a Tool | The workflow always runs the same tool at the same step. You choose the tool when you build the workflow. |
| MCP server tools on an Autonomous agent | The agent decides at run time which tools to call. |
Connection
A Run a Tool node signs in through a connection to the MCP server. Create a connection describes how to create one from the node. On the Connect to page, choose the sign-in method that the server requires:
| Sign-in method | What you need |
|---|---|
| OAuth 2.0 Authorization code | The base URL of the server, and the client ID, client secret, authorization URL, token URL, and scopes of its OAuth provider. |
| OAuth 2.0 Authorization code with PKCE | The same as above, without a client secret, and the code challenge method, which is S256 by default. |
| OAuth 2.0 Client Credentials | The base URL of the server, and the client ID, client secret, token URL, and scopes of its OAuth provider. |
| Personal Access Token | The base URL of the server, and the full value of the authorization header, including its prefix, such as Bearer. |
The base URL is the address of the server, for example https://mcp.example.com/mcp. PKCE stands for Proof Key for Code Exchange. The documentation of the MCP server lists the values it expects.
Next steps
- Connector: every connector, grouped by area.
- Autonomous agent: give an agent the tools of an MCP server.
- Community: ask questions and share workflows with other builders on the UiPath Forum.