TagTroniX

TagTroniX · AI connections (MCP)

Connect TagTroniX to your AI assistant

The TagTroniX MCP server lets an AI assistant work with your store in TagTroniX: read your product catalog, prices and electronic shelf label (ESL) status, and, when you allow it, update products, templates and labels. It uses the open Model Context Protocol and works with Claude, ChatGPT and other MCP clients.

Server URL: https://app.tagtronix.com/mcp
Sign-in: OAuth 2.1 with PKCE, using your TagTroniX account. One connection gives access to one store you choose during sign-in.

Before you start

Connect Claude

  1. In Claude (web or desktop), open Customize → Connectors (in some versions Settings → Connectors) and choose Add custom connector.
  2. Name: TagTroniX. Remote MCP server URL: https://app.tagtronix.com/mcp.
  3. Open Advanced settings and enter OAuth Client ID claude-tagtronix-public-v1. Leave the client secret empty.
  4. Choose Add, then Connect. A TagTroniX page titled “Connect Claude to TagTroniX” opens.
  5. Sign in with your TagTroniX login, select the store, review the permissions and choose Allow access.
  6. Back in Claude, enable the TagTroniX tools in a conversation and ask, for example, “Show my ESL fleet status” or “Find the price of product SKU 1001”.

On Team and Enterprise plans an owner may need to add the connector for the organization first. See Anthropic’s guide: Get started with custom connectors using remote MCP.

Connect ChatGPT

  1. In ChatGPT on the web, open the connectors / apps settings and choose to add a custom MCP server (developer mode may be required on your plan).
  2. Server URL: https://app.tagtronix.com/mcp, authentication: OAuth.
  3. A page titled “Connect ChatGPT to TagTroniX” opens. Sign in, select the store and allow access.

See OpenAI’s guide: Custom MCP servers.

Other MCP apps and your own developers

Other clients (for example IDE assistants or software your developers build) need their own OAuth client. Email info@tagtronix.com with the app name and its exact redirect URI (HTTPS on a public domain, or http://localhost with a fixed port). We issue a client ID, read-only by default; write permissions are added on request. Public clients use PKCE and have no client secret.

What it can do

Read tools never change anything. Change tools act only on the connected store and only when the matching permission was approved. Each tool is labelled for the assistant as read-only or as changing data, so assistants that ask before actions can do so.

Read only (20 tools)

AreaTools
Getting startedget_setup_menu (optional setup guides), get_setup (one workflow), get_store_overview (identity, store, sync and ESL summary)
Account and storewhoami, get_store
Catalog and priceslist_products, get_product_status (intended vs. vendor price), get_sync_status, list_product_categories, get_product_category, list_product_images
ESL labels and gatewaysget_device_stats, list_devices, get_device, get_device_diagnostics, get_device_capabilities, list_device_models, list_gateways
Label templateslist_templates, get_template_design

Changes data (11 tools)

ToolWhat it doesPermission
upsert_productCreate or update one product (name, prices)catalog:write
set_product_categoryAssign or clear a product categorycatalog:write
add_product_imageAdd an image from a public HTTPS URL (fetched and validated by TagTroniX)catalog:write
delete_product_imageDelete one product imagecatalog:write
reorder_product_imagesSet the image order (up to five)catalog:write
create_templateCreate an ESL template (does not change any label)templates:write
assign_esl_templatesAssign templates to up to four labels, optionally refresh themdevices:template_assign, devices:refresh
refresh_deviceRe-render and re-send one labeldevices:refresh
retry_syncRetry synchronization for one labelsync:retry
remediate_syncDiagnose sync problems; a dry run unless explicitly confirmedsync:write
update_storeChange the store’s display name onlystores:write

Label refresh, retry and template assignment can change what physical shelf labels display. A successful request means TagTroniX accepted the job; it is not proof that a label has already shown the new content.

Permissions requested

You see and approve these on the TagTroniX sign-in page. Read permissions are required; write permissions are only used by the change tools above.

PermissionAllows
stores:readSee the connected store and account identity
catalog:readRead products, prices, categories, images and sync status
devices:readRead ESL labels, gateways, models and diagnostics
templates:readRead ESL label templates
catalog:writeCreate and update products, categories and product images
templates:writeCreate ESL templates
devices:template_assignAssign templates to labels
devices:refreshRefresh labels
sync:retry / sync:writeRetry and remediate label synchronization
stores:writeChange the store display name
offline_accessStay connected without signing in again each session (refresh token)

Security and data

Disconnect

Remove or disconnect the TagTroniX connector in your assistant’s connector settings. To revoke access on our side as well, contact info@tagtronix.com.

Help

Questions or problems connecting: Support · info@tagtronix.com · 1-888-884-9860.

Last updated: November 15, 2026