npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

agents-memory-sidecar

v0.1.1

Published

Local-first shared memory sidecar for MCP-capable AI agents.

Readme

Agents Memory Sidecar

Local-first shared memory for MCP-capable AI agents.

Agents Memory Sidecar lets tools such as Codex, Claude Code, Grok, agy, Pi, and other MCP clients share operational memory through one local sidecar. It is designed for coding agents that need to search prior context before changing a project and store durable non-secret facts after work is validated.

Agent CLI -> stdio MCP wrapper -> localhost HTTP sidecar -> PostgreSQL + pgvector

The HTTP server is intended to listen on 127.0.0.1 only. Do not expose it directly to the public internet.

Features

  • MCP tools for searching, reading, and writing shared memory
  • Project context storage for stable paths, services, ports, and conventions
  • Short-lived agent observations with TTL
  • HTTP sidecar with bearer-token authentication
  • Actor identity derived from token registry, not model-provided fields
  • PostgreSQL persistence with pgvector-backed semantic and hybrid search
  • Secret rejection for common token/private-key patterns
  • Audit events for writes, permission denials, unauthorized calls, and pruning
  • Fake JSON store for local development and smoke tests

MCP Tools

  • memory_search
  • memory_get
  • project_context_get
  • memory_add
  • agent_observation_add
  • project_context_set (admin-only)

Search Modes

Search defaults to keyword/full-text mode. PostgreSQL deployments can enable semantic or hybrid mode after backfilling memory_embeddings; see Configuration.

Quick Start

npm install
npm run build
npm run smoke
npm run http:smoke
npm run http:bridge-smoke

Install from GitHub:

git clone https://github.com/zenbordercom/agents-memory-sidecar.git
cd agents-memory-sidecar
npm install
npm run build

Install globally from the GitHub release tag:

npm install -g agents-memory-sidecar

Or install from the GitHub release tag:

npm install -g github:zenbordercom/agents-memory-sidecar#v0.1.1

Or install the release tarball:

npm install -g https://github.com/zenbordercom/agents-memory-sidecar/releases/download/v0.1.1/agents-memory-sidecar-0.1.1.tgz

The CLI entry points are:

agents-memory --help
agents-memory-mcp
agents-memory-http

Run the stdio MCP wrapper with the fake store:

AGENT_MEMORY_AGENT_ID=local-agent \
AGENT_MEMORY_RUNTIME=local \
AGENT_MEMORY_ROLE=writer \
AGENT_MEMORY_PROJECTS='*' \
npm run dev

Run the HTTP sidecar locally with PostgreSQL after configuring the database:

AGENT_MEMORY_BACKEND=postgres \
AGENT_MEMORY_HTTP_HOST=127.0.0.1 \
AGENT_MEMORY_HTTP_PORT=18790 \
npm run http:dev

Use the fallback CLI:

node dist/cli.js memory_search '{"tenant":"default","project":"demo-app","query":"deployment","limit":5}'

PostgreSQL

Create a PostgreSQL database and install migrations:

createdb agents_memory
AGENT_MEMORY_BACKEND=postgres \
PGDATABASE=agents_memory \
npm run db:migrate

For production, use a restricted application role and store connection settings outside the repository. See Configuration.

Agent Setup

The recommended client pattern is:

  1. Store the bearer token in a private env file.
  2. Create a small launcher script that sources that env file.
  3. Point the agent's MCP config at the launcher.

See Agent Integrations and integrations/*/README.md.

Security Defaults

  • Bind the HTTP sidecar to 127.0.0.1.
  • Keep full bearer tokens out of Git, chat, logs, and docs.
  • Use separate tokens per agent.
  • Give normal agents writer, not admin.
  • Store stable facts, not secrets or raw .env files.
  • Treat model-provided actor fields as untrusted.

See Security Model.

Production Operations

Optional scripts and systemd unit examples are included for local Linux deployments. Review paths, users, groups, database roles, and backup passphrase handling before use.

sudo scripts/install-local.sh

See Operations and Backup And Restore.

Limitations

  • Search defaults to keyword/full-text mode. Semantic and hybrid search require stored embeddings and an embedding model or explicit query embedding.
  • The project does not replace an agent's internal conversation memory.
  • The sidecar is local-first and not designed as a public multi-tenant SaaS API.
  • Fresh install automation is intentionally minimal in this version.

License

Apache-2.0.