mcp-kb-sqlite 0.1.0__tar.gz

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

@@ -0,0 +1,32 @@
+name: CI
+
+on:
+  pull_request:
+    branches: [main]
+
+jobs:
+  check-version:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Check version has no pre-release suffix
+        run: |
+          VERSION=$(grep '^version' pyproject.toml | cut -d'"' -f2)
+          echo "Version: $VERSION"
+          if ! echo "$VERSION" | grep -qE '^[0-9]+(\.[0-9]+)*$'; then
+            echo "ERROR: Version '$VERSION' is not a clean release version (only digits and dots allowed). Remove any pre-release suffix before merging to main."
+            exit 1
+          fi
+          echo "OK: Version '$VERSION' is a clean release version."
+
+  check-lock:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+      - name: Verify uv.lock is up to date
+        run: uv lock --check
+
+  test:
+    needs: check-lock
+    uses: ./.github/workflows/test.yml

mcp_kb_sqlite-0.1.0/.github/workflows/publish.yml

@@ -0,0 +1,51 @@
+name: Publish to PyPI
+
+on:
+  push:
+    branches: [main]
+
+jobs:
+  test:
+    uses: ./.github/workflows/test.yml
+
+  publish:
+    needs: test
+    runs-on: ubuntu-latest
+    environment: pypi
+    permissions:
+      id-token: write
+      contents: write
+    steps:
+      - uses: actions/checkout@v4
+        with:
+          fetch-depth: 2
+      - name: Check version changed
+        id: version
+        run: |
+          VERSION=$(grep '^version' pyproject.toml | cut -d'"' -f2)
+          if git show HEAD~1:pyproject.toml > /dev/null 2>&1; then
+            PREV=$(git diff HEAD~1 pyproject.toml | grep '^\-version' | cut -d'"' -f2)
+          else
+            PREV="$VERSION"  # pyproject.toml is new, so this is always a version change
+          fi
+          if [ -z "$PREV" ]; then
+            echo "changed=false" >> $GITHUB_OUTPUT
+          else
+            echo "changed=true" >> $GITHUB_OUTPUT
+            echo "version=$VERSION" >> $GITHUB_OUTPUT
+          fi
+      - uses: astral-sh/setup-uv@v5
+        if: steps.version.outputs.changed == 'true'
+      - name: Build
+        if: steps.version.outputs.changed == 'true'
+        run: uv build
+      - name: Publish to PyPI
+        if: steps.version.outputs.changed == 'true'
+        uses: pypa/gh-action-pypi-publish@release/v1
+      - name: Tag release
+        if: steps.version.outputs.changed == 'true'
+        run: |
+          git config user.name "github-actions[bot]"
+          git config user.email "github-actions[bot]@users.noreply.github.com"
+          git tag "v${{ steps.version.outputs.version }}"
+          git push origin "v${{ steps.version.outputs.version }}"

mcp_kb_sqlite-0.1.0/.github/workflows/test.yml

