Skip to Retail Workspace documentation
Nesika AI

Retail Workspace

Connect Retail Workspace to AI assistants

Use the private Retail Workspace MCP endpoint to ask AI assistants about your tracked products, scans, competitors, and pricing insights.

Retail data only

This connection uses a workspace-scoped credential and private Retail Workspace tools. Market-wide product discovery uses a Developer Project credential and the separate Commerce MCP documentation.

Workspace endpoint

https://mcp.nesika.ai/workspace

API key connector URLs for ChatGPT and Claude use https://mcp.nesika.ai/mcp, which serves the same tools. Existing connectors that use it keep working. No change is needed.

Workspace credential

ChatGPT and Claude can connect by signing in with your Nesika account (recommended) or with a workspace API key (it starts with nes_) in the connector URL. Other clients send the key in the X-API-Key header.

Connect an MCP client

1

Create a workspace API key

Sign in through the Retail path and create a key from workspace settings. Copy it immediately: the key is shown only once. The key creation dialog also shows a ready-to-copy connector URL for ChatGPT and Claude. You can skip this step for ChatGPT and Claude if you connect them by signing in with your Nesika account.
2

Add Nesika to your client

ChatGPT and Claude: sign in with your Nesika account using https://mcp.nesika.ai/workspace (recommended), or use the API key connector URL https://mcp.nesika.ai/mcp?api_key=nes_your_workspace_api_key with your key in place of the placeholder. Claude Code, Cursor, VS Code, and other clients use https://mcp.nesika.ai/workspace with an X-API-Key header.
3

Start with a workspace question

Ask the assistant to list your tracked products or summarise recent price changes.

Authentication

The Retail Workspace endpoint accepts your workspace API key in any of these three ways. Use one method per connection. ChatGPT and Claude can also connect without a key by signing in with your Nesika account.

X-API-Key header

Recommended wherever your client supports custom headers. Send X-API-Key: nes_...

Authorization: Bearer

For clients that only support bearer tokens. Send Authorization: Bearer nes_...

api_key query parameter

Add ?api_key=nes_... to the /mcp endpoint (the API key connector URL). Use it to connect ChatGPT and Claude custom connectors with an API key, because they cannot send custom headers. It is supported and has the same permissions as the key in a header.

A connector URL with a key is a secret

Treat any URL that contains your API key like a password. Do not share it, paste it into chats, screenshots, or tickets, or commit it to source control. If it is exposed, revoke the key, create a new one, and update your connector URL.

Connect with an API key connector URL

Signing in with your Nesika account is recommended for ChatGPT and Claude, but they can also connect with a connector URL that carries your workspace API key. The URL has the same permissions as the same key sent in an X-API-Key header.

URL format

https://mcp.nesika.ai/mcp?api_key=<your API key>

The API key connector URL uses the /mcp path, which serves the same tools as /workspace, so the assistant connects with your key and does not ask you to sign in. Sign-in and header-based clients use /workspace without a key.

The easiest way to get it: when you create or replace a key in workspace settings, choose ChatGPT or Claude in the key dialog and select Copy next to the connector URL. It already includes your key and, like the key, is shown only once.

This URL contains your secret key

Treat it like a password. Store it only in your assistant's connector settings, never paste it into a chat, and do not share it or commit it to source control. If it is exposed, revoke the key, create a new one, and update the connector.

Connect ChatGPT

ChatGPT connects to remote MCP servers through apps. Sign in with your Nesika account (recommended), or use an API key connector URL: these apps cannot send custom headers, so the key goes in the connector URL.

Sign in with your Nesika account (recommended)

  1. In ChatGPT, open Settings → Apps and create a new app (enable Developer Mode first if required).
  2. Paste the connector URL below.
  3. Sign in with your Nesika account when asked, then choose what to allow.
https://mcp.nesika.ai/workspace

Signing in needs no API key. You can disconnect at any time from Connected assistants.

Connect with an API key connector URL

1

Turn on Developer mode

In ChatGPT, open Settings → Security and login and turn on Developer mode.
2

Create a developer-mode app

Go to Plugins, select +, and create a developer-mode app. Give it a recognisable name, such as Nesika Retail Workspace.
3

Paste your connector URL

Use this URL, replacing the placeholder with your workspace key:
https://mcp.nesika.ai/mcp?api_key=nes_your_workspace_api_key

Set Authentication to No authentication. The key in the URL authenticates the connection.

4

Use it in a chat

Create the app, then select it from Developer mode in the composer before you ask about your workspace.

Plan eligibility

Availability and permissions depend on your ChatGPT plan and workspace configuration. Workspace admins may need to allow developer-mode apps first.

Connect Claude.ai and Claude Desktop

Claude custom connectors work the same way in Claude.ai and Claude Desktop. Sign in with your Nesika account where available (recommended), or use an API key connector URL: custom connectors cannot send custom headers, so the key goes in the connector URL.

