Get started

iStores AI Storefront Designer

Use this MCP server when you want an AI assistant to redesign an iStores storefront safely.

The AI can read the current store CSS/JS, create a rollback snapshot, publish new CSS/JS, upload media, update products, and roll back if something goes wrong.

The MCP server is hosted by iStores. You do not need to install or host a server.

Never paste your API token into a public chat, GitHub issue, screenshot, or documentation page.

Start Here

You need three things:

Item	What it is
MCP URL	`https://api.istores.co.il/mcp`
API token header	`Authorization: Bearer YOUR_ISTORES_API_TOKEN`
Company ID	Your iStores `companyId`, for example `9906`

The API token is used in the MCP connection settings.

The companyId is given to the AI in the chat.

Step 1: Connect the MCP Server

Choose your AI tool and follow the matching setup.

Use these same values everywhere:

Field	Value
Server name	`iStores Design Ops`
MCP URL	`https://api.istores.co.il/mcp`
Header name	`Authorization`
Header value	`Bearer YOUR_ISTORES_API_TOKEN`

Use the Authorization header with the Bearer scheme.

Codex

Use this for Codex CLI/Desktop when you can edit the Codex config.

Open:

Code(text)
 
~/.codex/config.toml

Add:

Code
 
[mcp_servers.istores-design-ops]
url = "https://api.istores.co.il/mcp"
enabled = true

[mcp_servers.istores-design-ops.http_headers]
"Authorization" = "Bearer YOUR_ISTORES_API_TOKEN"

Restart Codex, then check MCP servers:

Code(bash)
 
codex mcp list

If Codex has a UI for MCP servers, add the same URL and header there instead.

Claude Code

Run this in your terminal:

Code(bash)
 
claude mcp add --transport http --scope user \
  --header "Authorization: Bearer YOUR_ISTORES_API_TOKEN" \
  istores-design-ops https://api.istores.co.il/mcp

Verify:

Code(bash)
 
claude mcp list

Inside Claude Code, run:

Code(text)
 
/mcp

Claude / Claude Desktop

Claude supports remote MCP through Custom Connectors, but the exact authentication options depend on your plan and current Claude UI.

Try this first:

Open Claude settings.
Go to Connectors or Integrations.
Add a custom connector.
Use URL:

Code(text)
 
https://api.istores.co.il/mcp

If Claude lets you add a custom API key/header, use:

Code(text)
 
Header name: Authorization
Header value: Bearer YOUR_ISTORES_API_TOKEN

If Claude does not let you add an Authorization header, this direct setup will not work yet. Use Claude Code, Codex, Cursor, VS Code, Windsurf, Antigravity, Manus, or ask iStores support for an OAuth/bridge setup.

Manus

Use this for Manus Custom MCP Servers.

Open Manus.
Go to Settings.
Open Integrations or Connectors.
Open Custom MCP Servers.
Click Add Server.
Choose direct/custom configuration.
Fill in:

Field	Value
Server name	`iStores Design Ops`
Transport	HTTP
Server URL	`https://api.istores.co.il/mcp`
Authentication	API key or custom header
Header name	`Authorization`
Header value	`Bearer YOUR_ISTORES_API_TOKEN`

Then test the connection. Manus should show the iStores tools.

Google Antigravity

Use this for Antigravity desktop or Antigravity CLI.

Open the MCP raw config from the UI:

Code(text)
 
Agent panel -> Manage MCP Servers -> View raw config

Common config paths:

App	Config path
Antigravity Desktop	`~/.gemini/antigravity/mcp_config.json`
Antigravity CLI	`~/.gemini/antigravity-cli/mcp_config.json`
Workspace config	`.agents/mcp_config.json`

Add:

Code(json)
 
{
  "mcpServers": {
    "istores-design-ops": {
      "url": "https://api.istores.co.il/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ISTORES_API_TOKEN"
      }
    }
  }
}

If your Antigravity version expects httpUrl instead of url, use this shape:

Code(json)
 
{
  "mcpServers": {
    "istores-design-ops": {
      "httpUrl": "https://api.istores.co.il/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ISTORES_API_TOKEN"
      }
    }
  }
}

Restart Antigravity or reload MCP servers after saving.

Gemini CLI

Run:

Code(bash)
 
gemini mcp add -s user -t http \
  -H "Authorization: Bearer YOUR_ISTORES_API_TOKEN" \
  istores-design-ops https://api.istores.co.il/mcp