@@ -0,0 +1,18 @@
+name: Test
+
+on:
+  workflow_call:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      matrix:
+        python-version: ["3.10", "3.11", "3.12", "3.13", "3.14"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+      - name: Run tests
+        run: uv run --python ${{ matrix.python-version }} pytest

mcp_kb_sqlite-0.1.0/.gitignore

@@ -0,0 +1,221 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[codz]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#   Usually these files are written by a python script from a template
+#   before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py.cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+# Pipfile.lock
+
+# UV
+#   Similar to Pipfile.lock, it is generally recommended to include uv.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+# uv.lock
+
+# poetry
+#   Similar to Pipfile.lock, it is generally recommended to include poetry.lock in version control.
+#   This is especially recommended for binary packages to ensure reproducibility, and is more
+#   commonly ignored for libraries.
+#   https://python-poetry.org/docs/basic-usage/#commit-your-poetrylock-file-to-version-control
+# poetry.lock
+# poetry.toml
+
+# pdm
+#   Similar to Pipfile.lock, it is generally recommended to include pdm.lock in version control.
+#   pdm recommends including project-wide configuration in pdm.toml, but excluding .pdm-python.
+#   https://pdm-project.org/en/latest/usage/project/#working-with-version-control
+# pdm.lock
+# pdm.toml
+.pdm-python
+.pdm-build/
+
+# pixi
+#   Similar to Pipfile.lock, it is generally recommended to include pixi.lock in version control.
+# pixi.lock
+#   Pixi creates a virtual environment in the .pixi directory, just like venv module creates one
+#   in the .venv directory. It is recommended not to include this directory in version control.
+.pixi
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow and github.com/pdm-project/pdm
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# Redis
+*.rdb
+*.aof
+*.pid
+
+# RabbitMQ
+mnesia/
+rabbitmq/
+rabbitmq-data/
+
+# ActiveMQ
+activemq-data/
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.envrc
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+# PyCharm
+#   JetBrains specific template is maintained in a separate JetBrains.gitignore that can
+#   be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
+#   and can be added to the global gitignore or merged into this file.  For a more nuclear
+#   option (not recommended) you can uncomment the following to ignore the entire idea folder.
+# .idea/
+
+# Abstra
+#   Abstra is an AI-powered process automation framework.
+#   Ignore directories containing user credentials, local state, and settings.
+#   Learn more at https://abstra.io/docs
+.abstra/
+
+# Visual Studio Code
+#   Visual Studio Code specific template is maintained in a separate VisualStudioCode.gitignore 
+#   that can be found at https://github.com/github/gitignore/blob/main/Global/VisualStudioCode.gitignore
+#   and can be added to the global gitignore or merged into this file. However, if you prefer, 
+#   you could uncomment the following to ignore the entire vscode folder
+# .vscode/
+# Temporary file for partial code execution
+tempCodeRunnerFile.py
+
+# Ruff stuff:
+.ruff_cache/
+
+# PyPI configuration file
+.pypirc
+
+# Marimo
+marimo/_static/
+marimo/_lsp/
+__marimo__/
+
+# Streamlit
+.streamlit/secrets.toml
+
+/.idea/
+/.qlty/

mcp_kb_sqlite-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Eugene Kosyakov
+
+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.

mcp_kb_sqlite-0.1.0/PKG-INFO

@@ -0,0 +1,147 @@
+Metadata-Version: 2.5
+Name: mcp-kb-sqlite
+Version: 0.1.0
+Summary: Local long-term memory MCP server backed by SQLite FTS5
+Project-URL: Homepage, https://github.com/eukos/mcp-kb-sqlite
+Author-email: Eugene Kosyakov <eukos@yandex.by>
+License: MIT
+License-File: LICENSE
+Keywords: ai,claude,fts5,knowledge-base,llm,mcp,memory,opencode,sqlite
+Classifier: Development Status :: 4 - Beta
+Requires-Python: >=3.10
+Requires-Dist: mcp[cli]<3,>=2
+Requires-Dist: pydantic>=2
+Description-Content-Type: text/markdown
+
+# mcp-kb-sqlite
+
+Simple, fast persistent memory for your coding agent — cross-session, cross-project. One knowledge
+base shared across every repo you work in, so what you learn in one project is there the next time
+you open another. Entries can be linked to each other (`relate`), so related facts stay connected
+instead of scattered.
+
+Start a conversation with `/kb-use` to load relevant context before you begin. When you learn
+something worth keeping — an architecture decision, a gotcha, a debugging finding — save it with
+`/kb-update`.
+
+Under the hood: a plain SQLite database with an FTS5 full-text index, and a small tool surface for
+agents to search, save, and link entries. No server to run, no external service, no schema to
+manage by hand.
+
+## Install — MCP server
+
+The database lives at `~/.ai-memory/kb.db` unless you override it with `DB_PATH` (shown below,
+optional). The schema is created and migrated automatically on first connection.
+
+### Claude Code
+
+```sh
+claude mcp add kb -- uv run --directory /path/to/mcp-kb-sqlite mcp-kb-sqlite
+
+# with a custom DB_PATH:
+claude mcp add kb --env DB_PATH=/path/to/kb.db -- uv run --directory /path/to/mcp-kb-sqlite mcp-kb-sqlite
+```
+
+Or add it directly to `.mcp.json` (project-local) or `~/.claude.json` (user-scoped, under the
+top-level `mcpServers` key):
+
+```json
+{
+  "mcpServers": {
+    "kb": {
+      "type": "stdio",
+      "command": "uv",
+      "args": ["run", "--directory", "/path/to/mcp-kb-sqlite", "mcp-kb-sqlite"],
+      "env": { "DB_PATH": "/path/to/kb.db" }
+    }
+  }
+}
+```
+
+`env` is optional — drop it to use the default `~/.ai-memory/kb.db`.
+
+### OpenCode
+
+Add to `opencode.json` (global at `~/.config/opencode/opencode.json`, or project-local):
+
+```json
+{
+  "mcp": {
+    "kb": {
+      "type": "local",
+      "command": [
+        "uv",
+        "run",
+        "--directory",
+        "/path/to/mcp-kb-sqlite",
+        "mcp-kb-sqlite"
+      ],
+      "enabled": true,
+      "environment": { "DB_PATH": "/path/to/kb.db" }
+    }
+  }
+}
+```
+
+`environment` is optional — drop it to use the default `~/.ai-memory/kb.db`.
+
+## Install — skills
+
+The `/kb-use` and `/kb-update` workflows ship as skills for both Claude Code and OpenCode. The two
+flavors are hand-kept in sync — there's no generator, so edit both when instructions change.
+
+### Claude Code
+
+Copy or symlink `skills/claude/commands/*.md` into `~/.claude/commands/`.
+
+### OpenCode
+
+Copy or symlink each `skills/opencode/<name>/` directory into `~/.config/opencode/skills/<name>/`
+(or a project-local `.opencode/skills/`). OpenCode skills are auto-invoked by description match via
+the agent's `skill` tool, but can also be triggered directly as `/<name>` in chat — this prepends
+the SKILL.md text and appends whatever you typed after the command.
+
+## Tools
+
+| Tool                                                       | Purpose                                                       |
+| ---------------------------------------------------------- | ------------------------------------------------------------- |
+| `save(id?, ns?, key?, title?, description?, tags?, data?)` | Create or update an entry — see below                         |
+| `get(id, include_data=False)`                              | Fetch one entry; `include_data=True` returns the payload      |
+| `search(query, ns?, limit=10, offset=0)`                   | FTS5/BM25 over title + description + tags                     |
+| `list(ns?, limit=20, offset=0)`                            | Entries by recency, metadata only                             |
+| `list_namespaces()`                                        | Namespaces with entry counts and last-updated date            |
+| `relate(from_id, to_id, rel?)`                             | Link two entries; omit `rel` to remove all links between them |
+| `get_relations(id)`                                        | Links in both directions                                      |
+| `delete(id)`                                               | Remove an entry (cascades to its relations)                   |
+
+Entries are addressed by `ns` (namespace, e.g. `project/subsystem`) plus `key` (a slug unique within the
+namespace). `ns` filters are prefix matches, so `ns="project"` covers every subsystem under it.
+
+Only `title`, `description`, and `tags` are FTS-indexed. `data` is the payload — put schemas, code, configs
+and traces there, and make sure anything you need to _find_ also appears in one of the indexed fields.
+
+### `save`: create vs. update
+
+Every parameter is optional; the presence of `id` picks the mode.
+
+**Update** — pass `id` plus only the fields you want to change:
+
+```python
+save(id=42, description="new search hints")   # title, tags, data untouched
+```
+
+Omitted fields keep their current value. Pass `""` (or `[]` for `tags`) to clear `description`, `tags`, or
+`data`. `ns`, `key`, and `title` can be changed — that's how you rename or move an entry — but not cleared.
+
+**Create** — omit `id`; `ns`, `key`, and `title` are all required:
+
+```python
+save(ns="project/db", key="schema", title="Schema layout", tags=["db","schema"], data="…")
+```
+
+There is no upsert. Creating over an existing `(ns, key)` is an error that reports the existing id, so an
+accidental full overwrite isn't possible:
+
+```
+Error: project/db/schema already exists (id=42) — pass id=42 to update it
+```

mcp_kb_sqlite-0.1.0/README.md

@@ -0,0 +1,132 @@
+# mcp-kb-sqlite
+
+Simple, fast persistent memory for your coding agent — cross-session, cross-project. One knowledge
+base shared across every repo you work in, so what you learn in one project is there the next time
+you open another. Entries can be linked to each other (`relate`), so related facts stay connected
+instead of scattered.
+
+Start a conversation with `/kb-use` to load relevant context before you begin. When you learn
+something worth keeping — an architecture decision, a gotcha, a debugging finding — save it with
+`/kb-update`.
+
+Under the hood: a plain SQLite database with an FTS5 full-text index, and a small tool surface for
+agents to search, save, and link entries. No server to run, no external service, no schema to
+manage by hand.
+
+## Install — MCP server
+
+The database lives at `~/.ai-memory/kb.db` unless you override it with `DB_PATH` (shown below,
+optional). The schema is created and migrated automatically on first connection.
+
+### Claude Code
+
+```sh
+claude mcp add kb -- uv run --directory /path/to/mcp-kb-sqlite mcp-kb-sqlite
+
+# with a custom DB_PATH:
+claude mcp add kb --env DB_PATH=/path/to/kb.db -- uv run --directory /path/to/mcp-kb-sqlite mcp-kb-sqlite
+```
+
+Or add it directly to `.mcp.json` (project-local) or `~/.claude.json` (user-scoped, under the
+top-level `mcpServers` key):
+
+```json
+{
+  "mcpServers": {
+    "kb": {
+      "type": "stdio",
+      "command": "uv",
+      "args": ["run", "--directory", "/path/to/mcp-kb-sqlite", "mcp-kb-sqlite"],
+      "env": { "DB_PATH": "/path/to/kb.db" }
+    }
+  }
+}
+```
+
+`env` is optional — drop it to use the default `~/.ai-memory/kb.db`.
+
+### OpenCode
+
+Add to `opencode.json` (global at `~/.config/opencode/opencode.json`, or project-local):
+
+```json
+{
+  "mcp": {
+    "kb": {
+      "type": "local",
+      "command": [
+        "uv",
+        "run",
+        "--directory",
+        "/path/to/mcp-kb-sqlite",
+        "mcp-kb-sqlite"
+      ],
+      "enabled": true,
+      "environment": { "DB_PATH": "/path/to/kb.db" }
+    }
+  }
+}
+```
+
+`environment` is optional — drop it to use the default `~/.ai-memory/kb.db`.
+
+## Install — skills
+
+The `/kb-use` and `/kb-update` workflows ship as skills for both Claude Code and OpenCode. The two
+flavors are hand-kept in sync — there's no generator, so edit both when instructions change.
+
+### Claude Code
+
+Copy or symlink `skills/claude/commands/*.md` into `~/.claude/commands/`.
+
+### OpenCode
+
+Copy or symlink each `skills/opencode/<name>/` directory into `~/.config/opencode/skills/<name>/`
+(or a project-local `.opencode/skills/`). OpenCode skills are auto-invoked by description match via
+the agent's `skill` tool, but can also be triggered directly as `/<name>` in chat — this prepends
+the SKILL.md text and appends whatever you typed after the command.
+
+## Tools
+
+| Tool                                                       | Purpose                                                       |
+| ---------------------------------------------------------- | ------------------------------------------------------------- |
+| `save(id?, ns?, key?, title?, description?, tags?, data?)` | Create or update an entry — see below                         |
+| `get(id, include_data=False)`                              | Fetch one entry; `include_data=True` returns the payload      |
+| `search(query, ns?, limit=10, offset=0)`                   | FTS5/BM25 over title + description + tags                     |
+| `list(ns?, limit=20, offset=0)`                            | Entries by recency, metadata only                             |
+| `list_namespaces()`                                        | Namespaces with entry counts and last-updated date            |
+| `relate(from_id, to_id, rel?)`                             | Link two entries; omit `rel` to remove all links between them |
+| `get_relations(id)`                                        | Links in both directions                                      |
+| `delete(id)`                                               | Remove an entry (cascades to its relations)                   |
+
+Entries are addressed by `ns` (namespace, e.g. `project/subsystem`) plus `key` (a slug unique within the
+namespace). `ns` filters are prefix matches, so `ns="project"` covers every subsystem under it.
+
+Only `title`, `description`, and `tags` are FTS-indexed. `data` is the payload — put schemas, code, configs
+and traces there, and make sure anything you need to _find_ also appears in one of the indexed fields.
+
+### `save`: create vs. update
+
+Every parameter is optional; the presence of `id` picks the mode.
+
+**Update** — pass `id` plus only the fields you want to change:
+
+```python
+save(id=42, description="new search hints")   # title, tags, data untouched
+```
+
+Omitted fields keep their current value. Pass `""` (or `[]` for `tags`) to clear `description`, `tags`, or
+`data`. `ns`, `key`, and `title` can be changed — that's how you rename or move an entry — but not cleared.
+
+**Create** — omit `id`; `ns`, `key`, and `title` are all required:
+
+```python
+save(ns="project/db", key="schema", title="Schema layout", tags=["db","schema"], data="…")
+```
+
+There is no upsert. Creating over an existing `(ns, key)` is an error that reports the existing id, so an
+accidental full overwrite isn't possible:
+
+```
+Error: project/db/schema already exists (id=42) — pass id=42 to update it
+```

mcp_kb_sqlite-0.1.0/mcp_kb_sqlite/db/__init__.py

@@ -0,0 +1,38 @@
+import os
+import sqlite3
+from contextlib import contextmanager
+from pathlib import Path
+
+from mcp_kb_sqlite.db.migrations import run_migrations
+
+_db_path: Path | None = None
+
+
+def get_db_path() -> Path:
+    global _db_path
+    if _db_path is None:
+        raw = os.environ.get("DB_PATH")
+        if raw:
+            _db_path = Path(raw)
+        else:
+            _db_path = Path.home() / ".ai-memory" / "kb.db"
+        os.makedirs(_db_path.parent, exist_ok=True)
+    return _db_path
+
+
+@contextmanager
+def get_conn():
+    conn = sqlite3.connect(get_db_path(), timeout=30)
+    conn.row_factory = sqlite3.Row
+    conn.execute("PRAGMA journal_mode = WAL")
+    conn.execute("PRAGMA foreign_keys = ON")
+    try:
+        yield conn
+        conn.commit()
+    finally:
+        conn.close()
+
+
+def init_db() -> None:
+    with get_conn() as conn:
+        run_migrations(conn)