Create an MCP Tool Workflow v2

Publish a narrow Workflow as an MCP tool by defining a typed argument schema, performing one business action, and returning structured content.

Build the tool contract

  1. Create a Workflow.
  2. Add the MCP receive Method to the Workflow.
  3. Set a concise, unique ToolName that describes an action.
  4. Define the input fields under the receive Step's Arguments object. Use clear names, types, shapes, and descriptions.
  5. Add the domain Steps that validate and perform the operation.
  6. Add the MCP respond Method at the Workflow root.
  7. Map the result to StructuredContent and set IsError appropriately.

Use exactly one matched receive/respond pair. Keep the respond Step at the root even when domain logic uses If, TryCatch, or another container.

Workflow returns are unused on an MCP tool. The tool result is provided through the StructuredContent return on the respond Step. Adjust the descendant schema for this return as required.

Test the tool

  1. Run the Workflow in Debug with representative Arguments.
  2. Inspect the captured MCP response in Logs.
  3. Test validation, not-found, authorization, provider failure, and success paths.
  4. Confirm that error paths set IsError: true and still return useful structured content.
  5. Save the tested revision.

Publish and authorize

  1. Publish or promote the Workflow to the target Environment.
  2. Enable it in that Environment.
  3. Create a Delegate MCP user API Key for the same Environment.
  4. Assign the Workflow and permitted users.
  5. Copy the Environment's /mcp URL from the MCP screen and register it in the client.
  6. Confirm tool discovery and make a controlled call.

Tool discovery is the intersection of publish, status, API-key Workflow assignment, permitted user, and effective user access. Do not troubleshoot these as interchangeable states.

See also

See Workflow MCP Server, MCP Screen, and Agent-ready Business Action.