Verify:

Code(bash)
 
gemini mcp list

You can also edit ~/.gemini/settings.json manually if needed.

Cursor

Open or create:

Code(text)
 
~/.cursor/mcp.json

For project-only setup, use:

Code(text)
 
.cursor/mcp.json

Add:

Code(json)
 
{
  "mcpServers": {
    "istores-design-ops": {
      "url": "https://api.istores.co.il/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ISTORES_API_TOKEN"
      }
    }
  }
}

Restart Cursor. In Agent mode, make sure MCP tools are enabled.

VS Code / GitHub Copilot Agent Mode

Open the Command Palette and run:

Code(text)
 
MCP: Open User Configuration

Or create a workspace file:

Code(text)
 
.vscode/mcp.json

Add:

Code(json)
 
{
  "servers": {
    "istores-design-ops": {
      "type": "http",
      "url": "https://api.istores.co.il/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ISTORES_API_TOKEN"
      }
    }
  }
}

Use Copilot Chat in Agent mode and enable the MCP server in the tools picker.

Windsurf / Cascade

Open Windsurf settings:

Code(text)
 
Windsurf Settings -> Cascade -> MCP Servers -> View raw config

This usually opens:

Code(text)
 
~/.codeium/windsurf/mcp_config.json

Add:

Code(json)
 
{
  "mcpServers": {
    "istores-design-ops": {
      "serverUrl": "https://api.istores.co.il/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ISTORES_API_TOKEN"
      }
    }
  }
}

Save, reload Windsurf, open Cascade, and check the MCP/tools icon.

Other AI Tools

If your AI tool supports remote HTTP MCP servers with custom headers, use:

Code(json)
 
{
  "mcpServers": {
    "istores-design-ops": {
      "type": "http",
      "url": "https://api.istores.co.il/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ISTORES_API_TOKEN"
      }
    }
  }
}

If the tool does not support custom headers, direct connection will not work. Use another MCP client or ask iStores support for an OAuth/bridge setup.

Step 2: Start the AI Chat

After the MCP server is connected, paste this into your AI chat:

Code(text)
 
Use the iStores Storefront Designer MCP.

My companyId is: YOUR_COMPANY_ID
My store URL is: YOUR_STORE_URL

I want to redesign my storefront.
Before publishing anything, create a rollback snapshot and ask me for approval.

First ask me what style, colors, sections, products, and images I want to change.

Replace:

YOUR_COMPANY_ID with your iStores company id.
YOUR_STORE_URL with your storefront URL.

Example:

Code(text)
 
Use the iStores Storefront Designer MCP.

My companyId is: 9906
My store URL is: https://example.com/

I want the homepage to look premium and modern.
Before publishing anything, create a rollback snapshot and ask me for approval.

Step 3: What the AI Should Do

The AI should work in this order:

Ask for the store style and design details.
Read the current CSS/JS with MCP tools.
Create a rollback snapshot.
Inspect the live storefront if possible.
Draft the CSS/JS changes.
Explain what will change.
Ask for approval before publishing.
Publish the change only after approval.
Verify the live storefront.
Give you the snapshotId for rollback.

If the AI tries to publish before creating a snapshot, stop it.

What to Give the AI

Prepare this information:

Question	Example answer
Company ID	`9906`
Store URL	`https://example-store.co.il/`
Business type	Fashion, supplements, cosmetics, food, electronics
Target audience	Young parents in Israel, Hebrew speakers
Style	Premium, clean, playful, luxury, calm, clinical
Colors	Black and gold, pink and white, green and cream
Logo/images	Upload files or provide URLs
Pages to change	Homepage, product page, category page
Products to update	Product ids or product URLs
Publish approval owner	The person who must approve live changes

What Success Looks Like

A good AI result should include:

What changed.
What was checked.
Whether desktop and mobile were checked.
The snapshotId.
How to roll back.

Example final AI message:

Code(text)
 
Status: Published

Changed:
- Homepage hero styling
- Product cards
- Add-to-cart buttons
- Mobile spacing

Checked:
- Homepage loaded
- CSS marker appeared in live HTML
- Product cards did not overlap on mobile

Snapshot ID:
2026-06-03T13-56-27-578929Z-fbb550d7

Rollback:
Ask me to roll back to this snapshot id.

For AI Agents: Follow This Exactly

If you are an AI agent reading this documentation, follow this protocol.

