Skip to content

Lightspeed MCP connector

Connect Lightspeed to Elaichi and Claude, ChatGPT, Cursor or any MCP client can look up sales, customers, products and suppliers, and keep customer and product records current, inside each person's own access with every action logged.

  • How it connects. OAuth or API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Lightspeed to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Lightspeed once

  1. Open Connections, choose Add connection, and pick Lightspeed.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Approve it in Lightspeed. Lightspeed's own window opens. Whoever approves it decides what this connection can reach.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

lightspeed
Lightspeed
Active Ants
Bigcommerce
Bol.com
Channable
Cin7
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Lightspeed MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Lightspeed MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Lightspeed MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Lightspeed to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Lightspeed through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Store operations

    Check today's sales across every outlet

    Ask how each outlet and register did today and get the answer from live Lightspeed sales, without opening the back office.

  • Merchandising

    Add a new product line in minutes

    Describe the new range, its brand and its pricing, and the products are created in Lightspeed ready for the shelf.

  • Customer service

    Fix a customer record after a visit

    Update a phone number, email or address the moment a shopper mentions it at the counter, and pull up their past sales while they wait.

  • Purchasing

    Raise a consignment for incoming stock

    Create the consignment for a supplier delivery before it arrives, then check it against what the supplier actually sent.

  • Ecommerce

    Keep product details consistent online and in store

    Ask which products are missing a brand or a description and correct them in Lightspeed before they go live.

  • Finance

    Pull a sale when a receipt is questioned

    Look up any Lightspeed sale by its number to see what was sold, at which register and for how much.

Try asking

  • “Which outlets had the most sales this week?”
  • “Create a product called Linen Tote under the Marlow brand.”
  • “Find the customer Priya Shah and update her phone number.”

See all 45 Lightspeed tools below

Compare

Elaichi vs Zapier MCP vs Composio for Lightspeed

All three can connect Lightspeed to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Lightspeed, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Lightspeed tools Allow or restrict single Lightspeed tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Lightspeed call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Lightspeed tools for your AI agents

45 tools are ready to call through Elaichi's MCP endpoint the moment you connect Lightspeed, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Lightspeed gets you

6 screens from the product, each doing one job for your Lightspeed account.

The agent

Ask about today's sales in plain words.

Questions about Lightspeed customers, products and sales, answered from live records.

  • customers
  • products
  • sales
  • consignments

Ask Elaichi to work across your apps.

Which outlets had the most sales this week?

Create a product called Linen Tote under the Marlow brand.

Find the customer Priya Shah and update her phone number.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One Lightspeed endpoint for every MCP client.

Claude, ChatGPT and Cursor reach Lightspeed through one governed endpoint, no SDK, no key handed around.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

45 Lightspeed tools, ready without writing code.

Customers, products, sales, suppliers, brands, outlets, registers and consignments, covered out of the box.

  • Create a Lightspeed customer
  • Delete a Lightspeed customer by ID
  • Get single Lightspeed customer by ID
  • List all Lightspeed customers
ElaichiTools
Tool Action Description
Create a Lightspeed customer Create Create a new customer in Lightspeed. Returns the created customer including id, first_name, last_name, email, customer_code, customer_group_id, balance, loyalty_balance, created_at, updated_at, and version. Requires first_name and last_name.
Delete a Lightspeed customer by ID Delete Delete a Lightspeed customer by id. Returns an empty 204 response on success. Required: id.
Get single Lightspeed customer by ID Get Get a single Lightspeed customer by id. Returns the full customer record including id, first_name, last_name, email, customer_code, customer_group_id, phone, loyalty_balance, and version. Required: id.
List all Lightspeed customers List List customers in Lightspeed with optional version-range and deleted-record filters. Returns: id, version, first_name, last_name, name, company_name, email, customer_code, customer_group_id, date_of_birth, gender, phone, mobile, fax, twitter, website, physical_address_1, physical_address_2, physical_suburb, physical_city, physical_state, physical_postcode, physical_country_id, postal_address_1,…
Update a Lightspeed customer by ID Update Update a customer in Lightspeed by id. Returns the updated customer including id, first_name, last_name, email, customer_group_id, loyalty_balance, and version. Required: id and first_name; the body also accepts last_name, email, phone, customer_group_id, and address fields.

Toolboxes

Every team gets its own Lightspeed toolbox.

