Connect Storelift to Claude as a custom connector

How this guide was checked

Claude's documentation: support.claude.com.

Version

This guide describes the server that is live: storelift-mcp 1.1.1 on npm (2026-09-14) and the hosted endpoint https://storelift.net/mcp, both with the same 8 tools: get_ai_visibility, get_charts, get_history, get_keywords, get_reviews, get_rivals, get_store_page, list_apps.

Every tool in this release reads; none of them changes anything in your account. The local server answers over stdio with protocol version 2024-11-05, the hosted endpoint over Streamable HTTP with 2025-06-18; the endpoint is stateless, with no session id and no server-sent stream.

Requirements

• Plan. MCP access needs the Pro, Studio or Enterprise plan, both with an API key and with sign-in (OAuth).
• Key. Storelift → Settings → API keys. The key starts with sl_live_. Keys in this release carry no scopes: a key reads every app in its workspace. Keep it only in the client's configuration.
• Claude. Custom connectors work on Claude's Free, Pro, Max, Team and Enterprise plans; Free is limited to one custom connector, and on Team only Owners add them. A connector added in Claude is also available in Claude Desktop.

Setup

1. In Claude, open Customize → Connectors, click + Add, then Add custom connector. On Team and Enterprise an owner goes to Organization settings → Connectors → Add → Custom → Web.
2. Name it Storelift, enter https://storelift.net/mcp as the URL and save.
3. Click Connect. Claude sends you to a Storelift page that names the app asking and the address you return to; sign in if needed and allow it.
4. In a new chat, check in the tools menu that Storelift is on: list_apps and the other tools are listed.

Claude can also add a connector with a fixed header (an API key); with Storelift, sign-in is the shorter path and there is no key to copy.

First read

Ask: “List my Storelift apps, then show the keyword ranks for the first one in the US.” The assistant calls list_apps first, then get_keywords for the app you pick. The list_apps reply looks like this (Storelift sample data, 2026-09-28; your account returns your own apps):

{
  "apps": [
    {
      "id": "sbx-lumen",
      "name": "Lumen — Sleep Sounds",
      "countries": [
        "us",
        "gb",
        "de"
      ],
      "keywords": [
        "sleep sounds",
        "white noise",
        "rain sounds"
      ]
    }
  ]
}

get_keywords returns one row per tracked keyword:

{
  "country": "us",
  "platform": "ios",
  "keywords": [
    {
      "term": "sleep sounds",
      "measured": true,
      "rank": null,
      "demand": 73,
      "searchDepth": 200
    },
    {
      "term": "white noise",
      "measured": true,
      "rank": 57,
      "demand": 37,
      "searchDepth": 200
    }
  ]
}

A number in rank is the rank; null means the keyword was measured and the app is not in the results; measured: false means it could not be measured. The three stay apart: counting an unmeasured day as zero gives a wrong answer.

The connection works. Next, three first tasks: which keywords fell, who is ahead on them, and what to say when a keyword has no measurement today, each with the answer to expect.

Removing access

1. In Claude, open Customize → Connectors and choose Remove next to Storelift (on Team and Enterprise an owner does this under Organization settings).
2. Delete the key under Storelift → Settings → API keys. The next request with that key is refused (a tool error from the local server, HTTP 401 from the hosted endpoint); there is no open session to wait out.
3. If you connected with sign-in (OAuth), remove the connection under Settings → API → Connected apps; that connection's token gets a 401 on its next request.

Troubleshooting

Read next