Skip to main content
mcp.vori.com is in alpha. It’s a new, separate integration point, so it doesn’t yet cover as much as app.vori.com or the Vori mobile app. Expect gaps and rough edges while it matures.
A note on LLM risk. You are connecting a third-party AI assistant to your live store data. LLMs can misinterpret requests, call the wrong tool, or state things confidently that are inaccurate. Review what an assistant is about to do before you rely on its output, especially before taking any action based on it. If you want to be safe, create a user with the Read-only role at the banner level and connect your AI client with that account instead of your own.
Vori runs a grocer-facing Model Context Protocol (MCP) server at mcp.vori.com. Any MCP-compatible AI client — Claude, Cursor, ChatGPT — can connect to it and get authenticated access to your store’s data: products, departments, inventory, invoices, and more. There is no API key to request or app to install — you authenticate with your normal Vori credentials and every tool call is scoped to your permissions, exactly like the web app.

​
How it works

Every request goes through an authenticated HTTPS connection. Authentication validates your credential (any credential type Vori already accepts — Firebase, Google, or Vori-managed), and authorization then checks the permission declared on the tool you’re calling against your account, so retail users only ever see their own banner’s data.

​
Connect your AI client

The server speaks the MCP Streamable HTTP transport at:
Opens Claude.ai with the connector name and URL prefilled — just click Add, then Connect.
Prefer to set it up by hand?
1

Open connector settings

Go to Settings → Connectors.
2

Add a custom connector

Click Add custom connector at the bottom of the Connectors section.
3

Name and point it at Vori

Set the name to Vori, and the URL to https://mcp.vori.com.
4

Connect

Click Add, then Connect — a browser window opens for you to sign in with your Vori credentials.

​
Video walkthroughs

Connecting Vori MCP to Claude:
Connecting Vori MCP to ChatGPT:

​
Schedule and send reports

Once connected, you can put your AI client to work on recurring tasks. This walkthrough uses Vori MCP with Claude Cowork to schedule and send a report:
The same approach works for scheduled delivery of any data Vori MCP can access — send it to email, SFTP, an API, or wherever else your workflow needs it.

​
Troubleshooting

If the client shows a generic “Unauthorized” error, double check the endpoint URL matches exactly (including scheme) — a mismatch causes token validation to fail silently.
  • No tools showing up after connecting — restart your AI client; some clients only pick up a server’s tool list on startup or reconnect.
  • Repeated login prompts — reconnect the server in your client’s settings to refresh the session.

​
Available tools

Tools are grouped by domain. Every tool enforces the same permissions you’d see in the Vori dashboard.
  • cube_meta — returns the semantic model (cubes, measures, dimensions) available for querying; call this first
  • cube_query — execute a structured analytics query, scoped to your banner/stores
  • create_department — create a new department (optionally a sub-department)
  • get_department_by_id — retrieve a single department by ID
  • list_departments — list departments in a store, filterable by name
  • update_department — update a department, including deactivating or reactivating it
  • get_discount_by_id — retrieve a discount by ID
  • list_discounts — list discounts for the banner, filterable by name
  • list_food_modifier_categories and related tools to create, update, and delete modifier categories and their modifiers, look up modifiers assigned to a product, and analyze a store’s modifier setup for gaps
  • docs_fetch — fetch the full content of a help doc by slug returned from docs_search
  • docs_search — search the Vori help-center docs (help.vori.com)
  • get_product_inventory — retrieve the current on-hand inventory quantity for a product
  • get_item_modifier_by_id — retrieve an item modifier (per-store charges like bottle deposits) by ID
  • list_item_modifiers — list a store’s item modifiers, filterable by name
  • get_invoice_raw_extracted_values — the raw extracted line values on an invoice’s active revision, before any Extraction Rule transformations
  • get_invoice_standardized_line_items — the standardized line items after Extraction Rules and reconciliation have run
  • create_product — create a new retail product
  • get_product_by_id — retrieve a retail product by ID
  • list_products — list products, filterable by store, department, or barcode
  • search_products — search products by name or barcode across one or more stores
  • update_product — update an existing retail product
  • get_store_by_id — retrieve a store by ID
  • list_stores — list all accessible stores, paginated
  • get_transaction_by_id — retrieve a checkout transaction by ID, including line items, payments, and linked refunds
  • list_transactions — list completed transactions for a store, filterable by lane, employee, date range, or shopper-facing ID
  • get_lane_by_id — retrieve a checkout lane by ID
  • list_lanes — list checkout lanes, filterable by store or by whether the lane is virtual (one that only attributes orders and has no physical terminal); both kinds are returned by default

​
Questions or issues?

Reach out through your normal Vori support channel.

Related topics

Connect XeroTroubleshoot Network Connectivity Issues with the POSHow to troubleshoot Zebra label printer connection issues