---
name: luxtron
description: Look up Luxtron Systems (Dubai, UAE) lighting products and item codes, plan DALI lines, size MCBs for LED drivers, turn A.A.G. Stucchi ONETRACK or EVO track runs into a parts list, build submittal and datasheet links, read Luxtron news and guides, and draft an enquiry to Luxtron. Use when the user asks about Luxtron, Helvar drivers or controls, Stucchi track, EUTRAC, DALI line counts, breaker sizing for drivers, or wants real lighting item codes for a project in the UAE or GCC.
---

# Luxtron catalogue and tools

Luxtron Systems supplies LED components (Helvar Components drivers and modules), lighting controls (Helvar, DALI-2), A.A.G. Stucchi and EUTRAC track systems and fixtures, connectors, Almeco decorative materials, and its own luminaires. The Luxtron MCP server gives you the live catalogue and the same calculators as https://luxtron.net/tools.

- Server URL: `https://luxtron.net/mcp`
- Transport: streamable HTTP, stateless, JSON responses
- Auth: none
- Setup page for people: https://luxtron.net/tools/mcp-server

## 1. Make sure the tools are available

If you already have tools named `search_products`, `find_item_code` and `plan_track_run` from a server called `luxtron`, skip to section 2.

Otherwise install the server in whatever client you run in:

- Claude Code: `claude mcp add --transport http luxtron https://luxtron.net/mcp`, then restart the session or run `/mcp` to confirm it is connected.
- Cursor: add to `~/.cursor/mcp.json` (or `.cursor/mcp.json` in the project), then enable it under Settings, MCP:
  ```json
  { "mcpServers": { "luxtron": { "url": "https://luxtron.net/mcp" } } }
  ```
- VS Code (Copilot agent mode): add to `.vscode/mcp.json`:
  ```json
  { "servers": { "luxtron": { "type": "http", "url": "https://luxtron.net/mcp" } } }
  ```
- Claude (web or desktop app) and ChatGPT: these are set up by the user in the app's settings, not by you. Tell the user: in Claude, Settings, Connectors, Add custom connector, paste `https://luxtron.net/mcp`. In ChatGPT, turn on Developer mode (Settings, Apps, Advanced settings), then create an app with that URL and no authentication.
- Any other MCP client: add a remote server with the URL above.

### No MCP client? Call it over HTTP

If you can run shell commands but cannot add MCP servers, call the endpoint directly with JSON-RPC. No initialize step is needed. The `accept` header must list both types.

```bash
curl -s https://luxtron.net/mcp \
  -H 'content-type: application/json' \
  -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"find_item_code","arguments":{"code":"LL120HE"}}}'
```

The answer is in `result.content[0].text`, a JSON string. Use `"method":"tools/list","params":{}` to see every tool with its full input schema.

## 2. Rules

- Never invent item codes, specs or links. If a tool does not return it, say you do not know and offer `draft_enquiry`.
- Prices and stock are not available. For a quote, use `draft_enquiry` or send the user to https://luxtron.net/contact.
- UAE and GCC projects use 230 V parts. The catalogue also has some US-market parts (UL, 120/277 V, lengths in feet); do not suggest those for the region, and point it out if the user picks one.
- Datasheets and submittals are PDFs the user downloads in their browser from the link you give them. Tell them to open the link and press the download button. You cannot attach the PDF yourself.
- Before `build_submittal` (email required) or a datasheet request through `get_product`, ask the user for their email and, if they have one, the project name and company. Never make up an email. Luxtron uses it to follow up.
- Calculator results are a planning aid, not a design sign-off. Say so when the result feeds a real design, and suggest checking against the exact product datasheet.
- Lists are paged. When a result has `next_offset`, call again with `offset` (or `variant_offset` for a product's variant table) set to it if you need more. Do not page through everything; narrow the query instead.

## 3. Tools

| Tool | Use it for | Key arguments |
|---|---|---|
| `search_products` | Finding products by words or specs | `query`, `category`, `brand`, `limit`, `offset` |
| `get_product` | Full specs, variants, datasheet and submittal links for one product | `slug`, `code` (variant), `variant_offset`, `email`, `project`, `company` |
| `find_item_code` | What an item code is, from a full or partial code | `code`, `offset` |
| `calc_mcb` | Drivers per breaker and breakers needed | `drivers`, `curve`, `rating_a`, `drivers_per_c16`, `mains_current_a`, `load_factor` |
| `plan_dali_line` | DALI lines and power supplies for gear and devices | `rows` (type, qty, ma), `supply`, `margin_pct`, `groups` |
| `plan_track_run` | Parts list for ONETRACK or EVO track runs | `system`, `profile`, `finish`, `runs`, `lengths_m`, `part_versions` |
| `get_news` | Luxtron news, project stories and technical guides | `query`, `category`, `slug`, `limit`, `offset` |
| `build_submittal` | A link to the submittal builder with products preselected | `items` (slug, variant_code), `email`, `project`, `company` |
| `draft_enquiry` | A mailto link with a drafted email to Luxtron | `subject`, `message`, `items`, `name`, `company` |

## 4. Typical flows

**"What is this code?"** `find_item_code`, then `get_product` with the returned `slug` and `variant_code` for full specs.

**"Which driver for ...?"** `search_products` with the key specs (for example "linear driver dali 700mA"), then `get_product` on the best two or three to compare their spec tables. Answer with the codes and links.

**Breakers for drivers.** Get the driver with `get_product` and read its inrush table (drivers per C 16 A breaker) and mains current from the specs or datasheet, then `calc_mcb`. If the datasheet figures are not in the specs, say the defaults are Helvar LL120HE-DA-100-800 figures.

**DALI lines.** `plan_dali_line` with one row per device type. Use the datasheet bus current where you have it; sensors with their own supply draw 0 mA. Report the line count, which limit decided it, and the notes.

**Track runs.** Ask for the system (ONETRACK 230 V or EVO 48 V), profile, finish and each run's shape and lengths if the user has not given them. Default to ONETRACK profile A in black with 2 m track. Call `plan_track_run`, then present the parts table with codes, and pass on the warnings and info lines; they carry the installation caveats.

**Submittal.** After the products are settled, ask for the email (and project and company), then `build_submittal` with every product's slug and, for track fixtures, the `variant_code`. Give the user the link and tell them to open it, check the list, and press the button to download the PDF.

**Quote or question for Luxtron.** `draft_enquiry` with the user's request in their words, the item codes and quantities, and the product links. Give the user the `mailto` link (it opens their email app with the draft; nothing is sent until they press send) and the contact page as the alternative. Do not invent quantities.

**News and guides.** `get_news` with a topic for background, for example "DALI-2" or "ONETRACK feed", then `get_news` with the `slug` to read the article.

## 5. Contact

Luxtron Systems, Al Qusais, Dubai, UAE. info@luxtron.net, +971 4 327 3594, https://luxtron.net/contact