Retail MCP Server is for retail organizations running ServiceNow retail — store teams and the HQ teams that support them. Work that until now meant opening the right form and filling it in can be done by asking an AI assistant instead.
The app is the layer that makes that possible: it exposes ServiceNow retail capabilities as tools any AI assistant can call, so a user describes the situation in plain language — "the third register is frozen" — and the assistant identifies the store, matches the device, raises the correct record, and reports back. Records arrive complete and correctly categorized, so less time goes into chasing detail before work can start, and requests that were never worth a form get captured.
Every tool delegates to existing ServiceNow retail logic rather than reimplementing it, and runs as the calling user — so your access controls, roles, and record-level visibility apply unchanged, with no separate integration layer to secure or maintain. It serves every retail persona from one server, and new retail capabilities register on it as they ship.
• A Retail MCP Server that AI assistants connect to — one endpoint for all retail tools, present and future.
• Store context (1 tool) — resolves which store the user works in, so nothing needs to be asked or typed.
• Store devices (1 tool) — matches a device from a plain-language description.
• Store Services cases (4 tools) — raise break-fix or inquiry cases to HQ, check status, comment, answer HQ, accept/reject a resolution, close.
• Runs as the calling user: existing ACLs and per-store visibility apply unchanged.
- New
- Retail MCP Server is now generally available (GA). It was previously available only as a Controlled Availability release.
Required
- Retail Core (com.sn_retail_core)
- CSM MCP Server (com.sn_csm_mcp_server)
Optional
- Retail Store Services (com.sn_rtl_stre_servcs) — the four Store Services case tools install only when this plugin is active