Store staff see customers and sales, merchandising sees products and brands, purchasing sees consignments.

  • Store operations
  • Merchandising
  • Purchasing
  • Customer service
ElaichiToolboxes
Name Source template Tools Created

Store operations toolbox

Lightspeed · outlets, registers and sales

Lightspeed starter 18 Mar 4, 2026

Merchandising toolbox

Lightspeed · products and brands

— 9 Mar 2, 2026

Purchasing toolbox

Lightspeed · suppliers and consignments

— 24 Feb 27, 2026

Customer service toolbox

Lightspeed · customers and their sales

Lightspeed starter 6 Feb 19, 2026

Ecommerce toolbox

Lightspeed · product listings and pricing

— 31 Jan 30, 2026

Finance toolbox

Lightspeed · sales by outlet and register

— 12 Jan 22, 2026

Shared connections

Share one Lightspeed connection, never the key.

Connect once, share with teams, and teammates work through it without seeing a credential.

  • Flagship store
  • Downtown outlet
  • Online store
  • Merchandising
ElaichiConnections
Connection Scope Status Access
LI

Lightspeed (Flagship store)

Connected by Emily Carter

Personal • Active 1 team · 6 members
LI

Lightspeed (Downtown outlet)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
LI

Lightspeed (Online store)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
LI

Lightspeed (Merchandising)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
LI

Lightspeed (Purchasing)

Connected by Ryan Hayes

Personal • Active Not shared
LI

Lightspeed (Head office)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Lightspeed change names the person behind it.

When, who, what happened and which product or customer, in an append-only log.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Lightspeed Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Lightspeed Customers Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Lightspeed Customers List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule turns Lightspeed sales into a digest.

Sales are fetched, grouped by outlet, drafted, approved by a person, then posted back.

Lightspeed digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch customers

    Lightspeed

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Lightspeed

    Queued

Collections and dashboards

Lightspeed store health, computed on a schedule.

Four metrics, 14 days of sales created and a breakdown by team, with no model involved.

Lightspeed health

Refreshed 4 minutes ago · every 15 minutes · from the customers collection

Live

Customers

1,284 ↓ 12%

Products

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Customers created

Last 14 days

By team

Share of activity

Flagship store 34%

Downtown outlet 27%

Online store 21%

Merchandising 18%

FAQ

Frequently asked questions

How do I connect Lightspeed to Claude?

Connecting Lightspeed to Claude takes two steps. First, in Elaichi, choose Lightspeed and paste in the API key from your Lightspeed account, and you are connected. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp.

Does Lightspeed work with ChatGPT and Cursor as well as Claude?

Yes. Once Lightspeed is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect Lightspeed once and every client you use picks it up.

What can an AI agent actually do with my Lightspeed data?

An agent can look up Lightspeed customers, products, brands, suppliers, outlets, registers, users and sales, and answer questions about them in plain language. It can also create and update customers, products and brands, and create consignments for incoming stock. Because Lightspeed has a large set of tools, short concrete asks like "find the customer Priya Shah" work better than long paragraphs.

Does connecting Lightspeed give the AI my whole store?

No. The Lightspeed API key carries the access of the account that created it, and each person signs in to Elaichi as themselves, so every request runs under that identity. Elaichi can narrow what the AI is allowed to do in Lightspeed, for example read only, but it can never widen access beyond what the connected account already has.

Can my team share one Lightspeed connection?

Yes. One person connects Lightspeed in Elaichi and shares the connection with a team, and nobody else ever handles the Lightspeed API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every lookup and change in Lightspeed.

Can I stop an agent from deleting or changing things in Lightspeed?

Yes. In Elaichi, restrictions on the Lightspeed connection work per action, so you can allow reading sales and customers while blocking deletes, or blocking any change to products. A blocked action is never advertised to Claude, ChatGPT or Cursor at all, so no prompt, however worded, can reach it.

What happens to a Lightspeed connection when someone leaves?

Offboarding a person in Elaichi ends their access to Lightspeed at once, across every client they used. If they had shared a Lightspeed connection, it keeps working for everyone else on the team. Disconnecting Lightspeed once in Elaichi removes it from Claude, ChatGPT, Cursor and every other client in one step.

Does the Lightspeed MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Lightspeed is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Lightspeed?

Yes. Both let Claude, ChatGPT or Cursor use Lightspeed. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Lightspeed call.

How is Elaichi different from Composio for Lightspeed?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Lightspeed: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Lightspeed in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.