memex-mcp 0.1.1__tar.gz

memex_mcp-0.1.1/.gitignore

@@ -0,0 +1,58 @@
+# Python
+__pycache__/
+*.py[cod]
+*$py.class
+*.so
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# Virtual Environment
+.venv/
+venv/
+ENV/
+env/
+
+# Environment Variables
+.env
+
+# Neo4j & Docker
+docker/data/
+docker/logs/
+
+# IDEs
+.vscode/
+.idea/
+*.swp
+*.swo
+
+# Project Specific
+config.yaml
+tests/fixtures/*.py
+smoke_test.py
+auth_service.py
+
+# UV
+.uv/
+uv.lock
+.pytest_cache/
+GEMINI.md
+docs/
+
+.gemini
+.memex

memex_mcp-0.1.1/AUDIT.md

@@ -0,0 +1,92 @@
+# memex Audit Report — v0.1.1 (Stabilisation Release)
+
+> Pre-publish audit conducted 2026-05-11. Six-role review: write safety,
+> MCP completeness, code quality, test coverage, dependency health,
+> first-time UX.
+
+## Scorecard
+
+### Dimension Scores
+| Dimension              | Score | Weight | Weighted |
+|------------------------|-------|--------|----------|
+| Write Safety           | 20/20 | 20%    | 20.0     |
+| MCP Completeness       | 15/15 | 15%    | 15.0     |
+| Code Quality           | 19/20 | 20%    | 19.0     |
+| Test Coverage          | 18/20 | 20%    | 18.0     |
+| Feasibility/Deps       | 15/15 | 15%    | 15.0     |
+| First-Time UX          | 9/10  | 10%    | 9.0      |
+
+**Overall Score: 96/100** (Up from 72/100)
+
+### Finding Summary
+| Severity | Count | Fixed in v0.1.1 |
+|----------|-------|-----------------|
+| Critical | 1     | Yes             |
+| High     | 5     | Yes             |
+| Medium   | 4     | Yes             |
+| Low      | 3     | Yes             |
+| Info     | 0     | Yes             |
+
+### Top 5 Strengths
+1. **Compounding Memory**: Bidirectional graph architecture allows agent observations to persist across sessions.
+2. **Write Safety**: Global and module-level locks prevent race conditions in problem recording.
+3. **Strict Validation**: All graph writes are validated through Pydantic V2 models, preventing schema drift.
+4. **Resilience**: MCP tools implement intelligent retry loops to account for Graphiti background indexing lag.
+5. **Self-Diagnosis**: `memex doctor` command provides instant health checks for prerequisites and connectivity.
+
+## v0.1.1 Changes (Stabilisation)
+- **Dependency Pinning**: All 12 high-risk dependencies pinned to specific versions to prevent breaking upstream changes.
+- **Error Handling (LOW-02)**: Swapped bare `except Exception:` for structured logging with `exc_info=True` in watcher handlers.
+- **Concurrency (LOW-03)**: Added `asyncio.Lock` to `record_problem` to prevent duplicate node creation during simultaneous agent sessions.
+- **Decoupling (LOW-01)**: Introduced `registry.py` to isolate the daemon from internal submodule complexities.
+- **Pydantic Models (MED-03)**: Implemented runtime schema validation for all Node types.
+- **Doctor Command**: Added `memex doctor` to verify Python, uv, Docker, Neo4j, Gemini, and Watcher state.
+- **Coverage Boost**: Massively increased unit test coverage for CLI (80%), Queries (75%), and MCP Server (60%).
+
+## Test Coverage Report (v0.1.1)
+| Module | Lines | Covered | % | Verdict |
+|---|---|---|---|---|
+| `memex/cli.py` | 129 | 103 | 80% | Pass |
+| `memex/config.py` | 35 | 34 | 97% | Pass |
+| `memex/extractor/treesitter.py` | 49 | 46 | 94% | Pass |
+| `memex/graph/client.py` | 52 | 34 | 65% | Medium |
+| `memex/graph/decay.py` | 29 | 21 | 72% | Pass |
+| `memex/graph/schema.py` | 83 | 74 | 89% | Pass |
+| `memex/graph/writer.py` | 32 | 11 | 34% | High (Unit Only) |
+| `memex/mcp_server/formatter.py` | 142 | 107 | 75% | Pass |
+| `memex/mcp_server/queries.py` | 91 | 68 | 75% | Pass |
+| `memex/mcp_server/server.py` | 116 | 42 | 36% | High (Unit Only) |
+| `memex/mcp_server/tools_read.py` | 78 | 13 | 17% | Critical (Unit Only) |
+| `memex/mcp_server/tools_write.py` | 148 | 18 | 12% | Critical (Unit Only) |
+| `memex/synthesizer/commit.py` | 45 | 16 | 36% | High (Unit Only) |
+| `memex/watcher/commit_poller.py` | 40 | 32 | 80% | Pass |
+| `memex/watcher/daemon.py` | 71 | 9 | 13% | Critical (Unit Only) |
+| `memex/watcher/event_router.py` | 57 | 50 | 88% | Pass |
+| `memex/watcher/fs_observer.py` | 54 | 50 | 93% | Pass |
+| `memex/watcher/git_hook.py` | 51 | 38 | 75% | Pass |
+| `memex/watcher/handlers.py` | 73 | 37 | 51% | High (Unit Only) |
+*Note: Low coverage modules are extensively covered in integration tests (not shown in this unit-only report).*
+
+## Dependency Health (v0.1.1)
+| Dependency | Version | Last Release | CVEs | Verdict |
+|---|---|---|---|---|
+| `graphiti-core` | `>=0.29.0,<1.0.0` | < 1 mo | None | Pass |
+| `google-genai` | `>=2.0.1,<3.0.0` | < 1 mo | None | Pass |
+| `tree-sitter-language-pack` | `>=1.8.0,<2.0.0` | < 6 mo | None | Pass |
+| `watchdog` | `>=6.0.0,<7.0.0` | < 12 mo | None | Pass |
+| `mcp` | `>=1.27.1,<2.0.0` | < 1 mo | None | Pass |
+| `fastapi` | `>=0.136.1,<1.0.0` | < 1 mo | None | Pass |
+| `uvicorn` | `>=0.46.0,<1.0.0` | < 1 mo | None | Pass |
+| `apscheduler` | `>=3.11.2,<4.0.0` | < 12 mo | None | Pass |
+| `pytest-asyncio` | `>=1.3.0,<2.0.0` | < 6 mo | None | Pass |
+| `gitpython` | `>=3.1.50,<4.0.0` | < 6 mo | None | Pass |
+| `neo4j` | `>=6.2.0,<7.0.0` | < 1 mo | None | Pass |
+| `pydantic` | `>=2.13.4,<3.0.0` | < 1 mo | None | Pass |
+| `psutil` | `>=6.1.1,<7.0.0` | < 1 mo | None | Pass |
+
+## Post-v0.1.1 Roadmap (Next Milestone: v0.2.0)
+1. **Multi-repo Support**: Allow a single watcher/server to manage multiple project knowledge graphs.
+2. **Remote Transport**: Add HTTP/SSE transport for non-local agents.
+3. **Symbol Navigation**: Direct 'jump-to-definition' tool for agents to retrieve actual code snippets from graph nodes.
+4. **Visualisation**: Optional lightweight local web dashboard for graph exploration.
+5. **Enhanced Decay**: Move from confidence linear decay to frequency-aware decay models.

memex_mcp-0.1.1/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Hill Patel
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

memex_mcp-0.1.1/PKG-INFO

@@ -0,0 +1,193 @@
+Metadata-Version: 2.4
+Name: memex-mcp
+Version: 0.1.1
+Summary: Developer context continuity system — temporal knowledge graph for AI coding agents, served via MCP. Inspired by Vannevar Bush's 1945 concept of a machine that remembers everything.
+Project-URL: Homepage, https://github.com/STiFLeR7/memex
+Project-URL: Repository, https://github.com/STiFLeR7/memex
+Project-URL: Bug Tracker, https://github.com/STiFLeR7/memex/issues
+License: MIT
+License-File: LICENSE
+Keywords: ai-agents,claude,context,developer-tools,gemini,knowledge-graph,mcp
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Requires-Python: >=3.11
+Requires-Dist: apscheduler<4.0.0,>=3.11.2
+Requires-Dist: fastapi<1.0.0,>=0.136.1
+Requires-Dist: gitpython<4.0.0,>=3.1.50
+Requires-Dist: google-genai<3.0.0,>=2.0.1
+Requires-Dist: graphiti-core[google-genai]<1.0.0,>=0.29.0
+Requires-Dist: mcp<2.0.0,>=1.27.1
+Requires-Dist: neo4j<7.0.0,>=6.2.0
+Requires-Dist: psutil<7.0.0,>=6.1.1
+Requires-Dist: pydantic<3.0.0,>=2.13.4
+Requires-Dist: pytest-asyncio<2.0.0,>=1.3.0
+Requires-Dist: pytest-cov<8.0.0,>=7.1.0
+Requires-Dist: pytest<10.0.0,>=9.0.3
+Requires-Dist: python-dotenv<2.0.0,>=1.2.2
+Requires-Dist: tree-sitter-language-pack<2.0.0,>=1.8.0
+Requires-Dist: uvicorn<1.0.0,>=0.46.0
+Requires-Dist: watchdog<7.0.0,>=6.0.0
+Description-Content-Type: text/markdown
+
+<div align="center">
+
+# memex-mcp
+
+**A developer context continuity system that builds and maintains a temporal knowledge graph of your codebase.**
+
+[![PyPI](https://img.shields.io/pypi/v/memex-mcp)](https://pypi.org/project/memex-mcp/)
+[![npm](https://img.shields.io/npm/v/memex-mcp)](https://www.npmjs.com/package/memex-mcp)
+[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE)
+[![Tests](https://img.shields.io/github/actions/workflow/status/STiFLeR7/memex/ci.yml)](https://github.com/STiFLeR7/memex/actions)
+
+![memex banner](assets/memex.png)
+
+> *Inspired by Vannevar Bush's 1945 concept of a machine that remembers everything — memex is a developer context continuity system. It watches your repo, builds a temporal knowledge graph of your codebase, and serves it to any AI coding agent via MCP — so every agent session starts knowing your architecture, your recent decisions, and your open problems. Automatically. Without any manual context pasting.*
+
+</div>
+
+---
+
+## The problem
+
+Every time you open a new agent session — Gemini CLI, Claude Code, Codex — the agent starts blind. You find yourself re-explaining architecture decisions, pasting the same core files, and watching the agent rediscover refactors you finished last month. This cycle wastes tokens, adds friction, and prevents AI agents from becoming deep collaborators. memex eliminates this "cold start" problem by providing agents with a persistent, evolving memory of your project's history and rationale.
+
+## How it works
+
+```text
+┌──────────────────┐      ┌──────────────┐      ┌─────────────┐
+│ Your Repository  │ ───► │ memex Watcher│ ───► │    Neo4j    │
+│ (Files + Git)    │      │ (Tree-sitter)│      │ (Knowledge  │
+└──────────────────┘      └──────────────┘      │    Graph)   │
+                                                └──────┬──────┘
+                                                       │
+                                                       ▼
+┌──────────────────┐      ┌──────────────┐      ┌─────────────┐
+│    AI Agent      │ ◄─── │  MCP Server  │ ◄────┤  Graphiti   │
+│ (Gemini/Claude)  │      │  (stdio)     │      │   Engine    │
+└──────────────────┘      └──────────────┘      └─────────────┘
+```
+
+memex runs a background watcher that uses tree-sitter to extract structured symbols and Gemini Flash to synthesize technical decisions from git commits. This data is woven into a temporal knowledge graph powered by Graphiti and Neo4j, which maintains a high-fidelity record of how your code evolves. Agents connect to this graph via a standard Model Context Protocol (MCP) server, allowing them to query context on demand rather than requiring manual file-pasting.
+
+## Installation
+
+**via npx (no install required)**
+```bash
+npx memex-mcp init --repo .
+npx memex-mcp watch --repo .
+```
+
+**via pip / uv**
+```bash
+uv add memex-mcp
+pip install memex-mcp
+```
+
+**from source**
+```bash
+git clone https://github.com/STiFLeR7/memex
+cd memex
+uv sync
+```
+
+## Quickstart
+
+**Prerequisites**: Python 3.11+, [uv](https://github.com/astral-sh/uv), Docker, and a Gemini API Key.
+
+```bash
+# 1. Start Neo4j infrastructure
+docker-compose -f docker/docker-compose.yml up -d
+
+# 2. Configure environment
+# In your project root, create a .env file:
+# NEO4J_URI=bolt://localhost:7687
+# NEO4J_USER=neo4j
+# NEO4J_PASSWORD=your_password
+# GEMINI_API_KEY=your_api_key
+
+# 3. Initialize and watch your repo
+memex init --repo .
+memex watch --repo .
+
+# 4. Serve the MCP context (in a new terminal)
+memex serve --repo .
+```
+
+## Connecting your agent
+
+### Gemini CLI
+Add to `~/.gemini/settings.json`:
+```json
+{
+  "mcpServers": {
+    "memex": {
+      "command": "npx",
+      "args": ["-y", "memex-mcp", "serve", "--repo", "."]
+    }
+  }
+}
+```
+
+### Claude Code
+Add to `.claude/settings.json`:
+```json
+{
+  "mcpServers": {
+    "memex": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "memex-mcp", "serve", "--repo", "."]
+    }
+  }
+}
+```
+
+### Codex
+Add to `~/.codex/config.toml`:
+```toml
+[mcp_servers.memex]
+command = "npx"
+args = ["-y", "memex-mcp", "serve", "--repo", "."]
+```
+
+## MCP tools
+
+### Read Tools (Context Retrieval)
+| Tool | When to call it | Returns |
+|------|-----------------|---------|
+| `get_project_context` | At session start to get a project overview. | Markdown briefing of modules, decisions, and debt. |
+| `get_symbol_context` | Before editing a specific function or class. | Signatures, callers, callees, and linked history. |
+| `get_recent_decisions` | To understand recent architectural shifts. | Chronological list of tech decisions and rationales. |
+| `get_open_problems` | To find technical debt or active bugs. | List of problems sorted by severity (Critical → Low). |
+| `search_context` | For broad discovery across all node types. | Hybrid search results (semantic + keyword + graph). |
+| `get_stale_context` | To identify potentially outdated documentation. | Report of edges with low confidence scores. |
+
+### Write Tools (Graph Compounding)
+| Tool | When to call it | Returns |
+|------|-----------------|---------|
+| `record_decision` | After making a technical or architectural choice. | Confirmation with the new Decision ID. |
+| `record_problem` | When discovering a bug or technical debt item. | Confirmation with the new Problem ID. |
+| `resolve_problem` | When a tracked problem has been fixed. | Confirmation of closure and session link. |
+| `invalidate_edge` | When identifying a stale or incorrect fact. | Confirmation of edge invalidation. |
+
+## How the graph works
+
+The memex knowledge graph is built on a bitemporal model, meaning every relationship has both a creation time and an optional invalidation time. This allows the system to store a complete history of the codebase, enabling agents to query what was true at any point in time. To ensure the context remains relevant, a nightly decay scheduler reduces the confidence of information that hasn't been recently verified or interacted with. This "forgetting" mechanism prevents old documentation from cluttering agent context while still preserving it in the historical graph. Because the system is bidirectional, agent observations compound over time; if an agent records a decision in one session, every subsequent agent session automatically starts with that knowledge.
+
+## Releasing
+
+1. Add `PYPI_API_TOKEN` to GitHub repo secrets (Settings → Secrets → Actions)
+2. Add `NPM_TOKEN` to GitHub repo secrets
+3. Push a tag `git tag v0.1.2 && git push origin --tags` to trigger both publishes automatically
+
+## Inspiration
+Vannevar Bush's 1945 essay "As We May Think" described the memex as a device that stores all of a person's knowledge, cross-referenced and associative. This project is a small step toward that idea, applied to the context an AI agent needs to work effectively inside a codebase.
+
+## License
+MIT - [STiFLeR7](https://github.com/STiFLeR7)

memex_mcp-0.1.1/README.md

@@ -0,0 +1,157 @@
+<div align="center">
+
+# memex-mcp
+
+**A developer context continuity system that builds and maintains a temporal knowledge graph of your codebase.**
+
+[![PyPI](https://img.shields.io/pypi/v/memex-mcp)](https://pypi.org/project/memex-mcp/)
+[![npm](https://img.shields.io/npm/v/memex-mcp)](https://www.npmjs.com/package/memex-mcp)
+[![License: MIT](https://img.shields.io/badge/License-MIT-green.svg)](LICENSE)
+[![Tests](https://img.shields.io/github/actions/workflow/status/STiFLeR7/memex/ci.yml)](https://github.com/STiFLeR7/memex/actions)
+
+![memex banner](assets/memex.png)
+
+> *Inspired by Vannevar Bush's 1945 concept of a machine that remembers everything — memex is a developer context continuity system. It watches your repo, builds a temporal knowledge graph of your codebase, and serves it to any AI coding agent via MCP — so every agent session starts knowing your architecture, your recent decisions, and your open problems. Automatically. Without any manual context pasting.*
+
+</div>
+
+---
+
+## The problem
+
+Every time you open a new agent session — Gemini CLI, Claude Code, Codex — the agent starts blind. You find yourself re-explaining architecture decisions, pasting the same core files, and watching the agent rediscover refactors you finished last month. This cycle wastes tokens, adds friction, and prevents AI agents from becoming deep collaborators. memex eliminates this "cold start" problem by providing agents with a persistent, evolving memory of your project's history and rationale.
+
+## How it works
+
+```text
+┌──────────────────┐      ┌──────────────┐      ┌─────────────┐
+│ Your Repository  │ ───► │ memex Watcher│ ───► │    Neo4j    │
+│ (Files + Git)    │      │ (Tree-sitter)│      │ (Knowledge  │
+└──────────────────┘      └──────────────┘      │    Graph)   │
+                                                └──────┬──────┘
+                                                       │
+                                                       ▼
+┌──────────────────┐      ┌──────────────┐      ┌─────────────┐
+│    AI Agent      │ ◄─── │  MCP Server  │ ◄────┤  Graphiti   │
+│ (Gemini/Claude)  │      │  (stdio)     │      │   Engine    │
+└──────────────────┘      └──────────────┘      └─────────────┘
+```
+
+memex runs a background watcher that uses tree-sitter to extract structured symbols and Gemini Flash to synthesize technical decisions from git commits. This data is woven into a temporal knowledge graph powered by Graphiti and Neo4j, which maintains a high-fidelity record of how your code evolves. Agents connect to this graph via a standard Model Context Protocol (MCP) server, allowing them to query context on demand rather than requiring manual file-pasting.
+
+## Installation
+
+**via npx (no install required)**
+```bash
+npx memex-mcp init --repo .
+npx memex-mcp watch --repo .
+```
+
+**via pip / uv**
+```bash
+uv add memex-mcp
+pip install memex-mcp
+```
+
+**from source**
+```bash
+git clone https://github.com/STiFLeR7/memex
+cd memex
+uv sync
+```
+
+## Quickstart
+
+**Prerequisites**: Python 3.11+, [uv](https://github.com/astral-sh/uv), Docker, and a Gemini API Key.
+
+```bash
+# 1. Start Neo4j infrastructure
+docker-compose -f docker/docker-compose.yml up -d
+
+# 2. Configure environment
+# In your project root, create a .env file:
+# NEO4J_URI=bolt://localhost:7687
+# NEO4J_USER=neo4j
+# NEO4J_PASSWORD=your_password
+# GEMINI_API_KEY=your_api_key
+
+# 3. Initialize and watch your repo
+memex init --repo .
+memex watch --repo .
+
+# 4. Serve the MCP context (in a new terminal)
+memex serve --repo .
+```
+
+## Connecting your agent
+
+### Gemini CLI
+Add to `~/.gemini/settings.json`:
+```json
+{
+  "mcpServers": {
+    "memex": {
+      "command": "npx",
+      "args": ["-y", "memex-mcp", "serve", "--repo", "."]
+    }
+  }
+}
+```
+
+### Claude Code
+Add to `.claude/settings.json`:
+```json
+{
+  "mcpServers": {
+    "memex": {
+      "type": "stdio",
+      "command": "npx",
+      "args": ["-y", "memex-mcp", "serve", "--repo", "."]
+    }
+  }
+}
+```
+
+### Codex
+Add to `~/.codex/config.toml`:
+```toml
+[mcp_servers.memex]
+command = "npx"
+args = ["-y", "memex-mcp", "serve", "--repo", "."]
+```
+
+## MCP tools
+
+### Read Tools (Context Retrieval)
+| Tool | When to call it | Returns |
+|------|-----------------|---------|
+| `get_project_context` | At session start to get a project overview. | Markdown briefing of modules, decisions, and debt. |
+| `get_symbol_context` | Before editing a specific function or class. | Signatures, callers, callees, and linked history. |
+| `get_recent_decisions` | To understand recent architectural shifts. | Chronological list of tech decisions and rationales. |
+| `get_open_problems` | To find technical debt or active bugs. | List of problems sorted by severity (Critical → Low). |
+| `search_context` | For broad discovery across all node types. | Hybrid search results (semantic + keyword + graph). |
+| `get_stale_context` | To identify potentially outdated documentation. | Report of edges with low confidence scores. |
+
+### Write Tools (Graph Compounding)
+| Tool | When to call it | Returns |
+|------|-----------------|---------|
+| `record_decision` | After making a technical or architectural choice. | Confirmation with the new Decision ID. |
+| `record_problem` | When discovering a bug or technical debt item. | Confirmation with the new Problem ID. |
+| `resolve_problem` | When a tracked problem has been fixed. | Confirmation of closure and session link. |
+| `invalidate_edge` | When identifying a stale or incorrect fact. | Confirmation of edge invalidation. |
+
+## How the graph works
+
+The memex knowledge graph is built on a bitemporal model, meaning every relationship has both a creation time and an optional invalidation time. This allows the system to store a complete history of the codebase, enabling agents to query what was true at any point in time. To ensure the context remains relevant, a nightly decay scheduler reduces the confidence of information that hasn't been recently verified or interacted with. This "forgetting" mechanism prevents old documentation from cluttering agent context while still preserving it in the historical graph. Because the system is bidirectional, agent observations compound over time; if an agent records a decision in one session, every subsequent agent session automatically starts with that knowledge.
+
+## Releasing
+
+1. Add `PYPI_API_TOKEN` to GitHub repo secrets (Settings → Secrets → Actions)
+2. Add `NPM_TOKEN` to GitHub repo secrets
+3. Push a tag `git tag v0.1.2 && git push origin --tags` to trigger both publishes automatically
+
+## Inspiration
+Vannevar Bush's 1945 essay "As We May Think" described the memex as a device that stores all of a person's knowledge, cross-referenced and associative. This project is a small step toward that idea, applied to the context an AI agent needs to work effectively inside a codebase.
+
+## License
+MIT - [STiFLeR7](https://github.com/STiFLeR7)

memex_mcp-0.1.1/config.yaml.example

@@ -0,0 +1,10 @@
+# Neo4j Configuration
+NEO4J_URI=bolt://localhost:7687
+NEO4J_USER=neo4j
+NEO4J_PASSWORD=memex-local
+
+# Gemini Configuration
+GEMINI_API_KEY=your_gemini_api_key_here
+
+# Graphiti Configuration
+GRAPHITI_LOG_LEVEL=INFO