memoryintelligence-mcp 0.2.7__tar.gz → 0.2.8__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Potentially problematic release.


This version of memoryintelligence-mcp might be problematic. Click here for more details.

Files changed (23) hide show
  1. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/CHANGELOG.md +37 -0
  2. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/PKG-INFO +14 -2
  3. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/README.md +13 -1
  4. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/pyproject.toml +1 -1
  5. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/__init__.py +1 -1
  6. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/cli.py +91 -0
  7. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/.gitignore +0 -0
  8. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/CONTRIBUTING.md +0 -0
  9. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/LICENSE +0 -0
  10. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/__main__.py +0 -0
  11. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/client.py +0 -0
  12. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/config.py +0 -0
  13. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/embedder.py +0 -0
  14. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/indexer.py +0 -0
  15. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/keys.py +0 -0
  16. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/local_index.py +0 -0
  17. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/localreads.py +0 -0
  18. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/paths.py +0 -0
  19. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/recall_guard.py +0 -0
  20. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/scrub.py +0 -0
  21. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/server.py +0 -0
  22. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/umo_format.py +0 -0
  23. {memoryintelligence_mcp-0.2.7 → memoryintelligence_mcp-0.2.8}/src/mi_mcp/vault.py +0 -0
@@ -3,6 +3,43 @@
3
3
  All notable changes to `memoryintelligence-mcp` are documented here.
