hippmem-mcp 0.1.0__tar.gz

hippmem_mcp-0.1.0/.env.example

@@ -0,0 +1,11 @@
+# HIPPMEM MCP server configuration template
+# Copy to .env and fill in real values (optional — defaults work without API key)
+
+# --- HIPPMEM engine backend (optional) ---
+# Leave empty to use the deterministic fallback (no API key needed).
+# Set to "openai-compatible" for higher semantic accuracy.
+
+# HIPPMEM_EMBEDDING_PROVIDER=
+# HIPPMEM_EMBEDDING_BASE_URL=https://api.openai.com/v1
+# HIPPMEM_EMBEDDING_MODEL=text-embedding-3-small
+# OPENAI_API_KEY=sk-xxxxxxxxxxxx

hippmem_mcp-0.1.0/.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,29 @@
+---
+name: Bug report
+about: Report a bug in hippmem-mcp
+title: ''
+labels: bug
+assignees: ''
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Install version '...'
+2. Configure with '...'
+3. Call tool '...'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Environment**
+- hippmem-mcp version: `pip show hippmem-mcp`
+- Python version: `python --version`
+- OS: [e.g. macOS 15, Ubuntu 24.04]
+- MCP client: [e.g. Claude Desktop, VS Code]
+
+**Additional context**
+Add any other context about the problem here.

hippmem_mcp-0.1.0/.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: Feature request
+about: Suggest an idea for hippmem-mcp
+title: ''
+labels: enhancement
+assignees: ''
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or workarounds you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

hippmem_mcp-0.1.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,22 @@
+## Description
+
+<!-- Describe your changes clearly and concisely. -->
+
+## Motivation and Context
+
+<!-- Why is this change needed? What problem does it solve? -->
+
+## Type of Change
+
+- [ ] Bug fix
+- [ ] New feature
+- [ ] Documentation update
+- [ ] Refactor / performance improvement
+- [ ] CI / tooling
+
+## Checklist
+
+- [ ] Tests pass (`pytest`)
+- [ ] Commit messages follow [Conventional Commits](https://www.conventionalcommits.org/)
+- [ ] Commits include `Signed-off-by:` (DCO)
+- [ ] Documentation updated if applicable

hippmem_mcp-0.1.0/.github/workflows/ci.yml

@@ -0,0 +1,56 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+    branches: [main]
+
+jobs:
+  lint:
+    name: lint (ruff)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+      - name: Install
+        run: pip install ruff
+      - name: Lint
+        run: ruff check src/ tests/
+
+  test:
+    name: test (Python ${{ matrix.python-version }})
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.11", "3.12", "3.13"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install
+        run: pip install ".[dev]"
+      - name: Run tests
+        run: pytest tests/ -v
+
+  publish:
+    name: publish to PyPI
+    runs-on: ubuntu-latest
+    if: startsWith(github.ref, 'refs/tags/v')
+    needs: [lint, test]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: "3.11"
+      - name: Build
+        run: |
+          pip install build
+          python -m build
+      - name: Publish
+        uses: pypa/gh-action-pypi-publish@release/v1
+        with:
+          password: ${{ secrets.PYPI_TOKEN }}

hippmem_mcp-0.1.0/.gitignore

@@ -0,0 +1,34 @@
+# Python build artifacts
+__pycache__
+*.pyc
+*.egg-info
+dist/
+
+# Virtual environment
+.venv
+venv/
+
+# IDE
+.idea/
+.vscode/
+*.swp
+*.swo
+
+# OS
+.DS_Store
+Thumbs.db
+
+# Environment variables (may contain secrets)
+.env
+
+# HIPPMEM runtime data (redb database + full-text index)
+*.redb
+fulltext/
+
+# Temporary files
+.tmp/
+
+# Project-local CLAUDE.md (gitignored per project convention)
+CLAUDE.md
+scripts/publish.sh
+.publish-venv

hippmem_mcp-0.1.0/CHANGELOG.md

@@ -0,0 +1,20 @@
+# Changelog
+
+All notable changes to this project are recorded here.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/).
+
+---
+
+## [0.1.0] — unreleased
+
+### Added
+- Initial release: MCP server for HIPPMEM associative memory.
+- `write_memory` tool — write a memory; engine auto-discovers associations (entity, causal, semantic, topic, temporal).
+- `retrieve_memories` tool — multi-channel associative recall via spreading activation with explanation traces.
+- FastMCP high-level API with lifespan management.
+- Stdio transport for Claude Desktop and other MCP-compatible tools.
+- Deterministic fallback backend — zero-config, no API key, no network required.
+
+[0.1.0]: https://github.com/hippmem/hippmem-mcp/releases/tag/v0.1.0

