Create a tool from Action

Create a tool from Action to expose it to Model Context Protocol (MCP) clients from an MCP Server.

Before you begin

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

Perform these steps before creating a tool:

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

Procedure

Select Action from these categories.

Image omitted: mcp-create-tool-moveworks.png
Tool creation

On the form, fill in the fields.

Image omitted: mcp-server-create-tool-action.png
Create tool from Action

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

Field	Description
Action	Select a Action type from the list.
Label	An internal name for the tool.
MCP app	An active MCP app linked to this action.
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](create-tool-mcp-server.md) to learn more. The tool is now published on the 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.

Parent Topic:Create a tool for a Model Context Protocol server