Create a tool from Subflow

Create a tool from Subflow to expose it to Model Context (MCP) clients from an MCP Server. Subflows and actions empower agents to complete tasks seamlessly —from submitting requests to routing for approval and confirming outcomes across workflows, without leaving the client interface.

Before you begin

Role required: sn_mcp_server.tools_admin, sn_mcp_server.admin, or admin

Perform these steps before creating a tool:

1. Create a subflow in Flow Designer using supported input and output data types. See Create a subflow in Workflow Studio to learn more.
2. Establish the requisite AI Access Control List (ACL) to facilitate external invocation of the component. See Create AI ACL to learn more.
3. Confirm the compatibility status in the staging table. See Check compatibility of Subflow or Action to learn more.
4. Register the component as a tool within the MCP Server.

Procedure

1. Select Subflow from these categories.
   
   
2. On the form, fill in the fields.
   
   
   Note:

   The category is auto-populated if selected in the last modal.

   Table 1. Tool form

   Field	Description
   Subflow	Select a Subflow type from the list.
   Label	An internal name for the tool.
   Description	The description of what the tool intends to do. This input is exposed to AI clients and used to determine when to call this tool. Note: Admins must add specific and action-oriented description as the AI clients access it to decide when to invoke the tool.
   MCP Servers	One or more servers you want to add your tool to.

   In the Tool inputs section, add the fields associated with the capability. See Create a tool for a Model Context Protocol server to learn more. The tool is now published on MCP Server and discoverable by MCP clients.

What to do next

Invoke the tool via Claude or an alternative MCP client and verify that it functions as intended with the tool you registered. Launch MCP client to test end-to-end execution.