Shoplazza MCP connector
The Shoplazza connector brings store analytics, blog articles, automatic discounts and app proxies to Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, with each person working inside their own Shoplazza access and every call logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Which search keywords brought the most traffic this week?
Working in Shoplazza with Elaichi
-
List all Shoplazza access scopes
-
List all Shoplazza analytics landing pages
-
List all Shoplazza analytics overview
How to connect Shoplazza to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Shoplazza MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Shoplazza MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Shoplazza MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Shoplazza MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Shoplazza MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Shoplazza to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
What teams do with Shoplazza through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Shoplazza is logged.
-
Marketing
Spin up a discount for the weekend sale
Ask for an automatic discount on the sale collection with the right dates and amount, then adjust it later from the same chat when the plan changes.
-
Content
Draft and publish the next blog article
Turn a few notes into a finished Shoplazza article, assign the right author, and file it under the correct blog without opening the store admin.
-
Growth
See which search keywords bring buyers
Pull the search keywords and traffic channels behind this month's visits and ask which ones actually turned into orders.
-
Merchandising
Find the products and SKUs that sold
Get the week's product and SKU analytics in one answer, compare them with last week, and decide what to feature on the home page.
-
Marketing
Check which UTM campaigns actually converted
Ask how each UTM campaign and landing page performed, then summarize the result for the Monday meeting in plain language.
-
Engineering
Set up an app proxy in minutes
Create, inspect or remove a Shoplazza app proxy by describing what it should do, with every change recorded against the person who asked for it.
Try asking
- “Which search keywords brought the most traffic this week?”
- “Draft a blog article announcing the spring sale.”
- “Show the top landing pages by conversions for last month.”
What connecting Shoplazza gets you
6 screens from Elaichi, each doing one job for your Shoplazza account.
Ask Elaichi to work across your apps.
Which search keywords brought the most traffic this week?
Draft a blog article announcing the spring sale.
Show the top landing pages by conversions for last month.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask Shoplazza questions in plain language.
Get answers from live analytics, articles and discounts without opening the store admin.
Copy the endpoint
AI apps
One endpoint connects Shoplazza to every client.
Claude, ChatGPT and Cursor reach Shoplazza through one governed endpoint, no SDK and no shared key.
Tool catalog
316 Shoplazza tools, ready without writing code.
Analytics, articles, blogs, discounts and app proxies, each covered without custom code.
Toolboxes
Every team gets its own Shoplazza toolbox.
Marketing keeps discounts, content keeps articles, and each toolbox is scoped to one team.
Shared connections
Share a Shoplazza connection, never the key.
One person connects the store, teammates work through it and never see the API key.
Audit log
Every Shoplazza action is logged with a name.
See who created a discount or edited an article, when, and on which resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Shoplazza digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch articles
Shoplazza
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Shoplazza
Queued
Workflows
A schedule starts Shoplazza work, a person approves.
Analytics are fetched, grouped, drafted into a digest, approved, then posted back to Shoplazza.
Shoplazza health
Refreshed 4 minutes ago · every 15 minutes · from the articles collection
Articles
1,284 ↓ 12%
Blogs
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Articles created
Last 14 days
By team
Share of activity
Marketing 34%
Content 27%
Growth 21%
Store US 18%
Collections and dashboards
Shoplazza store health, computed without a model.
Four metrics, fourteen days of articles created and a team breakdown, refreshed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Shoplazza
All three can connect Shoplazza to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| 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 Shoplazza tools | Allow or restrict single Shoplazza 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 Shoplazza 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 | Free for one person; $15 per user per month on Gold. | 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.
Shoplazza tools for your AI agents
316 tools are ready to call through Elaichi's MCP endpoint the moment you connect Shoplazza, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect Shoplazza to Claude?
Connect Shoplazza in Elaichi by pasting your store's API key, then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. There is no OAuth application to register and no client ID or secret to generate. Once connected, you sign in to Elaichi as yourself and Claude can work with Shoplazza on your behalf.
Does Shoplazza work with ChatGPT and Cursor as well as Claude?
Yes. Shoplazza is connected once in Elaichi, and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You never set up Shoplazza separately for each client.
What can an AI agent actually do with my Shoplazza data?
An agent connected to Shoplazza can read your store analytics, including landing pages, search keywords, traffic channels, UTM campaigns, products and SKUs, and explain what they mean. It can also write and update blog articles, create and change automatic discounts, and manage app proxies. Short, concrete asks such as "top search keywords this week" work better than long paragraphs.
Does connecting Shoplazza give the AI access to the whole store?
No. Every call to Shoplazza runs inside the access of the person who signed in to Elaichi, so an agent sees only what that person can see in the store. Elaichi can narrow that access further with roles and restrictions, and it never widens it beyond what the Shoplazza API key allows.
Can I stop an agent from deleting or changing things in Shoplazza?
Yes. Restrictions in Elaichi work per action, so you can restrict deleting articles or changing discounts in Shoplazza for a role or for one person while leaving analytics open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.
What happens to a Shoplazza connection when someone leaves?
Offboarding a person in Elaichi ends their access to Shoplazza at once, across every client they used. A shared Shoplazza connection keeps working for everyone else on the team. If you want the store gone entirely, disconnecting Shoplazza once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent together.
Does the Shoplazza MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Shoplazza 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, Microsoft Copilot, 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 Shoplazza?
Yes. Both let Claude, ChatGPT or Cursor use Shoplazza. 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 Shoplazza call.
How is Elaichi different from Composio for Shoplazza?
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 Shoplazza: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Shoplazza in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot