MCP
Attach outbound MCP servers to an Action Agent. The agent calls remote tools at chat time. This is not the hosted ActionFlows MCP server.
MCP
The MCP panel in Studio attaches Model Context Protocol servers the agent can call during chat. This is outbound MCP: the agent uses remote tools.
It is not the hosted ActionFlows MCP server, where Cursor or Claude call ActionFlows tools.
Org connections vs custom URL
- Organization MCP connection: reuse a connection from Organization → Integrations → MCP Servers. Status follows
isMcpConnectionReady(URL, headers, or OAuth as required). - Custom URL: name plus HTTPS URL and optional encrypted headers. Studio probes the catalog (SSRF-safe) and you pick enabled tool names.
OAuth-mapped catalog servers
When the MCP catalog slug maps to an org OAuth integration (for example GitHub, Google products, Microsoft/Teams, Jira), Studio shows Authenticate. That reuses the organization's OAuth connection for that provider. Unmapped servers stay URL plus headers only.
Slack is excluded from this MCP OAuth map on purpose. Slack bot credentials are for flow nodes and triggers, not hosted Slack MCP.
Only remote URLs that pass ActionFlows SSRF checks are allowed. Private and link-local targets are blocked.
If one MCP server fails to connect, that server is marked in error and the turn continues with the remaining tools.
Transport
Streamable HTTP (default) and SSE, matching common remote MCP deployments. See the MCP catalog.
Enable only the tools the agent needs. Smaller catalogs mean fewer wrong calls.