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

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Retail Industry

ft:clusterId :

    - rahi

bundleId :

    - rahi

workflow :

    - Customer and Industry


---

# Retail MCP Server

# Retail MCP Server {#ariaid-title1}

Release version: Brazil  
Updated September 23, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
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.

Without the Retail MCP Server, a store associate who uses an AI assistant has to leave the conversation and open the portal to find their store, check on a case, or report broken equipment. The Retail MCP Server lets the assistant do this work on the associate's behalf, using the associate's own identity and access rights.

## One server for all retail tools {#rahi-retail-mcp-server-overview__rahi-retail-mcp-server-overview-hub}

The application registers a single MCP server, Retail MCP Server. MCP-compatible AI clients, such as ServiceNow Otto, Now Assist, and Claude, discover and connect to this one server. Every retail tool registers under it, so new retail capabilities become available to the assistant without a new server being set up.

## Available tools {#rahi-retail-mcp-server-overview__rahi-retail-mcp-server-overview-tools}

The Retail MCP Server provides six tools. The assistant usually chains them: it identifies the store first, then the device, and then the case.

Get my retail store
:   Returns the stores the signed-in user belongs to.

Get store devices
:   Returns the devices registered to a store, so the assistant can match "the freezer in aisle 3" to a real device.

Create store break-fix case
:   Reports a broken or faulty device to HQ.

Create store inquiry case
:   Sends HQ a question about store policy, process, or operations.

Get my store services cases
:   Lists the break-fix and store inquiry cases the user raised.

Update store services case
:   Comments on, accepts or rejects a proposed resolution for, or closes one of the user's cases.

The four case tools install only when the Retail Store Services plugin is active. The store and device tools work without it.

## Access and identity {#rahi-retail-mcp-server-overview__rahi-retail-mcp-server-overview-access}

Each tool runs as the calling user. The tools identify the user from the authenticated session, never from a user name or ID that the assistant supplies, and they return only records that the user can already read in the platform. Each tool also requires a specific role before it can be invoked. For details, see [Retail MCP Server roles and data access](https://www.servicenow.com/docs/ERyHQoUNWUdeDV8AX76_4g "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.").

## What the Retail MCP Server doesn't do {#rahi-retail-mcp-server-overview__rahi-retail-mcp-server-overview-scope}

* It provides no user interface. Store staff work entirely in their AI assistant.
* It doesn't create, update, or delete devices. Device access is read-only.
* It supports only break-fix and store inquiry cases.
* It doesn't let callers change a case's state directly, or its priority, assignment, or resolution code. Callers can only comment, respond to a proposed resolution, or close the case.
* It doesn't choose a primary store for a user who belongs to several stores. The assistant asks the user which store to use.
* **[Set up the Retail MCP Server](https://www.servicenow.com/docs/tPcZ_xKIWZ_ptYSL5Goupw)**   
  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.
* **[Report a broken device from your AI assistant](https://www.servicenow.com/docs/wRxRIjLS5yLUm5w9k~r3NQ)**   
  Create a break-fix case for broken or faulty equipment in your store by describing the problem to your AI assistant, without opening the portal.
* **[Ask HQ a question from your AI assistant](https://www.servicenow.com/docs/0K7arqkdFEVtgCYnu6860g)**   
  Get an official answer from HQ about store policy, process, or operations by raising a store inquiry case from your AI assistant.
* **[Track and update your cases from your AI assistant](https://www.servicenow.com/docs/llVmrSwSUJ~2l2gCjCc_uA)**   
  Check the status of your break-fix and store inquiry cases, answer questions from HQ, respond to proposed resolutions, and close cases, all from your AI assistant.
* **[Retail MCP Server tools](https://www.servicenow.com/docs/I_PxBPWEVvXDIVDfsjW4Pg)**   
  The Retail MCP Server provides six tools. Each entry lists the tool's purpose, inputs, what it returns, whether it changes data, and what it requires.
* **[Retail MCP Server roles and data access](https://www.servicenow.com/docs/ERyHQoUNWUdeDV8AX76_4g)**   
  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.

**Related concepts**   

* [ServiceNow Otto for Break-Fix and Store Audit overview](https://www.servicenow.com/docs/kYJQbpXDC~6wkDIcYQbrvQ "The ServiceNow Otto conversational interface connects to Break-Fix Case Management and Store Audit Plans workflows. Store staff can submit, troubleshoot, and track cases without accessing the RSM portal.")  
**Related tasks**   

* [Set up the Retail MCP Server](https://www.servicenow.com/docs/tPcZ_xKIWZ_ptYSL5Goupw "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.")  
**Related reference**   

* [Retail MCP Server tools](https://www.servicenow.com/docs/I_PxBPWEVvXDIVDfsjW4Pg "The Retail MCP Server provides six tools. Each entry lists the tool's purpose, inputs, what it returns, whether it changes data, and what it requires.")
* [Retail MCP Server roles and data access](https://www.servicenow.com/docs/ERyHQoUNWUdeDV8AX76_4g "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.")
* [Components Moveworks Integration for Break-Fix and Store Audit](https://www.servicenow.com/docs/wtK0SoDqZ7k_UaXrQkeUPg "Technical details on data flow, integration points, API usage, and supported operations for Moveworks with Break-Fix Case Management and Store Audit Plans.")

