PCE Memory
Process-Context Engine (PCE) - MCP Server for Context-Aware Memory & Retrieval
Overview
PCE Memoryは、LLMエージェントやアプリケーションに文脈記憶・検索・統合機能を提供するMCPサーバーです。
Key Features
- 🔒 Boundary-first Security: スコープベースの境界管理とRedact-before-send
- 🧠 Dual-phase Memory: LCP (長期記憶) + AC (短期記憶) の二相アーキテクチャ
- 🔍 Hybrid Search: FTS + VSS のハイブリッド検索 (r, S, g 関数)
- 📊 DuckDB Storage: 組み込みDuckDBによる高速ローカルストレージ
- 🎯 MCP Protocol: Model Context Protocol v1.0.4 準拠
- 🛡️ Law-Driven Engineering: fp-ts/io-ts によるType-safe & Property-based Testing
Benchmark Results
pce-memory's hybrid search pipeline is evaluated across three dimensions: search quality, scalability, and latency.
Search Quality (Ablation Study)
| Search Method | Recall@10 | nDCG | Latency |
|---|
| Text-only (BM25) | 50.0% | 50.0% | 34.7ms |
| Vector-only (Semantic) | 87.1% | 69.0% | 32.3ms |
| Hybrid (BM25 + Vector) | 91.7% | 81.0% | 32.6ms |
Hybrid search combines the precision of keyword matching with the semantic understanding of vector search, achieving +41.7pp recall over text-only and +4.6pp over vector-only.
Provenance-Aware Reranking
The g() reranking function leverages claim provenance quality to improve result ordering:
| Metric | Without Rerank | With Rerank | Delta |
|---|
| Recall@10 | 65.2% | 74.2% | +9.1pp |
| nDCG | 62.4% | 67.1% | +4.7pp |
Measured at 150 claims (golden + synthetic noise). Claims with richer provenance (actor, notes) are ranked higher.
Scalability
| Claims | P@5 | R@10 | MRR | Latency p50 |
|---|
| 15 | 18.2% | 91.7% | 83.0% | 38ms |
| 50 | 18.2% | 87.9% | 79.8% | 42ms |
| 100 | 17.3% | 87.9% | 78.9% | 40ms |
| 250 | 17.3% | 81.1% | 77.7% | 43ms |
| 500 | 15.5% | 72.0% | 68.6% | 45ms |
| 1,000 | 15.5% | 72.0% | 68.6% | 57ms |
| 5,000 | 12.7% | 60.6% | 61.4% | 60ms |
Latency Profile
| Operation | Time |
|---|
| Embedding model cold start | 177ms (once per session) |
| Embedding (cached) | 0.1ms |
| Search p50 (with rerank) | 37.5ms |
| Rerank overhead | 5.1ms |
All operations are well below the 100ms human perception threshold. Run pnpm benchmark to reproduce (requires apps/pce-memory/external/assay-kit submodule).
Project Structure
pce-memory/
├── apps/
│ └── pce-memory/ # MCP server implementation
├── packages/
│ ├── pce-boundary/ # Boundary validation & redaction
│ ├── pce-embeddings/ # Embedding provider abstraction
│ ├── pce-policy-schemas/ # YAML policy schemas
│ └── pce-sdk-ts/ # TypeScript client SDK
├── docs/ # Documentation
│ ├── pce-memory-vision.md
│ ├── core-types.md
│ ├── mcp-tools.md
│ ├── boundary-policy.md
│ └── activation-ranking.md
├── scripts/ # Development and local validation helpers
└── validation/ # Local validation tasks and result artifacts
Quick Start
Prerequisites
- Node.js: ≥ 22.18.0 (LTS)
- pnpm: ≥ 9.0.0
Installation
# Install dependencies
pnpm install
# Build all packages
pnpm build
# Run tests
pnpm test
# Run property-based tests
pnpm test:pbt
Running the MCP Server
# Start MCP server (stdio transport)
cd apps/pce-memory
pnpm dev
Development Workflow
# Watch mode (auto-reload on file changes)
pnpm dev
# Type checking
pnpm typecheck
# Linting
pnpm lint
pnpm lint:fix
# Formatting
pnpm format
pnpm format:check
# Clean build artifacts
pnpm clean
Local Architecture Validation with Ollama
The repository includes a documented local validation workflow for architecture experiments using Ollama and qwen3.5:122b-a10b.
# Interactive Codex against Ollama
pnpm local:codex
# Interactive Claude Code through Ollama launch integration
pnpm local:claude
# Canonical smoke task
pnpm local:validation:smoke
See docs/local-validation-ollama.md for machine assumptions, launch recipes, known limitations, and result capture conventions.
MCP Tools
PCE Memoryは以下のMCPツールを提供します：
