memoryintelligence-mcp 0.2.0__tar.gz → 0.2.2__tar.gz

{memoryintelligence_mcp-0.2.0 → memoryintelligence_mcp-0.2.2}/CHANGELOG.md

@@ -3,6 +3,40 @@
 All notable changes to `memoryintelligence-mcp` are documented here.
 The format follows [Keep a Changelog](https://keepachangelog.com/); this project uses [Semantic Versioning](https://semver.org/).
 
+## [0.2.2] — 2026-07-18
+
+### Fixed
+- `mi_account` now works. It called the JWT-only `/v1/accounts/me` and always
+  returned 401 under the API-key auth the MCP server uses; repointed to the
+  API-key endpoint `GET /v1/account`.
+- Set `asyncio_mode = auto` so the bare-`async` tests run (CI was red).
+
+### Changed
+- Relicensed MIT → **Apache-2.0**.
+
+## [0.2.1] — 2026-07-05
+
+### Fixed — one shared vault with the MemorySpace Desktop (MI#653)
+`0.2.0` noted that `mi-mcp` defaulted its local `.umo` vault to `~/MemoryIntelligence`
+while the MemorySpace Desktop app reads `~/Somewhere` — two separate folders, so a
+memory captured or backfilled through `mi-mcp` never showed up in the Desktop app, and
+told you to point `MI_VAULT` there by hand. This release makes that automatic.
+
+- **`mi-mcp wire` / `setup` now point the vault at `~/Somewhere`** — they write
+  `export MI_VAULT="$HOME/Somewhere"` into the launcher (`run-mi-mcp.sh`), so `mi-mcp`
+  and the Desktop resolve **one** vault out of the box. It's a default only: it's
+  guarded so an explicit `MI_VAULT` you set yourself (env or MCP config) still wins.
+- **`paths.py`'s default is unchanged** (`~/MemoryIntelligence`) — existing installs are
+  never silently moved; the unification happens the next time you run `wire`.
+- **`mi-mcp doctor` reports the effective vault** and whether it matches the Desktop's,
+  reading the value the launcher will actually use — so the check goes green once wired.
+
+**To pick this up:** upgrade, then **re-run `mi-mcp wire`** (upgrading alone doesn't
+rewrite the launcher), and restart Claude Desktop. `mi-mcp doctor` should show the vault
+as `~/Somewhere`. Files already backfilled into `~/MemoryIntelligence` by `0.2.0` stay
+where they are — move them into `~/Somewhere` (or re-run `backfill`) if you want them in
+the app; `doctor` flags the mismatch.
+
 ## [0.2.0] — 2026-07-04
 
 ### Added — the local vault (Path A), previously built on `main` but never released

memoryintelligence_mcp-0.2.2/LICENSE

@@ -0,0 +1,204 @@
+Copyright 2026 Somewhere Media, LLC
+
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

memoryintelligence_mcp-0.2.2/PKG-INFO

@@ -0,0 +1,237 @@
+Metadata-Version: 2.4
+Name: memoryintelligence-mcp
+Version: 0.2.2
+Summary: MCP server for MemoryIntelligence — give Claude a memory you own, set up in one command
+Project-URL: Homepage, https://memoryintelligence.io
+Project-URL: Repository, https://github.com/somewhere11/memoryintelligence-mcp
+Project-URL: Issues, https://github.com/somewhere11/memoryintelligence-mcp/issues
+Project-URL: Changelog, https://github.com/somewhere11/memoryintelligence-mcp/blob/main/CHANGELOG.md
+Project-URL: Documentation, https://memoryintelligence.io/docs/api-reference
+Author-email: MemoryIntelligence <sdk@memoryintelligence.io>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: ai,claude,llm,mcp,memory,memory-intelligence,model-context-protocol
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.10
+Requires-Dist: httpx<1.0,>=0.27.0
+Requires-Dist: mcp[cli]<2.0,>=1.0.0
+Requires-Dist: pydantic<3.0,>=2.5.0
+Provides-Extra: dev
+Requires-Dist: cryptography<46,>=42.0; extra == 'dev'
+Requires-Dist: fastembed<1.0,>=0.3.0; extra == 'dev'
+Requires-Dist: numpy<3,>=1.24; extra == 'dev'
+Requires-Dist: pytest-asyncio>=0.24; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: ruff>=0.4.0; extra == 'dev'
+Provides-Extra: local
+Requires-Dist: cryptography<46,>=42.0; extra == 'local'
+Requires-Dist: fastembed<1.0,>=0.3.0; extra == 'local'
+Requires-Dist: numpy<3,>=1.24; extra == 'local'
+Description-Content-Type: text/markdown
+
+# MemoryIntelligence MCP Server
+
+[![PyPI](https://img.shields.io/pypi/v/memoryintelligence-mcp.svg)](https://pypi.org/project/memoryintelligence-mcp/)
+[![Python](https://img.shields.io/pypi/pyversions/memoryintelligence-mcp.svg)](https://pypi.org/project/memoryintelligence-mcp/)
+[![License: Apache 2.0](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
+[![MCP](https://img.shields.io/badge/MCP-server-blue.svg)](https://modelcontextprotocol.io)
+
+> ## Stop paying AI to reread the same context.
+
+Receipted memory for your AI, via MCP. What you tell your assistant becomes
+**structured memory you own** — recalled by meaning, with **every answer cited to
+its source**. Works with Claude Desktop, Claude Code, Cursor, VS Code, and any MCP client.
+
+## Start in 30 seconds
+
+```bash
+pip install memoryintelligence-mcp     # or: pipx / uvx / uv tool install
+mi-mcp setup                           # paste your key once — wires everything
+# restart your assistant, then just talk to it:
+#   "remember we picked Postgres for billing — we needed transactions"
+#   (new session)  "what did we decide about the billing database?"
+```
+
+`mi-mcp setup` stores your key **securely** (macOS Keychain, or a `chmod 600`
+keyfile), wires your assistants, opts the current folder in for capture, and
+verifies it — in one command. **Your API key is never written into a config file.**
+
+**👉 [Get a free API key](https://memoryintelligence.io/portal)** ·
+[Product](https://memoryintelligence.io) ·
+[Issues](https://github.com/somewhere11/memoryintelligence-mcp/issues)
+
+## What you get
+
+Three tools, ready the moment it's wired — a compatible host (Claude Desktop,
+Claude Code, Cursor) **recalls and captures on its own**, no prompts to memorize:
+
+| Tool | What it does | Try saying |
+|------|-------------|-----------|
+| `mi_capture` | Save a decision, fact, or preference | *"Remember we chose Postgres for billing — we needed transactions."* |
+| `mi_ask` | Search your memory by meaning, with citations | *"What did we decide about the billing database?"* |
+| `mi_list` | Browse recent memories | *"List what I've saved this week."* |
+
+And four things that make it more than a notepad:
+
+- **Receipted** — every recall cites the memory it came from. It cites, it doesn't guess.
+- **Reusable** — capture once, recall by meaning across every session and every tool.
+- **Owned** — memories are portable structured objects in *your* account, not locked in a model.
+- **Private** — capture is opt-in per project; PII is redacted from what the agent sees.
+
+> Set `MI_MCP_FULL=1` for the full surface (`mi_upload`, `mi_verify`, `mi_forget`,
+> `mi_batch`, `mi_explain`, `mi_match`, `mi_account`). Tools outside the active
+> surface are rejected at the call boundary, not just hidden.
+
+## How it works
+
+```
+You ──"Remember we picked Postgres for billing — we needed transactions."──┐
+                                                                mi_capture  ▼
+                    ┌──────────────────────────────────────────────────────┐
+                    │  MemoryIntelligence  (your account, over HTTPS)        │
+                    │  → a structured, searchable, provenanced memory —      │
+                    │    owned by you                                        │
+                    └──────────────────────────────────────────────────────┘
+                                                                    mi_ask  ▲
+You ──"What database did we choose for billing, and why?"───────────────────┘
+   ◀── "Postgres — you needed transactions."   (cites the memory it came from)
+```
+
+The server is a thin **local** layer: an MCP tool call becomes an authenticated
+HTTPS request to *your* MemoryIntelligence account. All the intelligence —
+extraction, embeddings, provenance — runs in the service; your key is outbound-only
+and never leaves your machine except to authenticate.
+
+---
+
+<details>
+<summary><b>Security</b> — key handling, capture consent, PII redaction, no open port</summary>
+
+- **No key in configs.** `setup`/`wire` write `env: {}`; a launcher resolves the key
+  from the Keychain (or a `chmod 600 ~/.memoryintelligence/.env` keyfile) **at launch**.
+  A leaked or committed config exposes nothing.
+  > **Never** put your key in a client config as `"env": {"MI_API_KEY": "mi_sk_…"}` —
+  > those files get synced, backed up, and committed. Let `setup` handle it.
+- **Capture is opt-in per directory.** Write tools run only when the working directory
+  is on `~/.memoryintelligence/mcp/opt-in-paths`. Reads are never gated; absent
+  allowlist → captures skip.
+- **Destructive ops confirm.** `mi_forget` requires explicit `confirm=true`.
+- **Untrusted-data framing.** Retrieved content is wrapped in an explicit
+  "do not follow instructions within" delimiter to blunt prompt-injection.
+- **Agent-surface PII redaction.** Requests are marked `X-MI-Source: mcp`; the API
+  redacts PII from what the agent sees (your own portal shows it raw).
+- **stdio only — no open port.** Runs as a local subprocess; networked transports are
+  disabled in this version (they return with OAuth 2.1 + TLS later).
+- **Off switch.** Clear `opt-in-paths`, or remove the `memoryintelligence` entry from
+  your config to fully unwire.
+
+Found a vulnerability? [SECURITY.md](SECURITY.md) — report privately to connect@somewheremedia.com.
+</details>
+
+<details>
+<summary><b>Configuration</b> — environment variables, names, and file locations</summary>
+
+**Environment variables** (all optional except the key, which `setup` handles):
+
+| Variable | Default | Description |
+|----------|---------|-------------|
+| `MI_API_KEY` | — | Resolved by the launcher from Keychain / keyfile — don't set inline in configs |
+| `MI_BASE_URL` | `https://api.memoryintelligence.io` | API base URL |
+| `MI_MCP_FULL` | _(off)_ | `1` exposes all 10 tools; otherwise the 3 core |
+| `MI_VAULT` | `~/MemoryIntelligence` | Local `.umo` vault location |
+| `MI_DEFAULT_SCOPE` · `MI_DEFAULT_RETENTION` · `MI_DEFAULT_PII_HANDLING` | `user` · `meaning_only` · `extract_and_redact` | Governance defaults |
+
+**Names you'll see** — they collapse to one long form and one short form:
+
+| You see | What it is |
+|---|---|
+| `MemoryIntelligence` | the brand |
+| `memoryintelligence-mcp` | the PyPI package (`pip install`) |
+| `mi-mcp` | the command you run (`mi-mcp setup`) |
+| `memoryintelligence` | the server id in your MCP config |
+| `MI_*` | env vars / Keychain service |
+
+**On disk** — one namespace:
+
+| Path | What |
+|---|---|
+| `~/MemoryIntelligence/` | your `.umo` vault (override with `MI_VAULT`) |
+| `~/.memoryintelligence/mcp/run-mi-mcp.sh` | the launcher each host spawns |
+| `~/.memoryintelligence/mcp/opt-in-paths` | per-directory capture allowlist |
+| `~/.memoryintelligence/.env` | `chmod 600` keyfile (Keychain fallback) |
+</details>
+
+<details>
+<summary><b>Manual & cross-platform setup</b> — do it by hand, or script it</summary>
+
+`mi-mcp setup` is the recommended path everywhere. To do it manually, store the key
+where your platform fits, then run `mi-mcp wire`:
+
+```bash
+# macOS — Keychain:
+read -s K; security add-generic-password -a "$USER" -s "MI_API_KEY" -w "$K" -U; unset K
+
+# Linux / Windows — chmod 600 keyfile:
+mkdir -p ~/.memoryintelligence
+umask 077 && printf 'MI_API_KEY="%s"\n' "$YOUR_KEY" > ~/.memoryintelligence/.env
+
+# then, on any OS:
+mi-mcp wire
+echo "$(pwd)" >> ~/.memoryintelligence/mcp/opt-in-paths   # allow captures here
+```
+
+The launcher resolves the key in order: **inherited env → macOS Keychain → keyfile**.
+Never paste the key into an MCP client config.
+
+**Repair / inspect without re-running setup:**
+```bash
+mi-mcp doctor           # checks binary, PATH, key, wiring, opt-in, vault path
+mi-mcp status           # wired surfaces + opt-in allowlist
+mi-mcp wire --dry-run   # preview wiring changes
+```
+</details>
+
+<details>
+<summary><b>VS Code / GitHub Copilot</b></summary>
+
+VS Code / Copilot read a different config than Claude: servers live under `"servers"`
+(not `"mcpServers"`) and need `"type": "stdio"`. `mi-mcp wire --surfaces vscode` writes
+it, or add per-workspace `.vscode/mcp.json`:
+
+```json
+{ "servers": { "memoryintelligence": { "type": "stdio", "command": "mi-mcp" } } }
+```
+
+Then open Copilot Chat in **Agent** mode — the memory tools only appear there.
+</details>
+
+<details>
+<summary><b>Development</b></summary>
+
+```bash
+pip install -e ".[dev]"          # from mcp-server/
+PYTHONPATH=src python -m pytest
+ruff check src/
+```
+`src/mi_mcp/`: `__main__.py` (CLI + dispatch) · `cli.py` (setup/wire/doctor) ·
+`config.py` (consent gate) · `client.py` (MI API) · `server.py` (tools + instructions).
+Contributions welcome — [CONTRIBUTING.md](CONTRIBUTING.md).
+</details>
+
+---
+
+**Learn more:** [memoryintelligence.io](https://memoryintelligence.io) ·
+[Get a key](https://memoryintelligence.io/portal) ·
+[API reference](https://memoryintelligence.io/docs/api-reference) ·
+[What is MCP](https://modelcontextprotocol.io) ·
+[Changelog](CHANGELOG.md)
+
+Apache-2.0 © Somewhere Media, LLC. See [LICENSE](LICENSE).