Sign in with your Nesika account (recommended)

  1. In Claude, open Customize → Connectors and select Add custom connector.
  2. Paste the connector URL below.
  3. Select Connect, sign in with your Nesika account, then choose what to allow.
https://mcp.nesika.ai/workspace

Signing in needs no API key. You can disconnect at any time from Connected assistants.

Connect with an API key connector URL

1

Open connector settings

Open Customize → Connectors.
2

Add a custom connector

Select Add custom connector and give it a name, such as Nesika Retail Workspace.
3

Paste your connector URL

Use this URL, replacing the placeholder with your workspace key:
https://mcp.nesika.ai/mcp?api_key=nes_your_workspace_api_key

Leave the OAuth Client ID and OAuth Client Secret fields empty.

4

Add and enable the connector

Add the connector, then enable it in the conversation from the tools menu.

Team and Enterprise workspaces

An organization Owner may need to add the connector first before members can connect it. Organizations with access to Claude's request-header support may instead use https://mcp.nesika.ai/workspace with the key in an X-API-Key header.

Connect Claude Code

1

Run the add command

Replace the placeholder with your workspace key:
claude mcp add --transport http nesika-retail https://mcp.nesika.ai/workspace --header "X-API-Key: nes_your_workspace_api_key"
2

Choose a scope

Add --scope user to use it in every project, or --scope project to share it with the current project. Keep real keys out of files you commit.
3

Verify the connection

Start a new Claude Code session and ask it to list your tracked products.

Connect Cursor

1

Add the MCP config

Save this to .cursor/mcp.json in your project or ~/.cursor/mcp.json for a global setup.
{
  "mcpServers": {
    "nesika-retail": {
      "url": "https://mcp.nesika.ai/workspace",
      "headers": {
        "X-API-Key": "nes_your_workspace_api_key"
      }
    }
  }
}
2

Reload Cursor

Restart Cursor or reload MCP servers so the Nesika tools are discovered.
3

Use the tools

Open Cursor chat in Agent mode and ask about your tracked products.

Connect VS Code (GitHub Copilot)

1

Add the MCP config

Save this to .vscode/mcp.json or your user-level MCP configuration. VS Code prompts for the key and stores it securely, so the key is not saved in the file.
{
  "inputs": [
    {
      "type": "promptString",
      "id": "nesika-retail-api-key",
      "description": "Nesika Retail Workspace API key (starts with nes_)",
      "password": true
    }
  ],
  "servers": {
    "nesika-retail": {
      "type": "http",
      "url": "https://mcp.nesika.ai/workspace",
      "headers": {
        "X-API-Key": "${input:nesika-retail-api-key}"
      }
    }
  }
}
2

Start the server

Start the nesika-retail server and enter your workspace key when prompted.
3

Open Copilot Chat in Agent mode

Ask Copilot Chat about your tracked products using the Nesika tools.

Other MCP clients

Add a remote HTTP MCP server with the workspace endpoint and send your key in the X-API-Key header (or Authorization: Bearer). Most clients accept a configuration like this:

{
  "mcpServers": {
    "nesika-retail": {
      "type": "http",
      "url": "https://mcp.nesika.ai/workspace",
      "headers": {
        "X-API-Key": "nes_your_workspace_api_key"
      }
    }
  }
}

If your client cannot send custom headers, use the connector URL https://mcp.nesika.ai/mcp?api_key=nes_your_workspace_api_key instead.

Do not commit the key

Replace the placeholder through your MCP client's secret storage. Do not save a real workspace key in a repository.

Private Retail Workspace tools

These are the only six private tools available. Each returns data from the Retail Workspace linked to your credential.

my_products

Read products tracked in the current Retail Workspace.

my_price_position

Compare current prices with tracked competitor offers.

my_price_history

Read historical prices for tracked products.

my_scan_status

Check the status and freshness of workspace scans.

my_insights

Read private pricing insights for the workspace.

export_scan_report

Export an authorized report for a workspace scan.

Example prompts

  • “List my tracked products with their latest prices.”
  • “Summarise my biggest price changes from recent scans.”
  • “Which products are currently priced above competitors?”
  • “Show my latest high-priority pricing insights.”

Troubleshooting

Authentication fails (401 Unauthorized)

The key may be revoked, expired, or from a different workspace. Generate a new key in workspace settings, then update the connector URL in ChatGPT or Claude, or the X-API-Key header in other clients. If you connected ChatGPT or Claude by signing in, reconnect it from the assistant.

Tools do not appear

Confirm the URL path ends with /workspace for sign-in and header-based clients, or /mcp for an API key connector URL. If ChatGPT or Claude connects with an API key, the connector URL must also include ?api_key= followed by your key. Save the configuration, then refresh or reconnect the client.

Results are empty

Check that the connected workspace contains tracked products and completed scan data.

Logos provided by Logo.dev