lightspeed-x
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LIGHTSPEED_TOKEN | Yes | Personal token from Lightspeed X. Required. | |
| LIGHTSPEED_DOMAIN | Yes | Store prefix, host, or URL. Accepts a bare prefix (e.g. 'mystore'), a host (e.g. 'mystore.retail.lightspeed.app'), or a full URL. Required. | |
| LIGHTSPEED_ENV_FILE | No | Explicit path to a credential file. The plugin sets this to ${CLAUDE_PLUGIN_DATA}/credentials.env | |
| LIGHTSPEED_MAX_SALES | No | Safety cap per sales call. | 200000 |
| LIGHTSPEED_API_VERSION | No | API version path segment. | 2026-01 |
| LIGHTSPEED_DEFAULT_ACCOUNT | No | Account used when a tool omits `account`. Defaults to the first account. | first account |
| LIGHTSPEED_SEEK_MARGIN_DAYS | No | Days of margin when seeking the version anchor. | 1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| lightspeed_setup_statusA | Report whether this server has working Lightspeed credentials, and if not, the exact file path to create and what to put in it. Call this first when any Lightspeed tool fails with a credential error, when the user says Lightspeed is not connected, or when setting the server up for the first time. Safe to call at any time and never returns the token itself. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tool purposes. The tool's role as a credential/setup status check is clearly defined.
A single tool name cannot exhibit inconsistency. 'lightspeed_setup_status' is descriptive, snake_case, and follows a predictable pattern for this server.
A single setup/status tool is an extreme mismatch for a server named 'lightspeed-x'. The tool explicitly references other Lightspeed tools that do not exist, making the surface feel incomplete and unbalanced.
The server provides no actual Lightspeed operations—only a credential status check. This is severely incomplete for a Lightspeed integration domain and leaves agents with no way to perform real tasks.