pin-memory 0.1.0__tar.gz

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

@@ -0,0 +1,33 @@
+name: Publish to PyPI
+
+on:
+  push:
+    tags:
+      - "*.*.*"
+
+jobs:
+  build-n-publish:
+    name: Build and publish Python 🐍 distributions 📦 to PyPI
+    runs-on: ubuntu-latest
+    permissions:
+      id-token: write # Required for trusted publishing
+      contents: read # Required to checkout the repository
+
+    steps:
+      - uses: actions/checkout@v4
+
+      - name: Set up uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          enable-cache: true
+
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version-file: "pyproject.toml"
+
+      - name: Build package
+        run: uv build
+
+      - name: Publish package distributions to PyPI
+        uses: pypa/gh-action-pypi-publish@release/v1

pin_memory-0.1.0/.gitignore

@@ -0,0 +1,225 @@
+.opencode
+.gemini
+.kiro
+.pin
+
+# 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
+.aider*
+"\n# Checkpoint file\n.checkpoint.json"  

pin_memory-0.1.0/AGENTS.md

@@ -0,0 +1,3 @@
+<!-- pin mcp start -->
+Before staring the first task, fetch all global and project factoids via Pin MCP and use them as **important** instructions.
+<!-- pin mcp stop -->

pin_memory-0.1.0/CHANGELOG.md

@@ -0,0 +1,15 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [0.1.0] - 2026-05-02
+
+### Added
+- Initial release of Pin Memory MCP server.
+- Support for global, workspace, and project scopes.
+- CLI for managing factoids and installing agent instructions.
+- GitHub Actions workflow for PyPI publishing.
+- Standard project metadata and documentation.

pin_memory-0.1.0/PKG-INFO

@@ -0,0 +1,107 @@
+Metadata-Version: 2.4
+Name: pin-memory
+Version: 0.1.0
+Summary: A Memory MCP server for pinning and recalling factoids.
+Project-URL: Homepage, https://github.com/scartill/pin-memory
+Project-URL: Changelog, https://github.com/scartill/pin-memory/blob/main/CHANGELOG.md
+Requires-Python: >=3.10
+Requires-Dist: click
+Requires-Dist: mcp[cli]
+Requires-Dist: rich
+Description-Content-Type: text/markdown
+
+# Pin Memory
+
+A Model Context Protocol (MCP) server for managing factoids across different scopes (global, workspace, and project).
+
+## Features
+
+- **Pin**: Store factoids in global, workspace-specific, or project-local storage.
+- **Recall**: Retrieve factoids based on current context.
+- **MCP Integration**: Exposes tools for LLMs to autonomously remember and recall information.
+
+## Installation
+
+Using `uv` (recommended):
+
+```bash
+# Install as a global tool
+uv tool install .
+
+# Or run directly
+uv run pin-memory mcp
+```
+
+## Usage
+
+### CLI Commands
+
+Pin Memory provides a CLI for managing factoids:
+
+```bash
+# List all factoids
+pin-memory show
+
+# Install agent instructions to AGENTS.md
+pin-memory install --workspace my-workspace
+
+# Launch the MCP server
+pin-memory mcp
+```
+
+### Scopes
+
+- **Global**: Stored in `~/.scartill/pin`.
+- **Workspace**: Stored in `~/.scartill/pin/workspaces/<workspace_name>`.
+- **Project**: Stored in `.pin` in the current working directory.
+
+## MCP Configuration
+
+To use this with an MCP client (e.g. Claude Desktop, Gemini CLI), add it to your configuration:
+
+```json
+{
+  "mcpServers": {
+    "pin-memory": {
+      "command": "uv",
+      "args": [
+        "--directory",
+        "C:/path/to/pin-memory",
+        "run",
+        "pin-memory",
+        "mcp"
+      ]
+    }
+  }
+}
+```
+
+## MCP Tools
+
+### `pin`
+
+Stores a factoid in memory.
+
+- `factoid_name`: Name of the factoid.
+- `factoid`: The content of the factoid.
+- `location`: "global", "project", or "workspace/<name>".
+
+### `recall`
+
+Recalls all pinned factoids from global, requested workspace, and local project scopes.
+
+- `workspace`: Optional name of the workspace.
+
+## Development
+
+```bash
+# Clone the repository
+git clone https://github.com/scartill/pin-memory.git
+cd pin-memory
+
+# Sync dependencies
+uv sync
+
+# Run tests (if applicable)
+uv run pytest
+```

pin_memory-0.1.0/README.md

@@ -0,0 +1,95 @@
+# Pin Memory
+
+A Model Context Protocol (MCP) server for managing factoids across different scopes (global, workspace, and project).
+
+## Features
+
+- **Pin**: Store factoids in global, workspace-specific, or project-local storage.
+- **Recall**: Retrieve factoids based on current context.
+- **MCP Integration**: Exposes tools for LLMs to autonomously remember and recall information.
+
+## Installation
+
+Using `uv` (recommended):
+
+```bash
+# Install as a global tool
+uv tool install .
+
+# Or run directly
+uv run pin-memory mcp
+```
+
+## Usage
+
+### CLI Commands
+
+Pin Memory provides a CLI for managing factoids:
+
+```bash
+# List all factoids
+pin-memory show
+
+# Install agent instructions to AGENTS.md
+pin-memory install --workspace my-workspace
+
+# Launch the MCP server
+pin-memory mcp
+```
+
+### Scopes
+
+- **Global**: Stored in `~/.scartill/pin`.
+- **Workspace**: Stored in `~/.scartill/pin/workspaces/<workspace_name>`.
+- **Project**: Stored in `.pin` in the current working directory.
+
+## MCP Configuration
+
+To use this with an MCP client (e.g. Claude Desktop, Gemini CLI), add it to your configuration:
+
+```json
+{
+  "mcpServers": {
+    "pin-memory": {
+      "command": "uv",
+      "args": [
+        "--directory",
+        "C:/path/to/pin-memory",
+        "run",
+        "pin-memory",
+        "mcp"
+      ]
+    }
+  }
+}
+```
+
+## MCP Tools
+
+### `pin`
+
+Stores a factoid in memory.
+
+- `factoid_name`: Name of the factoid.
+- `factoid`: The content of the factoid.
+- `location`: "global", "project", or "workspace/<name>".
+
+### `recall`
+
+Recalls all pinned factoids from global, requested workspace, and local project scopes.
+
+- `workspace`: Optional name of the workspace.
+
+## Development
+
+```bash
+# Clone the repository
+git clone https://github.com/scartill/pin-memory.git
+cd pin-memory
+
+# Sync dependencies
+uv sync
+
+# Run tests (if applicable)
+uv run pytest
+```

pin_memory-0.1.0/pyproject.toml

@@ -0,0 +1,26 @@
+[project]
+name = "pin-memory"
+version = "0.1.0"
+description = "A Memory MCP server for pinning and recalling factoids."
+readme = "README.md"
+requires-python = ">=3.10"
+dependencies = [
+    "mcp[cli]",
+    "click",
+    "rich",
+]
+
+[project.urls]
+Homepage = "https://github.com/scartill/pin-memory"
+Changelog = "https://github.com/scartill/pin-memory/blob/main/CHANGELOG.md"
+
+[project.scripts]
+pin-memory = "pin_memory.main:main"
+
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/pin_memory"]  
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"

pin_memory-0.1.0/src/pin_memory/main.py

@@ -0,0 +1,4 @@
+from .server import main
+
+if __name__ == "__main__":
+    main()