hippmem_mcp-0.1.0/CODE_OF_CONDUCT.md

@@ -0,0 +1,51 @@
+# Code of Conduct
+
+## Conduct
+
+We are committed to providing a friendly, safe and welcoming environment for all, regardless of level of experience, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, nationality, or other similar characteristic.
+
+Please avoid using overtly sexual aliases or other nicknames that might detract from a friendly, safe and welcoming environment for all.
+
+Please be kind and courteous. There’s no need to be mean or rude.
+
+Respect that people have differences of opinion and that every design or implementation choice carries a trade-off and numerous costs. There is seldom a right answer.
+
+Please keep unstructured critique to a minimum. If you have solid ideas you want to experiment with, make a fork and see how it works.
+
+We will exclude you from interaction if you insult, demean or harass anyone. That is not welcome behavior. We interpret the term “harassment” as including the definition in the Citizen Code of Conduct; if you have any lack of clarity about what might be included in that concept, please read their definition. In particular, we don’t tolerate behavior that excludes people in socially marginalized groups.
+
+Private harassment is also unacceptable. No matter who you are, if you feel you have been or are being harassed or made uncomfortable by a community member, please contact the moderation team immediately. Whether you’re a regular contributor or a newcomer, we care about making this community a safe place for you and we’ve got your back.
+
+Likewise any spamming, trolling, flaming, baiting or other attention-stealing behavior is not welcome.
+
+## Moderation
+
+These are the policies for upholding our community’s standards of conduct. If you feel that a thread needs moderation, please contact the moderation team.
+
+Remarks that violate the Rust standards of conduct, including hateful, hurtful, oppressive, or exclusionary remarks, are not allowed. (Cursing is allowed, but never targeting another user, and never in a hateful manner.)
+
+Remarks that moderators find inappropriate, whether listed in the code of conduct or not, are also not allowed.
+
+Moderators will first respond to such remarks with a warning.
+
+If the warning is unheeded, the user will be “kicked,” i.e., kicked out of the communication channel to cool off.
+
+If the user comes back and continues to make trouble, they will be banned, i.e., indefinitely excluded.
+
+Moderators may choose at their discretion to un-ban the user if it was a first offense and they offer the offended party a genuine apology.
+
+If a moderator bans someone and you think it was unjustified, please take it up with that moderator, or with a different moderator, in private. Complaints about bans in-channel are not allowed.
+
+Moderators are held to a higher standard than other community members. If a moderator creates an inappropriate situation, they should expect less leeway than others.
+
+In the Rust community we strive to go the extra step to look out for each other. Don’t just aim to be technically unimpeachable, try to be your best self. In particular, avoid flirting with offensive or sensitive issues, particularly if they’re off-topic; this all too often leads to unnecessary fights, hurt feelings, and damaged trust; worse, it can drive people away from the community entirely.
+
+And if someone takes issue with something you said or did, resist the urge to be defensive. Just stop doing what it was they complained about and apologize. Even if you feel you were misinterpreted or unfairly accused, chances are good there was something you could’ve communicated better — remember that it’s your responsibility to make your fellow community members comfortable. Everyone wants to get along and we are all here first and foremost because we want to talk about cool technology. You will find that people will be eager to assume good intent and forgive as long as you earn their trust.
+
+The enforcement policies listed above apply to all official HIPPMEM venues, including GitHub repositories under the `hippmem` organization. For other projects adopting the Rust Code of Conduct, please contact the maintainers of those projects for enforcement.
+
+Adapted from the [Node.js Policy on Trolling](https://www.rust-lang.org/policies/code-of-conduct) as well as the Contributor Covenant v1.3.0.
+
+## Contact
+
+To report a conduct issue, email **hippmem@gmail.com**.

hippmem_mcp-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,78 @@
+# Contributing to hippmem-mcp
+
+Thanks for your interest in contributing to hippmem-mcp! This document explains how to report issues, submit changes, and follow the project conventions.
+
+## Reporting Bugs
+
+- Open an issue at <https://github.com/hippmem/hippmem-mcp/issues>.
+- Include the hippmem-mcp version (`pip show hippmem-mcp`), Python version (`python --version`), OS, and a minimal reproduction.
+- For security vulnerabilities, do **not** open a public issue — see [SECURITY.md](SECURITY.md).
+
+## Submitting a Pull Request
+
+1. Fork the repository.
+2. Create a branch from `main`:
+   ```bash
+   git checkout -b my-fix
+   ```
+3. Make your changes. Keep PRs focused — one logical change per PR.
+4. Ensure tests pass (see [Development Setup](#development-setup)).
+5. Commit using [Conventional Commits](https://www.conventionalcommits.org/):
+   ```
+   feat: add new tool for batch memory retrieval
+   fix: handle empty query gracefully
+   docs: update configuration examples
+   refactor: extract lifespan into separate module
+   test: add edge case tests for write_memory
+   chore: bump dependencies
+   ```
+6. Open a PR against `main` and describe the change, the motivation, and any trade-offs.
+
+## Development Setup
+
+```bash
+git clone https://github.com/hippmem/hippmem-mcp.git
+cd hippmem-mcp
+pip install -e ".[dev]"
+pytest
+```
+
+Requires Python ≥ 3.11. No GPU, API key, or network connection is needed — the deterministic fallback backend provides full offline coverage.
+
+## Code Style
+
+- Follow [PEP 8](https://peps.python.org/pep-0008/) with the idioms visible in the existing code.
+- Use type annotations on all public function signatures.
+- Code comments and documentation are in English.
+- Match the surrounding code's naming, density, and idioms.
+- Avoid `assert` for runtime validation — raise explicit exceptions.
+
+## Commit Format
+
+Follow [Conventional Commits](https://www.conventionalcommits.org/):
+
+```
+<type>: <short imperative summary>
+
+<optional body explaining why and what trade-offs>
+
+<optional footer>
+```
+
+Types: `feat`, `fix`, `docs`, `refactor`, `test`, `chore`, `perf`.
+
+## License
+
+hippmem-mcp is licensed under Apache 2.0 (see [COPYRIGHT](COPYRIGHT)). By contributing, you agree that your contributions will be licensed under the same terms.
+
+## DCO (Developer Certificate of Origin)
+
+All commits must include a `Signed-off-by:` line certifying that you have the right to submit the contribution:
+
+```
+feat: add new tool for batch memory retrieval
+
+Signed-off-by: Your Name <you@example.com>
+```
+
+Add the line manually to your commit message, or use `git commit -s` to append it automatically. By signing off, you attest to the [Developer Certificate of Origin](https://developercertificate.org/) v1.1.

hippmem_mcp-0.1.0/COPYRIGHT

@@ -0,0 +1,5 @@
+# COPYRIGHT · hippmem-mcp
+hippmem-mcp is distributed under the Apache License 2.0 (see LICENSE).
+This is an MCP server wrapper for HIPPMEM. The underlying engine
+(hippmem-engine) is AGPL-3.0-only.
+For commercial licensing: hippmem@gmail.com

hippmem_mcp-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 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.

hippmem_mcp-0.1.0/NOTICE

@@ -0,0 +1,4 @@
+hippmem-mcp
+Copyright 2026 hippmem
+
+This product is distributed under the Apache License, Version 2.0 (see LICENSE).

hippmem_mcp-0.1.0/PKG-INFO

@@ -0,0 +1,150 @@
+Metadata-Version: 2.4
+Name: hippmem-mcp
+Version: 0.1.0
+Summary: MCP server for HIPPMEM — give AI tools long-term associative memory
+Project-URL: Homepage, https://github.com/hippmem/hippmem-mcp
+Project-URL: Repository, https://github.com/hippmem/hippmem-mcp
+Author-email: hippmem <hippmem@gmail.com>
+License: Apache-2.0
+License-File: LICENSE
+License-File: NOTICE
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Requires-Python: >=3.11
+Requires-Dist: hippmem>=0.1.0
+Requires-Dist: mcp>=1.0.0
+Provides-Extra: dev
+Requires-Dist: mcp[cli]>=1.0; extra == 'dev'
+Requires-Dist: pytest>=7; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# hippmem-mcp
+
+**MCP server for [HIPPMEM](https://github.com/hippmem/hippmem) — give AI tools long-term associative memory.**
+
+[![CI](https://github.com/hippmem/hippmem-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/hippmem/hippmem-mcp/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/hippmem-mcp.svg)](https://pypi.org/project/hippmem-mcp/)
+[![Python](https://img.shields.io/pypi/pyversions/hippmem-mcp.svg)](https://pypi.org/project/hippmem-mcp/)
+[![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
+
+---
+
+## What is HIPPMEM?
+
+[HIPPMEM](https://github.com/hippmem/hippmem) is a native associative memory engine for AI agents, written in Rust. Instead of storing text chunks and searching them by vector similarity, it discovers associations between memories at write time and retrieves them via spreading activation at read time — so the AI recalls not just *what* was said, but *how things connect* and *why*.
+
+It runs fully offline with a deterministic fallback backend.
+
+## What is hippmem-mcp?
+
+hippmem-mcp wraps HIPPMEM as a [Model Context Protocol](https://modelcontextprotocol.io/) server. Configure it once in Claude Desktop (or any MCP-compatible tool), and your AI assistant gains persistent, associative memory across sessions — no API key required.
+
+```
+AI Tool (Claude Desktop / VS Code / ...)
+        │  MCP protocol (stdio)
+        ▼
+  hippmem-mcp
+        │  Python bindings
+        ▼
+  hippmem Engine (Rust)
+        │
+        ▼
+  Local storage (redb + Tantivy + HNSW)
+```
+
+## Key Features
+
+- **Zero config** — `pip install` then one JSON block in your MCP client configuration; deterministic fallback backend works offline
+- **Write-time association discovery** — entities, topics, goals, causal links extracted and scored automatically
+- **Spreading activation retrieval** — multi-channel seed recall (BM25 + entity + semantic + temporal + topic) fused by RRF
+- **Graph evolution** — co-activated connections strengthen (Hebbian learning); stale edges decay
+- **Explanation traces** — every result shows *why* it was recalled via `dimensions` and `matched_dimensions`
+- **Single-file storage** — one redb file + Tantivy full-text index + HNSW vector index; no external database
+
+## Install
+
+```bash
+pip install hippmem-mcp
+```
+
+Requires Python ≥ 3.11.
+
+## Configure
+
+### Claude Desktop
+
+Add to `claude_desktop_config.json`:
+
+```json
+{
+  "mcpServers": {
+    "hippmem": {
+      "command": "python",
+      "args": ["-m", "hippmem_mcp.server"]
+    }
+  }
+}
+```
+
+Or use the entry point:
+
+```json
+{
+  "mcpServers": {
+    "hippmem": {
+      "command": "hippmem-mcp"
+    }
+  }
+}
+```
+
+### Environment Variables
+
+Copy `.env.example` to `.env` and configure:
+
+| Variable | Default | Description |
+|----------|---------|-------------|
+| `HIPPMEM_EMBEDDING_PROVIDER` | *(empty = deterministic)* | Embedding backend: `openai-compatible` or leave empty for offline fallback |
+| `HIPPMEM_EMBEDDING_BASE_URL` | `https://api.openai.com/v1` | API endpoint when using remote embeddings |
+| `HIPPMEM_EMBEDDING_MODEL` | `text-embedding-3-small` | Model name for embeddings |
+| `OPENAI_API_KEY` | *(none)* | API key for OpenAI-compatible embedding services |
+
+The deterministic fallback backend requires no API key, no GPU, and no network connection.
+
+### Other MCP Clients
+
+hippmem-mcp speaks standard MCP over stdio. Configure any [MCP-compatible client](https://modelcontextprotocol.io/clients) the same way — point the `command` to `hippmem-mcp` or `python -m hippmem_mcp.server`.
+
+## Tools
+
+| Tool | Description |
+|------|-------------|
+| `write_memory` | Write a memory. The engine automatically discovers associations with existing memories. Supports `content_type` (Decision, Preference, ProjectKnowledge, TaskState, Correction, Event, Reflection) and `importance` (0.0–1.0). |
+| `retrieve_memories` | Cross-session associative recall via multi-channel seed retrieval + spreading activation. Returns scored results with `dimensions` explaining *why* each memory was recalled. Supports `top_k` and `max_hops` tuning. |
+
+## Development
+
+```bash
+git clone https://github.com/hippmem/hippmem-mcp.git
+cd hippmem-mcp
+pip install -e ".[dev]"
+pytest
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for commit conventions, PR workflow, and DCO requirements.
+
+## Documentation
+
+- [HIPPMEM main project](https://github.com/hippmem/hippmem) — engine architecture, concepts, and API reference
+- [MCP specification](https://modelcontextprotocol.io/) — Model Context Protocol
+- [Changelog](CHANGELOG.md)
+- [Security policy](SECURITY.md)
+
+## License
+
+Apache 2.0. See [LICENSE](LICENSE) and [COPYRIGHT](COPYRIGHT).
+
+The underlying HIPPMEM engine (`hippmem`) is AGPL-3.0-only. A commercial license is available — contact hippmem@gmail.com.

hippmem_mcp-0.1.0/README.md

@@ -0,0 +1,127 @@
+# hippmem-mcp
+
+**MCP server for [HIPPMEM](https://github.com/hippmem/hippmem) — give AI tools long-term associative memory.**
+
+[![CI](https://github.com/hippmem/hippmem-mcp/actions/workflows/ci.yml/badge.svg)](https://github.com/hippmem/hippmem-mcp/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/hippmem-mcp.svg)](https://pypi.org/project/hippmem-mcp/)
+[![Python](https://img.shields.io/pypi/pyversions/hippmem-mcp.svg)](https://pypi.org/project/hippmem-mcp/)
+[![License](https://img.shields.io/badge/license-Apache%202.0-blue.svg)](LICENSE)
+
+---
+
+## What is HIPPMEM?
+
+[HIPPMEM](https://github.com/hippmem/hippmem) is a native associative memory engine for AI agents, written in Rust. Instead of storing text chunks and searching them by vector similarity, it discovers associations between memories at write time and retrieves them via spreading activation at read time — so the AI recalls not just *what* was said, but *how things connect* and *why*.
+
+It runs fully offline with a deterministic fallback backend.
+
+## What is hippmem-mcp?
+
+hippmem-mcp wraps HIPPMEM as a [Model Context Protocol](https://modelcontextprotocol.io/) server. Configure it once in Claude Desktop (or any MCP-compatible tool), and your AI assistant gains persistent, associative memory across sessions — no API key required.
+
+```
+AI Tool (Claude Desktop / VS Code / ...)
+        │  MCP protocol (stdio)
+        ▼
+  hippmem-mcp
+        │  Python bindings
+        ▼
+  hippmem Engine (Rust)
+        │
+        ▼
+  Local storage (redb + Tantivy + HNSW)
+```
+
+## Key Features
+
+- **Zero config** — `pip install` then one JSON block in your MCP client configuration; deterministic fallback backend works offline
+- **Write-time association discovery** — entities, topics, goals, causal links extracted and scored automatically
+- **Spreading activation retrieval** — multi-channel seed recall (BM25 + entity + semantic + temporal + topic) fused by RRF
+- **Graph evolution** — co-activated connections strengthen (Hebbian learning); stale edges decay
+- **Explanation traces** — every result shows *why* it was recalled via `dimensions` and `matched_dimensions`
+- **Single-file storage** — one redb file + Tantivy full-text index + HNSW vector index; no external database
+
+## Install
+
+```bash
+pip install hippmem-mcp
+```
+
+Requires Python ≥ 3.11.
+
+## Configure
+
+### Claude Desktop
+
+Add to `claude_desktop_config.json`:
+
+```json
+{
+  "mcpServers": {
+    "hippmem": {
+      "command": "python",
+      "args": ["-m", "hippmem_mcp.server"]
+    }
+  }
+}
+```
+
+Or use the entry point:
+
+```json
+{
+  "mcpServers": {
+    "hippmem": {
+      "command": "hippmem-mcp"
+    }
+  }
+}
+```
+
+### Environment Variables
+
+Copy `.env.example` to `.env` and configure:
+
+| Variable | Default | Description |
+|----------|---------|-------------|
+| `HIPPMEM_EMBEDDING_PROVIDER` | *(empty = deterministic)* | Embedding backend: `openai-compatible` or leave empty for offline fallback |
+| `HIPPMEM_EMBEDDING_BASE_URL` | `https://api.openai.com/v1` | API endpoint when using remote embeddings |
+| `HIPPMEM_EMBEDDING_MODEL` | `text-embedding-3-small` | Model name for embeddings |
+| `OPENAI_API_KEY` | *(none)* | API key for OpenAI-compatible embedding services |
+
+The deterministic fallback backend requires no API key, no GPU, and no network connection.
+
+### Other MCP Clients
+
+hippmem-mcp speaks standard MCP over stdio. Configure any [MCP-compatible client](https://modelcontextprotocol.io/clients) the same way — point the `command` to `hippmem-mcp` or `python -m hippmem_mcp.server`.
+
+## Tools
+
+| Tool | Description |
+|------|-------------|
+| `write_memory` | Write a memory. The engine automatically discovers associations with existing memories. Supports `content_type` (Decision, Preference, ProjectKnowledge, TaskState, Correction, Event, Reflection) and `importance` (0.0–1.0). |
+| `retrieve_memories` | Cross-session associative recall via multi-channel seed retrieval + spreading activation. Returns scored results with `dimensions` explaining *why* each memory was recalled. Supports `top_k` and `max_hops` tuning. |
+
+## Development
+
+```bash
+git clone https://github.com/hippmem/hippmem-mcp.git
+cd hippmem-mcp
+pip install -e ".[dev]"
+pytest
+```
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for commit conventions, PR workflow, and DCO requirements.
+
+## Documentation
+
+- [HIPPMEM main project](https://github.com/hippmem/hippmem) — engine architecture, concepts, and API reference
+- [MCP specification](https://modelcontextprotocol.io/) — Model Context Protocol
+- [Changelog](CHANGELOG.md)
+- [Security policy](SECURITY.md)
+
+## License
+
+Apache 2.0. See [LICENSE](LICENSE) and [COPYRIGHT](COPYRIGHT).
+
+The underlying HIPPMEM engine (`hippmem`) is AGPL-3.0-only. A commercial license is available — contact hippmem@gmail.com.

hippmem_mcp-0.1.0/SECURITY.md

@@ -0,0 +1,24 @@
+# Security Policy
+
+## Reporting a Vulnerability
+
+Please report security vulnerabilities to **hippmem@gmail.com**.
+Do NOT open a public issue.
+
+You will receive a response within 48 hours. We will keep you
+informed of the progress toward a fix and public disclosure.
+
+## Supported Versions
+
+| Version | Supported          |
+|---------|--------------------|
+| 0.1.x   | :white_check_mark: |
+
+## Disclosure Policy
+
+We follow a coordinated disclosure process:
+
+1. Reporter submits vulnerability via email.
+2. We acknowledge within 48 hours.
+3. We develop and test a fix.
+4. We release the fix and publish an advisory.

hippmem_mcp-0.1.0/SUPPORT.md

@@ -0,0 +1,14 @@
+# Support
+
+## Documentation
+
+- [HIPPMEM main project](https://github.com/hippmem/hippmem) — engine architecture, concepts, API reference
+- [README](README.md) — install, configure, and tool reference
+- [Changelog](CHANGELOG.md)
+
+## Getting Help
+
+- **Questions & Discussions**: Open a [GitHub Discussion](https://github.com/hippmem/hippmem-mcp/discussions).
+- **Bug Reports**: Open a [GitHub Issue](https://github.com/hippmem/hippmem-mcp/issues).
+- **Security Issues**: See [SECURITY.md](SECURITY.md) — do NOT open a public issue.
+- **Commercial Licensing**: Contact hippmem@gmail.com.

hippmem_mcp-0.1.0/pyproject.toml

@@ -0,0 +1,33 @@
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+[project]
+name = "hippmem-mcp"
+version = "0.1.0"
+description = "MCP server for HIPPMEM — give AI tools long-term associative memory"
+authors = [{ name = "hippmem", email = "hippmem@gmail.com" }]
+readme = "README.md"
+license = { text = "Apache-2.0" }
+requires-python = ">=3.11"
+classifiers = [
+    "Development Status :: 4 - Beta",
+    "Intended Audience :: Developers",
+    "License :: OSI Approved :: Apache Software License",
+    "Programming Language :: Python :: 3",
+    "Topic :: Scientific/Engineering :: Artificial Intelligence",
+]
+dependencies = [
+    "hippmem>=0.1.0",
+    "mcp>=1.0.0",
+]
+
+[project.urls]
+Homepage = "https://github.com/hippmem/hippmem-mcp"
+Repository = "https://github.com/hippmem/hippmem-mcp"
+
+[project.scripts]
+hippmem-mcp = "hippmem_mcp.server:main"
+
+[project.optional-dependencies]
+dev = ["pytest>=7", "mcp[cli]>=1.0"]

hippmem_mcp-0.1.0/src/hippmem_mcp/__init__.py

@@ -0,0 +1,5 @@
+"""hippmem-mcp: MCP server for HIPPMEM associative memory."""
+
+from importlib.metadata import version as _version
+
+__version__ = _version("hippmem-mcp")

hippmem_mcp-0.1.0/src/hippmem_mcp/server.py

@@ -0,0 +1,96 @@
+"""HIPPMEM MCP server — give AI tools long-term associative memory.
+
+Usage:
+    pip install hippmem-mcp
+    hippmem-mcp                    # stdio transport (for Claude Desktop etc.)
+"""
+
+from dataclasses import dataclass
+from collections.abc import AsyncIterator
+from contextlib import asynccontextmanager
+
+from mcp.server.fastmcp import FastMCP
+from hippmem import Engine
+
+
+@dataclass
+class AppContext:
+    engine: Engine
+
+
+@asynccontextmanager
+async def lifespan(server: FastMCP) -> AsyncIterator[AppContext]:
+    engine = Engine.open()
+    try:
+        yield AppContext(engine=engine)
+    finally:
+        engine.close()
+
+
+mcp = FastMCP("hippmem", lifespan=lifespan)
+
+
+@mcp.tool()
+def write_memory(
+    content: str,
+    content_type: str | None = None,
+    importance: float | None = None,
+) -> dict:
+    """Write a memory to HIPPMEM.
+
+    The engine automatically discovers associations (entity, causal,
+    semantic, topic, temporal) with existing memories.
+
+    Args:
+        content: The memory text to store.
+        content_type: One of Decision, Preference, ProjectKnowledge,
+                      TaskState, Correction, Event, Reflection.
+        importance: 0.0-1.0 importance hint.
+    """
+    ctx = mcp.get_context()
+    engine = ctx.request_context.lifespan_context.engine
+    out = engine.write(content, content_type=content_type, importance=importance)
+    return {
+        "memory_id": out.memory_id,
+        "links_created": out.links_count,
+    }
+
+
+@mcp.tool()
+def retrieve_memories(
+    query: str,
+    top_k: int = 5,
+    max_hops: int | None = None,
+) -> list[dict]:
+    """Retrieve memories via multi-channel associative recall.
+
+    Finds not just keyword matches, but memories connected by entity,
+    causal, semantic, and temporal associations. Returns WHY, not just WHAT.
+
+    Args:
+        query: Natural-language search query.
+        top_k: Maximum number of results.
+        max_hops: Graph traversal depth (None = auto).
+    """
+    ctx = mcp.get_context()
+    engine = ctx.request_context.lifespan_context.engine
+    results = engine.retrieve(query, top_k=top_k, max_hops=max_hops)
+    return [
+        {
+            "memory_id": r.memory_id,
+            "score": round(r.score, 3),
+            "content": r.content,
+            "content_type": r.content_type,
+            "dimensions": r.dimensions,
+        }
+        for r in results.results
+    ]
+
+
+def main():
+    """Entry point. Run with stdio transport."""
+    mcp.run()
+
+
+if __name__ == "__main__":
+    main()

hippmem_mcp-0.1.0/tests/test_server.py

@@ -0,0 +1,122 @@
+"""Tests for hippmem-mcp server."""
+
+import pytest
+from hippmem_mcp.server import mcp
+
+
+class TestServerMetadata:
+    def test_server_name(self):
+        assert mcp.name == "hippmem"
+
+    def test_version(self):
+        from hippmem_mcp import __version__
+        assert isinstance(__version__, str)
+        assert len(__version__) > 0
+
+
+class TestToolsRegistration:
+    def test_write_memory_tool(self):
+        tools = mcp._tool_manager._tools
+        assert "write_memory" in tools
+
+    def test_retrieve_memories_tool(self):
+        tools = mcp._tool_manager._tools
+        assert "retrieve_memories" in tools
+
+
+class TestWriteMemoryFunctional:
+    def test_basic_write(self):
+        result = write_memory_standalone("Test memory")
+        assert "memory_id" in result
+        assert isinstance(result["links_created"], int)
+
+    def test_write_with_content_type(self):
+        result = write_memory_standalone("Decide to use Rust", content_type="Decision")
+        assert "memory_id" in result
+
+    def test_write_empty_content(self):
+        result = write_memory_standalone("")
+        assert "memory_id" in result
+
+    def test_write_long_content(self):
+        long_text = "The user prefers Rust for development. " * 50
+        result = write_memory_standalone(long_text)
+        assert "memory_id" in result
+
+
+class TestRetrieveMemoriesFunctional:
+    def test_retrieve_after_write(self):
+        write_memory_standalone("The user prefers Rust for development.")
+        results = retrieve_memories_standalone("What does the user prefer?")
+        assert len(results) > 0
+        r = results[0]
+        assert "memory_id" in r
+        assert "score" in r
+        assert "content" in r
+        assert "dimensions" in r
+
+    def test_retrieve_with_top_k(self):
+        for i in range(5):
+            write_memory_standalone(f"Memory {i}: test content for retrieval tuning.")
+        results = retrieve_memories_standalone("test content", top_k=3)
+        assert len(results) <= 3
+
+    def test_retrieve_no_match(self):
+        results = retrieve_memories_standalone("xyzzy_nonexistent_query_12345")
+        # Should return results (possibly low-scoring), not throw
+        assert isinstance(results, list)
+
+
+class TestToolSignature:
+    def test_write_memory_parameters(self):
+        fn = mcp._tool_manager._tools["write_memory"].fn
+        import inspect
+        sig = inspect.signature(fn)
+        params = list(sig.parameters.keys())
+        assert "content" in params
+
+    def test_retrieve_memories_parameters(self):
+        fn = mcp._tool_manager._tools["retrieve_memories"].fn
+        import inspect
+        sig = inspect.signature(fn)
+        params = list(sig.parameters.keys())
+        assert "query" in params
+        assert "top_k" in params
+
+
+# ---------------------------------------------------------------------------
+# Standalone helpers that bypass FastMCP context for functional testing
+# ---------------------------------------------------------------------------
+
+def write_memory_standalone(content, content_type=None, importance=None):
+    e = _get_test_engine()
+    out = e.write(content, content_type=content_type, importance=importance)
+    return {"memory_id": out.memory_id, "links_created": out.links_count}
+
+
+def retrieve_memories_standalone(query, top_k=5):
+    e = _get_test_engine()
+    results = e.retrieve(query, top_k=top_k)
+    return [
+        {
+            "memory_id": r.memory_id,
+            "score": round(r.score, 3),
+            "content": r.content,
+            "content_type": r.content_type,
+            "dimensions": r.dimensions,
+        }
+        for r in results.results
+    ]
+
+
+_test_engine = None
+
+
+def _get_test_engine():
+    global _test_engine
+    if _test_engine is None:
+        from hippmem import Engine
+        import tempfile, os
+        tmpdir = tempfile.mkdtemp()
+        _test_engine = Engine.open(os.path.join(tmpdir, "test.redb"))
+    return _test_engine