Confirm that the iStores MCP server is connected.
Ask the user for companyId before calling any tool.
Ask for the store URL and design brief.
Use MCP tools, not raw API calls.
Include companyId in every tool call.
Never print or store the Bearer token.
Before live changes, call create_snapshot.
Do not call update_theme, rollback_snapshot, or update_product without explicit user approval.
Keep CSS scoped to real storefront selectors.
Verify the storefront after publishing when possible.
Return the snapshotId and rollback instructions.

The companyId must match the company authenticated by the MCP Bearer token. If it does not match, the server will reject the tool call.

AI Agent Prompt

Use this prompt when your AI tool does not automatically understand the workflow:

Code(text)
 
You are an iStores storefront design operator.

Use the iStores Storefront Designer MCP tools only.
Do not use raw curl or direct API calls.

Before using tools, ask for:
- companyId
- store URL
- business type
- target audience
- desired style
- brand colors
- logo/images
- sections or pages to change
- publish approval owner

Every MCP tool call must include companyId.
The Bearer token is already configured in the MCP `Authorization` header.
Never print, store, or summarize the Bearer token.

Always create a snapshot before live CSS, JS, media, or product changes.

Workflow:
1. Read current CSS/JS.
2. Create snapshot.
3. Inspect storefront when possible.
4. Draft changes.
5. Explain preview.
6. Ask for approval.
7. Publish only after approval.
8. Verify live storefront.
9. Report snapshotId and rollback instructions.

Available MCP Tools

Tool	Use it for
`read_theme`	Read current custom CSS or JS
`create_snapshot`	Create a rollback snapshot before changes
`update_theme`	Publish replacement CSS or JS
`list_snapshots`	Find rollback snapshots
`rollback_snapshot`	Restore CSS and JS from a snapshot
`upload_media`	Upload storefront images/assets
`get_product`	Read a product by product id
`update_product`	Update product content

All tool calls require companyId.

Example Tool Calls

Read current CSS:

Code(json)
 
{
  "name": "read_theme",
  "arguments": {
    "companyId": "9906",
    "kind": "css"
  }
}

Create a snapshot:

Code(json)
 
{
  "name": "create_snapshot",
  "arguments": {
    "companyId": "9906",
    "label": "Before homepage redesign",
    "notes": "Snapshot before AI storefront CSS changes."
  }
}

Publish CSS:

Code(json)
 
{
  "name": "update_theme",
  "arguments": {
    "companyId": "9906",
    "kind": "css",
    "code": "/* full replacement CSS here */",
    "createBackup": true,
    "notes": "Homepage redesign CSS."
  }
}

Rollback:

Code(json)
 
{
  "name": "rollback_snapshot",
  "arguments": {
    "companyId": "9906",
    "snapshotId": "SNAPSHOT_ID_FROM_THE_AI"
  }
}

Rollback

If a published change looks wrong, tell the AI:

Code(text)
 
Use the iStores Storefront Designer MCP.
My companyId is YOUR_COMPANY_ID.
List snapshots and roll back to the version before the last storefront change.
Ask me for confirmation before restoring.

The AI should:

Call list_snapshots.
Show the available snapshots.
Ask which one to restore.
Ask for final confirmation.
Call rollback_snapshot.
Verify the storefront.

Common Problems

Problem	What it means
`401 Unauthorized`	The Bearer token is missing, invalid, or configured in the wrong place
`companyId does not match...`	The company id in chat does not belong to the configured token
`429 Too Many Requests`	Too many MCP/API calls were made too quickly; wait and retry
AI asks for a token	Configure it as `Authorization: Bearer YOUR_ISTORES_API_TOKEN`
AI wants to publish without snapshot	Stop and tell it to create a snapshot first

Security Rules

Keep the API token private.
Put the API token only in the private MCP connection header.
Do not paste the API token into prompts unless your support team explicitly tells you to.
Do not publish without a snapshot.
Do not roll back without confirmation.
Keep the snapshotId after every publish.

Tested Behavior

The hosted MCP server was verified with the Gateway Bearer-token flow:

Check	Result
`initialize` with a Bearer token	Works
`tools/list` with a Bearer token	Works
request without a Bearer token	Returns `401 Unauthorized`
`read_theme` with matching `companyId`	Works
`create_snapshot`	Creates a server-side rollback point
`update_theme`	Publishes CSS
live storefront check	CSS appears in the live HTML

Last modified on 27 July 2026

Istores SSO Integration