---
sourceDocument: Australia Build workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/build-workflows

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Check the compatibility of playbooks

# Check the compatibility of playbooks {#ariaid-title1}

Release version: Australia  
Updated September 21, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Verify that the playbook is compatible to be used as an MCP tool.

## Before you begin

Role required: workflow_mcp_tool_admin

## About this task

When you try to [Add a playbook as an MCP tool](https://www.servicenow.com/docs/zRzNhFHY~37SAiewqOCTJQ "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.") but are unable to see a playbook in the MCP tool list, perform this procedure to verify that the playbook is compatible.

## Procedure

1. Select All.
2. In the search box, enter <kbd class="ph userinput">sys_workflow_mcp_staging_tool.list</kbd>.
3. In the MCP Staging Workflow Tools list, locate the playbook by name or by sorting the table.
4. If you don't see your playbook in the list, run a new compatibility scan.

   | Option | Description |
   | Full scan compatibility check | Scans all the playbooks in your instance for compatibility. Select this option when the table is empty and you run the compatibility check for the first time. |
   | Quick scan compatibility check | Runs the compatibility scan only on new playbooks. Select this option if you import playbooks to your instance. |
   |-|-|

   {#check-mcp-compatibility-playbooks__choicetable_dds_bxv_qkc}
5. Check the Compatibility Status column of the playbook.  
   For incompatible playbooks, open the record to see the incompatible reason. After you update and republish the playbook, the compatibility status updates automatically. For more information about compatibility, see [Playbooks as an MCP tool](https://www.servicenow.com/docs/6pOGaYyGerE5RdYJU9nfXg "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).").

   When the playbook compatibility status is Compatible, you can add it to an MCP server as an MCP tool.

   To check the compatibility status of subflows and actions used in the playbook, select All and enter <kbd class="ph userinput">sn_fd_genai_mcp_staging_action_tool.list</kbd> (for actions) or
   <kbd class="ph userinput">sn_fd_genai_mcp_staging_subflow_tool.list</kbd>(for subflows) in the search box. To be compatible as an MCP tool, the subflows and actions need an AI ACL. For more information, see [Create an AI ACL for a Subflow or Action](https://www.servicenow.com/docs/access?context=create-ai-acl&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US).
{#check-mcp-compatibility-playbooks__steps_bcm_334_qkc}

## What to do next

Add the playbook as an MCP tool to an MCP server. For more information, see [Add a playbook as an MCP tool](https://www.servicenow.com/docs/zRzNhFHY~37SAiewqOCTJQ "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.").