Integration action (MCP)

The same idea as a native integration action, for any service that exposes an MCP (Model Context Protocol) server. You choose which of the server's tools the workflow may use, whether that's one, several, or its whole tool set, and the agent uses them during runs.

When a service offers an official MCP endpoint, this is preferred over hand-built API calls, since tools are discovered automatically. The architect verifies an endpoint belongs to the vendor before connecting it, and asks you when it can't.

What the architect sets up

• The server's address and how to sign in to it (OAuth or access headers)
• Which of the server's tools the workflow may use
• Guidance for how the agent should use them

How it behaves in a run

• The agent uses it as needed while working through a stage.

Related

• Stages & components: how components fit into a workflow
• Showcase: see components like this at work in real workflows
• Integrations: the services workflows connect to, including via MCP

For developers: the API and MCP server identify this component as mcp_server.