Connect Codex and other AI clients

MCP lets Codex, OpenCode, Pi, and compatible clients work with the Stores on Live tools you choose: catalog work, show preparation, live controls, listings, offers, and sales results.

1. Before you begin

  • A Stores on Live account with a connected Shopify store.
  • An agent that supports remote MCP over Streamable HTTP and OAuth with PKCE.
  • The server URL: https://kehk-systemic-production.up.railway.app/mcp

Codex uses its published client identity. OpenCode uses the preconfigured client ID in the settings below. Neither needs registration with our team. Pi and other agents require a registered client ID and exact return address before sign-in.

2. What you can do

  • Turn your catalog into a show: Ask your assistant to find Shopify products and variants, arrange the lineup and save a show draft. Your product selection becomes saved work in Stores on Live, ready for you to review and continue in the app.
  • Match the sale to the product: Let buyers compete in a rising-bid auction, wait for a falling price, buy at a fixed price or make an offer. Mix formats in one show and set each item’s starting price, reserve or price floor.
  • Give your show a place to sell: Check your draft for missing setup before you launch. Publish it as an event page on your Shopify storefront, or schedule its release. Shoppers get a place to watch, bid and buy from your store.
  • Keep the live sale moving: Ask your assistant to open the next product, close an auction or skip an item. Review incoming offers and accept, reject or counter them from the conversation. You present the products and start the camera on your device.
  • Keep selling between broadcasts: A product does not need a live show to sell. Create a standalone auction or an offer-based listing on your storefront. Set its pricing and schedule, then use your assistant to manage the offers that come in.
  • Know what needs your attention: Ask what sold, which purchases are paid and which still need payment. Review product outcomes and show attendance together, so you can see the result of the sale and decide what to follow up on.

3. Connect Codex

codex mcp add stores-on-live --url https://kehk-systemic-production.up.railway.app/mcp
codex mcp login stores-on-live

Sign in, choose your store, and approve access. No client ID or secret is needed.

4. Connect OpenCode

Check opencode --version, then merge the matching configuration.

OpenCode V2

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "servers": {
      "stores-on-live": {
        "type": "remote",
        "url": "https://kehk-systemic-production.up.railway.app/mcp",
        "protocol": "auto",
        "oauth": {
          "client_id": "stores-on-live-opencode",
          "callback_port": 8765,
          "redirect_uri": "http://127.0.0.1:8765/callback"
        }
      }
    }
  }
}

OpenCode 1.x

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "stores-on-live": {
      "type": "remote",
      "url": "https://kehk-systemic-production.up.railway.app/mcp",
      "oauth": {
        "clientId": "stores-on-live-opencode",
        "callbackPort": 8765,
        "redirectUri": "http://127.0.0.1:8765/callback"
      }
    }
  }
}
opencode mcp auth stores-on-live

Sign in, choose your store, approve access, then run opencode mcp list.

5. Connect Pi

Merge this into ~/.pi/agent/mcp.json, keeping existing servers. Replace the placeholder with the client ID registered for your agent.

{
  "mcpServers": {
    "stores-on-live": {
      "url": "https://kehk-systemic-production.up.railway.app/mcp",
      "oauth": {
        "clientId": "YOUR_REGISTERED_CLIENT_ID",
        "callbackPort": 8765
      }
    }
  }
}
pi mcp login stores-on-live

Sign in, choose your store, and approve access. Check the connection with /mcp.

6. Make your first request

Ask the agent to show five products from your connected store. This is a read-only request and is a simple way to confirm that you selected the right store.

To approve additional permissions, reconnect from your assistant and review the new access request. Refreshing a page or connection metadata does not grant more access. For ‘client not registered’ or a rejected callback, check that you used the settings for your client and version. For expired or revoked access, sign in again from the assistant. If the connection still shows old tools or sign-in settings, refresh its server metadata where supported and start a new chat. For help, contact support with the client name, version and error text; do not send passwords, tokens or authorization codes. Contact support.