Skip to main content

Setup Guide: KSI Vision MCP Server in Claude

This guide details the steps required to connect the KSI Vision Model Context Protocol (MCP) server to Claude — the web app (claude.ai), the desktop and mobile apps, and the Claude Code CLI.

Once connected, Claude can query your stores' indicators directly — traffic, queues, dwell time, sales conversion, zones, and more — and turn them into reports, comparisons, and analyses in natural language.

1. Prerequisites​

Before starting, make sure you have:

  • A KSI Vision account with access to create API Tokens (if you do not have access, request it at ksi.support@ksivision.com).
  • Your KSI API token (see API – Getting Started Guide).
  • A Claude account on a plan that supports custom connectors (Pro, Max, Team, or Enterprise).

👉 MCP Server URL:

  • https://mcp.ksivision.com/api/mcp

2. Claude.ai (Web, Desktop, and Mobile Apps)​

Connectors are configured once in your Claude account and become available across the web app, the desktop app, and the mobile apps.

Step 2.1: Add the Connector​

  1. Open claude.ai and go to Settings → Connectors.
  2. Scroll down and select Add custom connector.
  3. Fill in the fields:
    • Name: KSI Vision
    • Remote MCP server URL: https://mcp.ksivision.com/api/mcp
  4. Select Add.

Step 2.2: Authenticate​

  1. Next to the new KSI Vision connector, select Connect.
  2. A browser tab opens with the KSI login screen.
  3. Paste your KSI API token and select Authorize.
  4. You are redirected back to Claude — the connector now shows as connected.

You will not need to paste the token again until it expires (access tokens last 30 days and refresh automatically while you keep using the connector).

Step 2.3: Use It in a Chat​

  1. Start a new conversation.
  2. Open the search and tools menu (sliders icon) in the message box and confirm KSI Vision is enabled.
  3. Ask your first question:

"Diagnose my KSI account."

note

UI labels may vary slightly as Anthropic updates the product. If you don't see Connectors, look for it under Settings → Extensions or check that your plan supports custom connectors.

3. Claude Code (CLI)​

Claude Code supports both interactive OAuth and a static Bearer token.

Option A – OAuth (recommended)​

  1. Add the server:

    claude mcp add --transport http ksi https://mcp.ksivision.com/api/mcp

  2. Start claude, then run:

    /mcp

  3. Select the ksi server and press Enter to authenticate. Your browser opens the KSI login screen — paste your API token and select Authorize.

Option B – Static Bearer token​

claude mcp add --transport http ksi https://mcp.ksivision.com/api/mcp \
  --header "Authorization: Bearer <YOUR_KSI_TOKEN>"

Use this option for scripted or headless environments where an interactive login is not possible.

4. Verification​

Once connected, always start with the account diagnostic tool. Ask Claude:

"Diagnose my KSI account."

This returns your space type (retail, mall, airport…), the account's global feature flags, and which capabilities each store has (sales, queues, zones, sub-locations) — so Claude knows what it can safely ask for before running an analysis.

Example prompts​

  • "Compare traffic and conversion across my stores in June, grouped by tag."
  • "In which day-and-hour windows am I losing sales to long queues at store 661?"
  • "Would opening more checkouts improve conversion at peak hours?"

Security Notes​

  • The MCP server is read-only: it queries indicators and never modifies configuration, cameras, or data.
  • Your token travels with each request and is never stored on the MCP server.
  • Claude only sees the stores and data your token has access to — each user should connect with their own token.

Support​

If you need help connecting Claude, generating a token, or troubleshooting:

📧 ksi.support@ksivision.com