# Add the Storelift MCP server to Claude Code

URL: https://storelift.net/guide/storelift-mcp-claude-code/
Language: en
Updated: 2026-10-11

The steps to connect the Storelift MCP server to Claude Code; version, requirements and error replies were measured on the server itself.

## How this guide was checked

NOTE: How this was checked (2026-10-11). The server side was measured with storelift-mcp 1.1.1: handshake, tool list, read calls, error replies and access removal. Seen in Claude Code: 2.1.296 · stdio, API key: connects, lists the 8 tools, comes out cleanly with the remove command; 2.1.296 · Streamable HTTP, API key in a header: connects, lists the 8 tools. A tool call from inside Claude Code has not been tried; the steps below follow Claude Code's own documentation.

Claude Code's documentation: code.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.
- Runtime. Node.js 18 or later for the local server (npx fetches the package on first run). The hosted endpoint needs nothing installed.
- Claude Code. Any recent version; the commands below are from claude mcp add --help and Claude Code's MCP documentation.

## Setup

Local server with an API key (run it in your project directory; the default scope is this project only):

claude mcp add storelift -e STORELIFT_API_KEY=sl_live_... -- npx -y storelift-mcp

Or the hosted endpoint, nothing to install, key in a header:

claude mcp add --transport http storelift https://storelift.net/mcp --header "Authorization: Bearer sl_live_..."

To sign in (OAuth) instead of using a key, add the endpoint without a header, then run /mcp inside Claude Code:

claude mcp add --transport http storelift https://storelift.net/mcp

Check the connection with claude mcp list; the line should read ✔ Connected.

## 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. Run claude mcp remove storelift. For a sign-in connection Claude Code also deletes the tokens it stored; /mcp → Clear authentication does the same without removing the server.
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

| What you see | Why | What to do |
| --- | --- | --- |
| “No API key was sent…” | The local server started without a key. Tools still list, every call returns this. | Add STORELIFT_API_KEY to the server's configuration and restart the client. |
| “This API key is not valid…” | The key is mistyped or was deleted. The hosted endpoint answers HTTP 401. | Create a new key under Settings → API keys and replace the one in the configuration. |
| “The Public API is available on the Pro and Studio plans…” | The account's plan does not open MCP access (HTTP 403). In this release access is on Pro, Studio or Enterprise. | Upgrade at storelift.net/pricing; the key is kept and works again once the plan allows it. |
| “fetch failed…” | The local server could not reach Storelift: network, proxy or firewall. | Check that this machine can reach https://storelift.net; set STORELIFT_API only if you were given a different endpoint. |
| ✘ Failed to connect in claude mcp list | The server did not start (Node.js missing or too old) or the endpoint did not answer in time. | Run node --version; for slow starts raise the start-up timeout, e.g. MCP_TIMEOUT=10000 claude. |