---
sourceDocument: Australia Retail Industry
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/retail-industry

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Retail Industry

ft:clusterId :

    - rahi

bundleId :

    - rahi

workflow :

    - Customer and Industry


---

# Set up the Retail MCP Server

# Set up the Retail MCP Server {#ariaid-title1}

Release version: Australia  
Updated September 23, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Install the Retail MCP Server, connect your AI client to it, and give store staff the roles they need, so they can work with Retail Service Management from their AI assistant.

## Before you begin

These plugins must be active on the instance:

* CSM MCP Server (com.sn_csm_mcp_server). It also provides the platform MCP framework (com.sn_mcp_server).
* Retail Core (com.sn_retail_core)
* Optional: Retail Store Services (com.sn_rtl_stre_servcs). The four case tools install only when this plugin is active.

Role required: admin

## About this task

The Retail MCP Server doesn't ship its own OAuth configuration. The platform MCP framework generates an OAuth provider and client for the server when the app is installed. Your AI client connects with that OAuth client.

## Procedure

1. Install the Retail MCP Server application from the ServiceNow Store.  
   The Retail MCP Server and its tools are registered. If Retail Store Services isn't active, only Get my retail store and Get store devices are registered.
2. Locate the OAuth client that the platform MCP framework generated for the Retail MCP Server, in the global scope.
3. Add callback URLs as required for MCP clients.
4. Give the OAuth client ID and secret to the administrator of your MCP-compatible AI client, and configure the client to connect to your instance.
5. Assign roles to the store staff who will use the tools.  
   * To find their store and devices: sn_retail.associate_contributor or sn_retail.associate_fulfiller
   * To create, track, and update cases: sn_rtl_stre_servcs.contributor

   For instructions, see [Assign roles to Retail users](https://www.servicenow.com/docs/CWuCsNDTMdedjCJmB01WCg "Assign specific roles to give retail users visibility into organizations and the hierarchies they manage.").
6. Make sure each user is a member of the retail store they work in.  
   The tools look up a user's store from their store membership. A user who isn't a member of any store gets an empty result. For instructions, see [Add members to a retail organization](https://www.servicenow.com/docs/Ohz6cbL41ZeIiR8zPmsThw "Add members to your organization to enable them to view and complete tasks within your retail organization.").
{#rahi-retail-mcp-server-set-up__steps_rtl_mcp_setup}

## Result

The AI client discovers the Retail MCP Server and its tools. Store staff who hold the required roles can invoke the tools from their assistant.
**Related concepts**   

* [Retail MCP Server](https://www.servicenow.com/docs/o7dFGR4jPUmRgZSSh2_LBg "The Retail MCP Server exposes Retail Service Management capabilities as Model Context Protocol (MCP) tools, so store staff can find their store and devices and raise, track, and update Store Services cases from their AI assistant.")  
**Related reference**   

* [Retail MCP Server roles and data access](https://www.servicenow.com/docs/3IDbL~n0Cl3kgOT_Y_ln_A "Access to the Retail MCP Server is controlled at two levels: roles determine who can invoke each tool, and the caller's own record access determines what data each tool returns or changes.")