mcpscraper-memory 1.19.0 → 1.20.0

package/CHANGELOG.md

@@ -4,6 +4,28 @@ All notable changes to MCP Memory are documented here. The format is based on [K
 
 ## [Unreleased]
 
+## [1.20.0] - 2026-08-28
+
+### Added
+
+- Added immutable Personal Assistant context packets with revisioned source and attachment provenance, lifecycle controls, and owner-scoped readback in the selected vault.
+- Added authenticated original-image reads for Gmail and MMS attachment handoff, preserving bounded MIME, filename, digest, and owner authority without exposing storage credentials or signed provider URLs.
+
+### Changed
+
+- Memory remains the sole attachment-byte and object authority while the main product stores only opaque handles, digests, and bounded metadata for assistant conversations and wake packets.
+
+### Changed
+
+- Moved the consolidated Memory workspace into the main MCP Scraper product repository while preserving its hosted service and three independently versioned npm package contracts.
+- Co-located the Memory database and MCP tool packages as npm workspaces so storage, tool, and server changes can be reviewed and verified atomically while preserving their existing package names and exports.
+
+## [1.19.1] - 2026-08-27
+
+### Fixed
+
+- Made the deploy-artifact audit resolve the released attachment modules without importing the full hosted server or opening runtime services during a provider build.
+
 ## [1.19.0] - 2026-08-27
 
 ### Added

package/README.md

@@ -8,10 +8,27 @@ your [MCP Scraper](https://mcpscraper.dev) tools to gather live data and mcp-mem
 There is one backend: `https://memory.mcpscraper.dev`. This package is a thin local proxy to it —
 every tool call is forwarded over HTTPS with your API key; nothing runs or is stored on your machine.
 
-The backend consumes the shared `mcpscraper-memory-db` package for Postgres/PgVector storage, vault
-contracts, Jina embeddings, and reranking, and `mcpscraper-memory-tools` for the public tool behavior.
-Release those dependencies first, then update and redeploy this service before downstream products
-advertise a newer memory-tool contract.
+This repository also owns the independently publishable `mcpscraper-memory-db` workspace for
+Postgres/PgVector storage, vault contracts, Jina embeddings, and reranking, and the
+`mcpscraper-memory-tools` workspace for public tool behavior. The hosted backend consumes their
+released package versions. Release those dependencies first, then update and redeploy this service
+before downstream products advertise a newer memory-tool contract.
+
+## Repository development
+
+Run `npm install` once at the repository root. The root workspace then owns the server, CLI, database
+package, and tool package dependency graph:
+
+```sh
+npm run build
+npm run typecheck
+npm test
+npm run verify:workspaces
+npm run verify:packages
+```
+
+Package identities and release versions remain independent. See [`packages/README.md`](packages/README.md)
+for ownership boundaries and import provenance.
 
 ## Two ways to connect
 

package/dist/bin/mcp-stdio-server.js

@@ -9,7 +9,7 @@ import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js"
 import { ListToolsRequestSchema, CallToolRequestSchema } from "@modelcontextprotocol/sdk/types.js";
 
 // src/version.ts
-var PACKAGE_VERSION = "1.19.0";
+var PACKAGE_VERSION = "1.20.0";
 
 // bin/mcp-stdio-server.ts
 var wantsHelp = process.argv.includes("--help") || process.argv.includes("-h");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mcpscraper-memory",
-  "version": "1.19.0",
+  "version": "1.20.0",
   "description": "mcp-memory — a hosted, multi-tenant, access-controlled per-user Obsidian/Neon memory exposed AS an MCP server, with a scheduled optimization layer. Its own standalone MCP product.",
   "type": "module",
   "bin": {
@@ -13,20 +13,33 @@
   ],
   "repository": {
     "type": "git",
-    "url": "https://github.com/VilovietaSEO/mcp-memory.git"
+    "url": "https://github.com/VilovietaSEO/mcp-scraper.git",
+    "directory": "apps/memory"
   },
-  "homepage": "https://github.com/VilovietaSEO/mcp-memory#readme",
-  "bugs": "https://github.com/VilovietaSEO/mcp-memory/issues",
+  "homepage": "https://github.com/VilovietaSEO/mcp-scraper/tree/main/apps/memory#readme",
+  "bugs": "https://github.com/VilovietaSEO/mcp-scraper/issues",
   "engines": {
     "node": ">=22.13.0"
   },
+  "workspaces": [
+    "packages/memory-db",
+    "packages/memory-tools"
+  ],
   "scripts": {
     "dev": "mastra dev",
-    "build": "mastra build && node scripts/verify-mastra-build.mjs",
+    "build": "npm run build:packages && npm run build:server && npm run build:cli",
+    "build:server": "mastra build && node scripts/verify-mastra-build.mjs",
+    "build:packages": "npm run build --workspace=mcpscraper-memory-db && npm run build --workspace=mcpscraper-memory-tools",
     "build:cli": "tsup",
     "prepack": "npm run build:cli",
-    "test": "node --import tsx --test tests/*.test.mjs src/mastra/mcp/tools/*.test.ts",
-    "typecheck": "tsc --noEmit"
+    "test": "npm run test:packages && npm run test:server",
+    "test:server": "node --import tsx --test tests/*.test.mjs src/mastra/mcp/tools/*.test.ts",
+    "test:packages": "npm run test --workspace=mcpscraper-memory-db && npm run test --workspace=mcpscraper-memory-tools",
+    "typecheck": "npm run typecheck:packages && npm run typecheck:server",
+    "typecheck:server": "tsc --noEmit",
+    "typecheck:packages": "npm run typecheck --workspace=mcpscraper-memory-db && npm run typecheck --workspace=mcpscraper-memory-tools",
+    "verify:workspaces": "node scripts/verify-workspace-packages.mjs",
+    "verify:packages": "node scripts/verify-package-artifacts.mjs"
   },
   "dependencies": {
     "@mastra/core": "latest",
@@ -34,8 +47,8 @@
     "@mastra/mcp": "latest",
     "@mastra/pg": "latest",
     "@modelcontextprotocol/sdk": "^1.29.0",
-    "mcpscraper-memory-db": "1.15.1",
-    "mcpscraper-memory-tools": "1.16.0",
+    "mcpscraper-memory-db": "1.16.0",
+    "mcpscraper-memory-tools": "1.17.0",
     "zod": "^3.25.0"
   },
   "devDependencies": {