4
4
  The format follows [Keep a Changelog](https://keepachangelog.com/); this project uses [Semantic Versioning](https://semver.org/).
5
5
 
6
+ ## [0.2.8] — 2026-08-04
7
+
8
+ ### Added — `mi-mcp doctor` tells you when you're behind
9
+ Doctor reported the binary, PATH, wrapper, key, allowlist, vault and wiring — and
10
+ not one word about **which version it was running**. So the most common way to be
11
+ broken was invisible: a user on 0.2.5 asking why the workspace tools "don't exist",
12
+ when they exist fine and the install is two releases old.
13
+
14
+ Doctor now checks PyPI and reports as its **first** line:
15
+
16
+ ```
17
+ [✗] version 0.2.5 installed, 0.2.8 available — `uv tool upgrade memoryintelligence-mcp && mi-mcp wire`
18
+ ```
19
+
20
+ Details that matter:
21
+
22
+ - **The upgrade command matches how you actually installed it** — `uv tool` /
23
+ `pipx` / `pip`, detected from the interpreter's location. Suggesting `pip` to a
24
+ uv-tool user is a dead end; on a Homebrew Python, `pip` may not exist at all
25
+ and is PEP-668 externally-managed regardless.
26
+ - **`mi-mcp wire` is in the suggestion on purpose.** Upgrading across 0.2.6 without
27
+ re-wiring leaves your config pointing at a server id that no longer announces
28
+ itself, and the tools silently disappear.
29
+ - **Out of date never fails doctor's exit code** — behind is not broken, and scripts
30
+ that gate on `mi-mcp doctor` must not start failing the day a release lands.
31
+ - **Unreachable PyPI reports "latest unknown", never "up to date".** Offline is not
32
+ evidence of being current.
33
+ - **Opt out** with `--no-version-check` or `MI_MCP_NO_VERSION_CHECK=1`. Then **no
34
+ request is made at all** — not a request whose answer is ignored. The check is an
35
+ anonymous PyPI index fetch, the same one any install performs.
36
+
37
+ It reads the **simple index** (PEP 691), not `/pypi/<project>/json`. The aggregate
38
+ endpoint is CDN-cached and was observed serving a stale version for minutes after
39
+ 0.2.7 published — a doctor reading it would confidently tell a user they were
40
+ current when they were two releases behind, which is precisely the bug this check
41
+ exists to prevent.
42
+
6
43
  ## [0.2.7] — 2026-08-03
7
44
 
8
45
  ### Added — `mi_ask` / `mi_list` take a `workspace_id` (#385 UC2)
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: memoryintelligence-mcp
3
- Version: 0.2.7
3
+ Version: 0.2.8
4
4
  Summary: MCP server for MemoryIntelligence — give Claude a memory you own, set up in one command
5
5
  Project-URL: Homepage, https://memoryintelligence.io
6
6
  Project-URL: Repository, https://github.com/somewhere11/memoryintelligence-mcp
@@ -222,11 +222,23 @@ Never paste the key into an MCP client config.
222
222
 
223
223
  **Repair / inspect without re-running setup:**
224
224
  ```bash
225
- mi-mcp doctor # checks binary, PATH, key, wiring, opt-in, vault path
225
+ mi-mcp doctor # checks version, binary, PATH, key, wiring, opt-in, vault path
226
226
  mi-mcp status # wired surfaces + opt-in allowlist
227
227
  mi-mcp wire --dry-run # preview wiring changes
228
228
  ```
229
229
 
230
+ **Staying current.** `doctor` compares your installed version against PyPI and
231
+ prints the upgrade command for how you actually installed it:
232
+
233
+ ```
234
+ [✗] version 0.2.5 installed, 0.2.8 available — `uv tool upgrade memoryintelligence-mcp && mi-mcp wire`
235
+ ```
236
+
237
+ Run `mi-mcp wire` after any upgrade — 0.2.6 renamed the server, and a config left
238
+ pointing at the old id loses its tools silently. The check is an anonymous PyPI
239
+ index fetch; skip it entirely with `--no-version-check` or
240
+ `MI_MCP_NO_VERSION_CHECK=1`, and it fails quietly when you're offline.
241
+
230
242
  **Which server am I talking to?** The local server announces `mi-local`; the
231
243
  remote MCP surface announces `memoryintelligence-remote`. The local default
232
244
  surface is 7 tools; the remote is 4 — if the tool list doesn't match what you
@@ -183,11 +183,23 @@ Never paste the key into an MCP client config.
183
183
 
184
184
  **Repair / inspect without re-running setup:**
185
185
  ```bash
186
- mi-mcp doctor # checks binary, PATH, key, wiring, opt-in, vault path
186
+ mi-mcp doctor # checks version, binary, PATH, key, wiring, opt-in, vault path
187
187
  mi-mcp status # wired surfaces + opt-in allowlist
188
188
  mi-mcp wire --dry-run # preview wiring changes
189
189
  ```
190
190
 
191
+ **Staying current.** `doctor` compares your installed version against PyPI and
192
+ prints the upgrade command for how you actually installed it:
193
+
194
+ ```
195
+ [✗] version 0.2.5 installed, 0.2.8 available — `uv tool upgrade memoryintelligence-mcp && mi-mcp wire`
196
+ ```
197
+
198
+ Run `mi-mcp wire` after any upgrade — 0.2.6 renamed the server, and a config left
199
+ pointing at the old id loses its tools silently. The check is an anonymous PyPI
200
+ index fetch; skip it entirely with `--no-version-check` or
201
+ `MI_MCP_NO_VERSION_CHECK=1`, and it fails quietly when you're offline.
202
+
191
203
  **Which server am I talking to?** The local server announces `mi-local`; the
192
204
  remote MCP surface announces `memoryintelligence-remote`. The local default
193
205
  surface is 7 tools; the remote is 4 — if the tool list doesn't match what you
@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
4
4
 
5
5
  [project]
6
6
  name = "memoryintelligence-mcp"
7
- version = "0.2.7"
7
+ version = "0.2.8"
8
8
  description = "MCP server for MemoryIntelligence — give Claude a memory you own, set up in one command"
9
9
  readme = "README.md"
10
10
  license = "Apache-2.0"
@@ -1,3 +1,3 @@
1
1
  """MI MCP Server — MemoryIntelligence tools for Claude."""
2
2
 
3
- __version__ = "0.2.7"
3
+ __version__ = "0.2.8"
@@ -452,9 +452,75 @@ def cmd_wire(argv: list[str]) -> int:
452
452
  return 0
453
453
 
454
454
 
455
+ #: PyPI project name — the package this CLI ships as.
456
+ PYPI_PROJECT = "memoryintelligence-mcp"
457
+
458
+ #: Set truthy to skip doctor's release check entirely (no network call at all).
459
+ NO_VERSION_CHECK_ENV = "MI_MCP_NO_VERSION_CHECK"
460
+
461
+
462
+ def _version_tuple(v: str) -> tuple:
463
+ """`"0.2.10"` → `(0, 2, 10)` for ordering. Non-numeric parts sort as -1.
464
+
465
+ Deliberately not `packaging.version` — it is not a declared dependency, and a
466
+ doctor check must never be the thing that fails to import.
467
+ """
468
+ parts: list = []
469
+ for chunk in (v or "").strip().split("."):
470
+ digits = "".join(c for c in chunk if c.isdigit())
471
+ parts.append(int(digits) if digits else -1)
472
+ return tuple(parts)
473
+
474
+
475
+ def _latest_pypi_version(project: str = PYPI_PROJECT, timeout: float = 2.0) -> str | None:
476
+ """Newest version on PyPI, or None if it cannot be determined. Never raises.
477
+
478
+ Uses the **simple index** (PEP 691), NOT ``/pypi/<project>/json``. Learned the
479
+ hard way on 2026-08-04: minutes after 0.2.7 published, the aggregate JSON
480
+ endpoint was still serving a cached ``0.2.5`` while the simple index was already
481
+ correct. A doctor that reads the stale endpoint would tell a user they are
482
+ up to date when they are not — the exact failure this check exists to prevent.
483
+ """
484
+ import urllib.request
485
+
486
+ url = f"https://pypi.org/simple/{project}/"
487
+ req = urllib.request.Request(
488
+ url,
489
+ headers={
490
+ "Accept": "application/vnd.pypi.simple.v1+json",
491
+ "User-Agent": f"mi-mcp/{__version__}",
492
+ },
493
+ )
494
+ try:
495
+ with urllib.request.urlopen(req, timeout=timeout) as resp: # noqa: S310 (fixed https URL)
496
+ versions = json.loads(resp.read().decode("utf-8")).get("versions") or []
497
+ except Exception:
498
+ return None # offline, DNS, timeout, 5xx, schema change — all "unknown"
499
+ real = [v for v in versions if _version_tuple(v) != (-1,)]
500
+ return max(real, key=_version_tuple) if real else None
501
+
502
+
503
+ def _upgrade_command() -> str:
504
+ """The upgrade command for THIS install, not a generic guess.
505
+
506
+ `pip` is wrong for most installs of this package and is not even present on
507
+ some machines (Homebrew python is PEP-668 externally-managed), so guessing
508
+ costs the user a failed command and a detour. Detect from the interpreter's
509
+ location instead.
510
+ """
511
+ prefix = str(Path(sys.prefix).resolve())
512
+ if f"{os.sep}uv{os.sep}tools{os.sep}" in prefix + os.sep:
513
+ return f"uv tool upgrade {PYPI_PROJECT}"
514
+ if f"{os.sep}pipx{os.sep}venvs{os.sep}" in prefix + os.sep or os.environ.get("PIPX_HOME"):
515
+ return f"pipx upgrade {PYPI_PROJECT}"
516
+ return f"{Path(sys.executable).name} -m pip install --upgrade {PYPI_PROJECT}"
517
+
518
+
455
519
  def cmd_doctor(argv: list[str]) -> int:
456
520
  ap = argparse.ArgumentParser(prog="mi-mcp doctor")
457
521
  ap.add_argument("--home", default=os.environ.get("HOME"))
522
+ ap.add_argument("--no-version-check", action="store_true",
523
+ help="skip the PyPI release check (no network call)")
458
524
  args = ap.parse_args(argv)
459
525
  home = Path(args.home)
460
526
 
@@ -466,6 +532,31 @@ def cmd_doctor(argv: list[str]) -> int:
466
532
  ok = False
467
533
  print(f" [{'✓' if good else '✗'}] {label}" + (f" {detail}" if detail else ""))
468
534
 
535
+ # Release check FIRST — being two versions behind explains most "the tool
536
+ # doesn't have X" reports, and it is the one thing nothing else surfaces.
537
+ # Non-critical: out of date is not broken, so it never fails doctor's exit code.
538
+ # Opt out with --no-version-check or MI_MCP_NO_VERSION_CHECK=1; the call is an
539
+ # anonymous PyPI index fetch (same as any install) and is skipped entirely then.
540
+ skip_vc = args.no_version_check or os.environ.get(
541
+ NO_VERSION_CHECK_ENV, ""
542
+ ).strip().lower() in ("1", "true", "yes", "on")
543
+ if skip_vc:
544
+ check("version", True, f"{__version__} (release check skipped)", critical=False)
545
+ else:
546
+ latest = _latest_pypi_version()
547
+ if latest is None:
548
+ # Unknown is NOT "up to date" — say so rather than imply green.
549
+ check("version", True,
550
+ f"{__version__} installed — could not reach PyPI, latest unknown",
551
+ critical=False)
552
+ elif _version_tuple(latest) > _version_tuple(__version__):
553
+ check("version", False,
554
+ f"{__version__} installed, {latest} available — "
555
+ f"`{_upgrade_command()} && mi-mcp wire`",
556
+ critical=False)
557
+ else:
558
+ check("version", True, f"{__version__} (latest)", critical=False)
559
+
469
560
  bin_path = _mi_mcp_bin()
470
561
  check("mi-mcp binary", Path(bin_path).exists(), bin_path)
471
562