---
sourceDocument: Australia Enable AI
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/intelligent-experiences

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Enable AI

ft:clusterId :

    - platai

bundleId :

    - platai

workflow :

    - Platform


---

# Create a tool from a Playbook

# Create a tool from a Playbook {#ariaid-title1}

Release version: Australia  
Updated September 29, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Create a tool from a Playbook to expose it to Model Context Protocol (MCP) clients from an MCP Server Console.

## Before you begin

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

Minimum version required is Australia patch 6 or Brazil patch 1.

## Procedure

1. Select Playbook from these categories.  

2. On the form, fill in the fields.  

   Note:  
   The category is automatically populated if selected in the last modal.
   {#create-a-tool-from-a-playbook__table_l2y_lhm_hgc__entry__2}

   | Field | Description |
   |-|-|
   | Playbook | Select a compatible playbook from the list, that you want to add to the tool. If you're unable to see a playbook in the list, verify that the playbook is compatible. |
   | Label | Add 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: Add a specific, action-oriented description so AI clients can determine when to invoke the particular playbook. |
   | MCP Servers | From the <kbd class="ph userinput">MCP Servers</kbd> list, select a sever to which you want to add the tool. The AI clients will use the selected server to access the tool. |
   [Table 1. Tool form]

   {#create-a-tool-from-a-playbook__table_l2y_lhm_hgc}  
   Note:  
   A tool can be used by multiple servers so any changes that you make to a tool apply to all servers that use the tool. Before editing a tool, review which servers it's associated with to determine the impact for every server.  
   In the Tool inputs section, the fields associated with the capability are added.
3. You can proceed with default configurations, only.
4. Within the Tool inputs section, in the Enabled column, add the following two actions as tools to the MCP server.
   1. Check Playbook Status
   2. Check Playbook Execution  
      Note:  
      These Actions are available by default in the <kbd class="ph userinput">Action</kbd> category. You must add these Actions and enable them in the tools list. Some tool inputs are required and can't be turned off.
   {#create-a-tool-from-a-playbook__substeps_i4m_czr_jgc}
5. Select Create. {#create-a-tool-from-a-playbook__step_lyp_vjg_dkc}
{#create-a-tool-from-a-playbook__step_lyp_vjg_dkc}{#create-a-tool-from-a-playbook__steps_ubn_b25_skc}

## What to do next

Invoke the tool using an MCP client and verify that it works as expected. Launch MCP client to test end-to-end execution. For more information, see [Connecting to an MCP server from an MCP client](https://www.servicenow.com/docs/PF_Cub4lzK~3u0WPOtR5KQ "Connect to a Model Context Protocol (MCP) server from an MCP client by creating an OAuth inbound integration and configuring the client with the server details.").

See [Playbooks as an MCP tool](https://www.servicenow.com/docs/access?context=playbook-as-mcp-tool&version=australia&pubname=australia-build-workflows&ft:locale=en-US) to learn more.