slima-mcp 0.2.0 → 0.3.1

package/README.md

@@ -137,19 +137,41 @@ Get your token from [Slima Settings](https://app.slima.ai/settings/api-tokens) o
 gemini mcp add slima --command "npx -y slima-mcp@0"
 ```
 
-> **Why `slima-mcp@0` instead of `slima-mcp` / `slima-mcp@latest`?** Using `@0` pins to the current major version — npx still fetches new `0.x.y` releases automatically (so you get features + bug fixes), but when we ship `1.0.0` with breaking changes you won't silently pick it up without updating your config. We'll announce the `@1` switch in the release notes.
+> **Why `slima-mcp@0` instead of `slima-mcp` / `slima-mcp@latest`?** Using `@0` pins to the current major version — npx fetches new `0.x.y` releases automatically (so you get features + bug fixes), but when we ship `1.0.0` with breaking changes you won't silently pick it up without updating your config. We'll announce the `@1` switch in the release notes.
+>
+> ⚠️ **This only holds if you do not also have a global `slima-mcp` install.** `npx pkg@<range>`
+> will happily satisfy the range from a package already on your `PATH` and never contact the
+> registry at all. Measured on 2026-09-09 with a global `0.2.0` present and `0.3.0` on npm:
+>
+> | command | resolved |
+> |---|---|
+> | `npx -y slima-mcp@0` | **0.2.0** — used the global install |
+> | `npx -y slima-mcp` | **0.2.0** — same |
+> | `npx -y slima-mcp@latest` | 0.3.0 — a dist-tag forces a registry lookup |
+> | `npx -y slima-mcp@0.3.0` | 0.3.0 — the global can't satisfy an exact newer version |
+>
+> So a stale global install makes the npx form silently stop upgrading, while the server keeps
+> telling you to upgrade. Remove it — see below.
 
 #### Migrating from a global install
 
 If you already installed globally with `npm install -g slima-mcp`:
 
 ```bash
-# Remove the old global install (optional but cleaner)
+# Remove the old global install — REQUIRED, not just tidiness.
+# Leaving it in place makes `npx -y slima-mcp@0` resolve to the old global copy
+# forever (see the warning above), so you'd stay outdated while being told to upgrade.
 npm uninstall -g slima-mcp
 
-# Change your config `command` from "slima-mcp" to the npx form above, and restart the client.
+# Then change your config `command` from "slima-mcp" to the npx form above, and restart the client.
+# Verify: `npx -y slima-mcp@0 --version` must print the version shown by `npm view slima-mcp version`.
 ```
 
+⚠️ Check **every** place you may have installed it. A global install can exist per Node version
+manager environment and per OS — on WSL setups it is common to have one under `nvm` *and* one
+under Windows' `AppData/Roaming/npm`, at two different versions, with only one of them on the
+`PATH` your MCP client actually uses.
+
 Or, if you want to stay on a global install, remember to periodically run:
 
 ```bash
@@ -303,8 +325,8 @@ npm run dev:worker
 # Deploy to Cloudflare
 npm run deploy:worker
 
-# Deploy to preview environment
-npm run deploy:worker:preview
+# Deploy to the test environment (test-mcp.slima.ai)
+npm run deploy:worker:test
 ```
 
 ### Project Structure
@@ -352,13 +374,33 @@ git checkout main && git merge dev && git push
 
 ### Cloudflare Worker (Manual)
 
-Worker deployment is separate from npm. Deploy after code changes:
+**Worker deployment is separate from npm, and nothing triggers it automatically.**
+Publishing to npm does NOT update `mcp.slima.ai`. Remote clients (claude.ai /
+ChatGPT connectors) talk to the Worker, so they keep running the old tool set
+until someone runs this by hand:
 
 ```bash
-npm run deploy:worker           # Production (mcp.slima.ai)
-npm run deploy:worker:preview   # Staging
+npm run deploy:worker:test   # Test  (test-mcp.slima.ai -> test-api.slima.ai)
+npm run deploy:worker        # Prod  (mcp.slima.ai      -> api.slima.ai)
 ```
 
+Deploy test first and check `curl https://test-mcp.slima.ai/ | jq .version`
+before doing prod; the same one-liner against `mcp.slima.ai` is how you tell
+whether the Worker is behind npm at all.
+
+> 2026-09-09: the Worker sat on 0.2.0 for four and a half months — it was last
+> deployed the same day npm 0.2.0 shipped, so every change after that reached
+> npm users and no connector users. There is no alarm for this; the version
+> endpoint is the only signal.
+
+> There used to be a `deploy:worker:preview` script pointing at an `[env.preview]`
+> block. It was removed on 2026-09-09: its KV id was the literal placeholder
+> string, `staging-api.slima.ai` does not resolve, and — worst — it defined no
+> `routes`. `routes` is an *inheritable* key in wrangler, so that command would
+> have inherited the top-level `mcp.slima.ai` custom domain and pointed
+> **production's hostname** at the preview Worker. The real staging environment
+> is `[env.test]`.
+
 ### MCP Registry (Manual)
 
 To publish/update the server listing on the [MCP Registry](https://registry.modelcontextprotocol.io/):