feat: Prepare for npm publishing

- Add bin/mcp-memory-keeper CLI wrapper for npx execution
- Update package.json with bin entry and npm metadata
- Add .npmignore to control published files
- Update README with simple npx installation instructions
- Add prepublishOnly script to ensure build before publish

Now users can simply run:
claude mcp add memory-keeper npx mcp-memory-keeper

This provides the best user experience, matching other MCP servers.

Author: mkreyman

.gitignore

@@ -8,4 +8,5 @@ coverage/
 .DS_Store
 .env
 *.log
-memory-keeper-export-*.json
+memory-keeper-export-*.json
+.build-marker-*

.npmignore

@@ -0,0 +1,52 @@
+# Source files
+src/
+*.ts
+!dist/**/*.d.ts
+
+# Development files
+.devcontainer/
+.github/
+.husky/
+.vscode/
+scripts/
+examples/
+
+# Test files
+__tests__/
+test/
+tests/
+*.test.js
+*.test.ts
+jest.config.js
+coverage/
+
+# Build files
+tsconfig.json
+eslint.config.js
+.prettierrc.json
+.prettierignore
+.lintstagedrc.json
+
+# Git files
+.git/
+.gitignore
+
+# Docs (except main ones)
+*.md
+!README.md
+!LICENSE
+!CHANGELOG.md
+
+# Misc
+.DS_Store
+*.log
+.env
+.env.*
+node_modules/
+*.db
+*.db-*
+.build-marker-*
+
+# Installation scripts (not needed with npm)
+install.sh
+launcher.sh

README.md

@@ -39,35 +39,31 @@ Claude Code users often face context loss when the conversation window fills up.
 
 ## Installation
 
-### Method 1: Self-Contained Launcher (Easiest)
+### Method 1: NPX (Recommended)
 
-The launcher script handles everything automatically - installation, updates, and native module rebuilds:
+The simplest way to use memory-keeper with Claude:
 
 ```bash
-# Quick install and add to Claude
-curl -fsSL https://raw.githubusercontent.com/mkreyman/mcp-memory-keeper/master/install.sh | bash
-
-# Then add to Claude (using the path shown by installer)
-claude mcp add memory-keeper "$HOME/.local/mcp-servers/memory-keeper/launcher.sh"
+claude mcp add memory-keeper npx mcp-memory-keeper
 ```
 
-### Method 2: Direct from Repository
+That's it! This will:
 
-If you've already cloned the repository:
+- Always use the latest version
+- Handle all dependencies automatically
+- Create the data directory at `~/mcp-data/memory-keeper/`
+- Work across different platforms
 
-```bash
-# Add using the launcher script
-claude mcp add memory-keeper /path/to/mcp-memory-keeper/launcher.sh
-```
+### Method 2: Global Installation
 
-The launcher automatically:
+If you prefer a global installation:
 
-- Installs memory-keeper if needed
-- Rebuilds native modules for your platform
-- Creates the data directory at `~/mcp-data/memory-keeper/`
-- Handles updates (if enabled with `MEMORY_KEEPER_AUTO_UPDATE=1`)
+```bash
+npm install -g mcp-memory-keeper
+claude mcp add memory-keeper mcp-memory-keeper
+```
 
-### Method 3: Manual Installation
+### Method 3: From Source
 
 ```bash
 # 1. Clone the repository

bin/mcp-memory-keeper

@@ -0,0 +1,52 @@
+#!/usr/bin/env node
+
+/**
+ * MCP Memory Keeper CLI
+ * This wrapper ensures the server runs correctly when invoked via npx
+ */
+
+const { spawn } = require('child_process');
+const path = require('path');
+const fs = require('fs');
+const os = require('os');
+
+// Determine the data directory
+const DATA_DIR = process.env.DATA_DIR || path.join(os.homedir(), 'mcp-data', 'memory-keeper');
+
+// Ensure data directory exists
+if (!fs.existsSync(DATA_DIR)) {
+  fs.mkdirSync(DATA_DIR, { recursive: true });
+}
+
+// Set environment variable for the server
+process.env.DATA_DIR = DATA_DIR;
+
+// Get the path to the actual server
+const serverPath = path.join(__dirname, '..', 'dist', 'index.js');
+
+// Check if the server is built
+if (!fs.existsSync(serverPath)) {
+  console.error('Error: Server not built. This should not happen with the npm package.');
+  console.error('Please report this issue at: https://github.com/mkreyman/mcp-memory-keeper/issues');
+  process.exit(1);
+}
+
+// Change to data directory (where context.db will be created)
+process.chdir(DATA_DIR);
+
+// Spawn the server
+const child = spawn(process.execPath, [serverPath, ...process.argv.slice(2)], {
+  stdio: 'inherit',
+  env: process.env
+});
+
+// Handle exit
+child.on('exit', (code) => {
+  process.exit(code);
+});
+
+// Handle errors
+child.on('error', (err) => {
+  console.error('Failed to start memory-keeper server:', err);
+  process.exit(1);
+});

package.json

@@ -3,6 +3,9 @@
   "version": "0.10.0",
   "description": "MCP server for persistent context management in AI coding assistants",
   "main": "dist/index.js",
+  "bin": {
+    "mcp-memory-keeper": "./bin/mcp-memory-keeper"
+  },
   "scripts": {
     "build": "tsc",
     "dev": "tsx src/index.ts",
@@ -19,7 +22,8 @@
     "check-all": "npm run build && npm run type-check && npm run lint && npm run format:check && npm test",
     "pre-commit": "npm run build && npm run type-check && npm run lint && npm run format:check && npm test",
     "check-migrations": "tsx scripts/check-migrations.ts",
-    "prepare": "husky"
+    "prepare": "husky",
+    "prepublishOnly": "npm run build && npm run test"
   },
   "keywords": [
     "mcp",
@@ -34,6 +38,23 @@
     "type": "git",
     "url": "https://github.com/mkreyman/mcp-memory-keeper"
   },
+  "homepage": "https://github.com/mkreyman/mcp-memory-keeper#readme",
+  "bugs": {
+    "url": "https://github.com/mkreyman/mcp-memory-keeper/issues"
+  },
+  "files": [
+    "dist/**/*",
+    "bin/**/*",
+    "README.md",
+    "LICENSE",
+    "CHANGELOG.md"
+  ],
+  "engines": {
+    "node": ">=18.0.0"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.12.3",
     "better-sqlite3": "^11.10.0",