rmcp-memex

Rust MCP kernel for shared agent memory

One canonical memory surface for local MCP and multi-agent daemon mode.

rmcp-memex combines RAG, hybrid vector plus BM25 search, namespace isolation, and HTTP/SSE transport so multiple agents can use the same memory pool without fighting over LanceDB locks.

Download Releases Open Release Runbook
Quick install curl -LsSf https://raw.githubusercontent.com/VetCoders/rmcp-memex/main/install.sh | sh

Transport parity without drift

The stdio MCP server and HTTP/SSE daemon now route through the same core dispatch surface. Release prep includes parity coverage so transport bugs fail before they ship.

Built for real multi-agent use

Use stdio for local MCP hosts or switch to HTTP/SSE when several agents need one shared memory backend. The daemon mode removes the lock-contention pain of direct LanceDB access, and HTTP clients can bootstrap from one canonical /api/discovery surface.

Release-ready install path

GitHub Releases ship platform tarballs, SHA256 checksums, and a one-line installer that keeps the canonical rmcp-memex binary front and center while preserving a legacy rmcp_memex symlink for older automation.

Install and run

The shortest path from stranger to first query.

curl -LsSf https://raw.githubusercontent.com/VetCoders/rmcp-memex/main/install.sh | sh
rmcp-memex serve
rmcp-memex serve --http-port 6660 --http-only
Start here

README

Product overview, library usage, and MCP tool surface.

 Configuration

Provider and storage setup

Embedding providers, storage paths, and deployment-friendly defaults.

 HTTP/SSE

Daemon reference

Start with /api/discovery, then drill into browse, search, and write routes.

 Release ops

Runbook

Preflight checks, tagging, artifact verification, and launch follow-through.

Release contract

What shipping now means.

  • Canonical binary naming across Cargo, local signing pipeline, and installer
  • Locally built and signed release artifacts uploaded to GitHub Releases
  • Static launch page source for GitHub Pages with zero client-side JS dependency
  • Library-only and package smoke checks in CI, not just the default feature build