--- sourceDocument: Brazil Build workflows sourceDocumentLink: https://www.servicenow.com/docs/r/build-workflows Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Build workflows ft:clusterId : - crworkflow bundleId : - crworkflow workflow : - Creator --- # Playbooks as an MCP tool # Playbooks as an MCP tool {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Playbooks as an MCP tool ServiceNow's Model Context Protocol (MCP) Server Console enables you to expose playbooks as tools within an MCP server. This setup allows MCP clients to trigger and execute playbooks as part of automated workflows, enhancing integration and interaction capabilities with external clients through MCP. Show full answer Show less ## Key Requirements for Playbooks * **Activity and Lane Start Configuration:** All activities and lanes must start immediately upon triggering; delayed starts are not supported. * **Supported Activity Types:** Only specific activity types are supported, including Create Record, Form Record, Questionnaire, Send Email, Knowledge, Instruction, and Decisions. These map well to asynchronous form submissions or completion actions. * **Subflows and Actions:** Any referenced subflows or custom actions must be marked as MCP-compatible. If not, the entire playbook is incompatible. * **Form Field Types:** Only primitive field types are supported. Complex fields such as reference fields, rich text editors, attachments, and custom types are not supported. ## How to Enable a Playbook as an MCP Tool To enable a playbook for MCP client use, follow these steps: 1. **Create a compatible playbook:** Use Workflow Studio to develop and activate a playbook that meets MCP compatibility requirements. 2. **Create an MCP tool:** As an admin, create a Playbook-type MCP tool in the MCP Server Console, selecting the desired playbook, and add it to an MCP server. 3. **Configure MCP clients:** Set up MCP clients to connect to the MCP server and access the playbook tool. 4. **Use the playbook via MCP client:** Users can trigger the playbook from the MCP client (e.g., a chatbot like Claude), provide required inputs, and progress through the playbook activities. Completion triggers confirmation and summary display. ## Practical Benefits for ServiceNow Customers * Seamlessly integrate ServiceNow playbooks into external workflows and agentic processes via MCP clients. * Automate and streamline complex workflows such as employee onboarding with direct user interaction through chatbots or other MCP clients. * Ensure compatibility and reliability by adhering to specified playbook constraints and supported activity types. Expose a playbook as a tool in an MCP server, enabling MCP clients to trigger and execute the playbook through the Model Context Protocol (MCP). ServiceNow® MCP Server Console lets you create MCP servers and expose specific tools to MCP clients. When you add a playbook as a tool in an MCP server, MCP clients can invoke the playbook as part of an agentic workflow. ## Dependencies {#playbook-as-mcp-tool__section_wbt_cj5_zjc} Before you can expose a playbook as an MCP tool, the playbook must meet compatibility requirements. If you create a playbook or want to expose an existing playbook through an MCP server, make sure that the playbook meets the following requirements: Activity and lane start configuration : All playbook activities and lanes must start immediately when triggered. Delayed start configurations aren't supported in MCP execution. Supported activity types : The playbook may only contain the following activity types: * Create Record Form * Record Form * Questionnaire * Send Email * Knowledge * Instruction * Decisions {#playbook-as-mcp-tool__ul_kqn_p35_zjc}These activity types are supported because their completion semantics map to form submission or mark-complete actions, which MCP can handle asynchronously. Activity types with complex state management or long-running operations aren't supported. Subflows and actions : Any subflows or actions referenced within the playbook must be explicitly marked with Execution Type: MCP-compatible. If a subflow or custom action is not marked as MCP-compatible, the entire playbook is set to incompatible. All dependencies are scanned and validated before the playbook can be exposed as a tool. Form field types : Only primitive field types are supported in MCP playbook execution. Reference fields, complex widgets such as rich text editors and advanced pickers, attachment fields, and user-defined custom types aren't supported. ## Next steps {#playbook-as-mcp-tool__section_ckp_fj5_zjc} In ServiceNow® MCP Server Console, create a tool with the playbook and add it to an MCP server. When an MCP client is configured to use the MCP server, the client can invoke the playbook through the tool you created. ## Example: Enabling a playbook as an MCP tool {#playbook-as-mcp-tool__playbook-mcp-example} We take an example of enabling an employee onboarding playbook to new employees through an MCP client such as Claude. Step 1: Create a playbook for employee onboarding : As a playbook author, in Workflow Studio, create and activate a playbook for employee onboarding that is compatible to add as an MCP tool to an MCP server. Step 2: Create a Playbook MCP tool : As an system admin or MCP server admin, create an MCP tool of type Playbook. Select the employee onboarding playbook and add the tool to an MCP server. For more information, see [Add a playbook as an MCP tool](https://www.servicenow.com/docs/hu2M0MnMSgDf5UzwwDNY1g "Create a tool in the MCP Server Console and expose it in an MCP server so that MCP clients can invoke the playbook through the MCP."). Step 3: Configure the MCP client : Configure MCP clients to connect to the server and use the tool. For more information, see [Connecting to an MCP server from an MCP client](https://www.servicenow.com/docs/access?context=connect-mcp-server-client&version=brazil&pubname=brazil-intelligent-experiences&ft:locale=en-US) Step 4: Use the playbook from the MCP client : As an employee, use the configured MCP client to trigger the playbook. For example, trigger the playbook from a Claude chat. Claude searches for the available tools and runs the employee onboarding playbook that you have enabled through MCP tool. Claude prompts you for the required inputs. You can either enter the information or upload a document that contains the required information. The playbook then automatically moves to the next activity in the workflow and prompts for relevant information. After all the activities of the playbook are completed, Claude displays a confirmation message with a summary.