storm-site-mcp


 \ 

 \ 

 \  \  \ 


storm-client.net developer MCP

A Model Context Protocol server for developers to interact with Storm-client.net. Lets you manage your plans, prices, plugins, and plugin links through an AI assistant like Claude.

Prerequisites

• Python 3.12+
• A Storm-client.net developer account
• Claude Code or another MCP-compatible client

Getting your token

1. Log in to storm-client.net
2. Open browser DevTools → Application → Cookies → storm-client.net
3. Copy the value of the token cookie — this is your bearer token

Note: the token cookie is read-only — it authenticates GETs, but mutating calls (e.g. editing a plan) return 403 with it. You don't need to do anything extra: for write operations the server automatically exchanges the cookie for a short-lived JWT (via POST /identity/token) and caches it, refreshing before it expires. Just keep STORM_TOKEN set to your cookie value.

Setup

# 1. Clone the repo
git clone https://github.com/AchachiSoftware/storm-site-mcp
cd storm-site-mcp

# 2. Create a virtual environment and install dependencies
python3 -m venv .venv
.venv/bin/pip install -r requirements.txt

# 3. Create your local config
cp .env.example .env
# Edit .env and paste your token as STORM_TOKEN=<your token>

Configuring Claude Code

Create a .mcp.json file in the project root (it's gitignored, so it stays local):

{
  "mcpServers": {
    "storm-client": {
      "command": "/absolute/path/to/.venv/bin/python",
      "args": ["/absolute/path/to/server.py"],
      "env": {
        "STORM_TOKEN": "your_token_here",
        "CONFIG_DIR": "/absolute/path/to/config",
        "HAR_DIR": "/absolute/path/to/har"
      }
    }
  }
}

Then start Claude Code from the project directory. Run /mcp to confirm the storm-client server is connected.

Docker (alternative)

docker build -t storm-client-mcp .
docker run -e STORM_TOKEN=your_token_here \
  -v $(pwd)/config:/app/config \
  -v $(pwd)/har:/app/har \
  storm-client-mcp

Available tools

| Tool | Description | |---|---| | list_plans | List all your plans (paginated automatically) | | list_my_plans | Enumerate every plan you own, including hidden ones | | list_prices | List prices for a given plan ID | | update_price | Set a promo discount percent (0–100) on a price | | update_plan_field | Edit a single plan field (description, imageUrl, name, tags) | | list_plan_blacklist | List the users blacklisted from a plan | | blacklist_user | Blacklist a user by Discord ID from one plan, or all your plans | | unblacklist_user | Remove a user's blacklist entry from one plan, or all your plans | | call_endpoint | Call any API path directly — useful for exploration. Accepts a relative path (e.g. /shop/plans/my) or a full URL (e.g. https://api.storm-client.net/plugin-repos) | | register_endpoint | Save a discovered endpoint to the local registry | | list_registered_endpoints | Show all saved endpoints | | import_har | Import endpoints from a browser HAR export |

Discovering endpoints via HAR

The Storm site makes API calls to two bases:

• https://storm-client.net/api/shop/ — plans, prices, subscriptions, plugin links
• https://api.storm-client.net/ — plugin repos, plugins, changelogs, orders, payouts

To capture API calls the site makes:

1. Open DevTools → Network tab
2. Navigate around the developer portal
3. Right-click any request → Save all as HAR with content
4. Drop the .har file into the har/ directory
5. Ask Claude to run import_har with the filename

Endpoints registry

Discovered endpoints are stored in config/endpoints.json. The repo ships with a set of known endpoints — you can add more via register_endpoint or import_har and commit them back for others to benefit.