open-index/open-npm huggingface dataset:
npm package: @jcyamacho/agent-bridge
Description: A filesystem-based MCP server that enables room-first collaboration between local AI agents across repositories.
Latest version: 0.0.7

# agent-bridge

A filesystem-based MCP server that enables room-first collaboration
between local AI agents across repositories.

Each local MCP client session runs its own stdio MCP server instance.
All instances read/write to a shared directory (`~/.agent-bridge/`). No
central process - the filesystem is the message bus.

## Development Setup

```bash
bun install
bun run build
```

## Usage

Register the MCP server in each local agent session with a unique
`--peer-id`.

The examples below use Claude Code CLI, but the same server works with
other local MCP-capable agents (for example, Codex) using their MCP
server registration flow.

```bash
# Frontend session
claude mcp add agent-bridge -- npx -y @jcyamacho/agent-bridge \
  --peer-id frontend --name "Frontend"

# Backend session
claude mcp add agent-bridge -- npx -y @jcyamacho/agent-bridge \
  --peer-id backend --name "Backend API"
```

### CLI Arguments

| Argument | Required | Description |
| --- | --- | --- |
| `--peer-id` | Yes | Unique identifier for this peer |
| `--name` | No | Display name (defaults to peer-id) |
| `--project` | No | Project path (defaults to cwd) |
| `--bridge-dir` | No | Shared directory (defaults to `~/.agent-bridge`) |

## Tools

| Tool | Description |
| --- | --- |
| `list_peers` | List other registered peers |
| `open_feature_room` | Create a feature room |
| `close_feature_room` | Close a feature room (read-only) |
| `list_feature_rooms` | List open feature rooms (or include closed) |
| `post_feature_message` | Post a typed feature message (`update`, `question`, `decision`, `blocker`) |
| `read_feature_messages` | Read feature room messages |
| `put_feature_context` | Write a context document in a feature room |
| `get_feature_context` | Read a context document from a feature room |
| `list_feature_context_keys` | List context keys in a feature room |

Feature-room tools use `room_id` as the stable room identifier in their
input payloads. Closed rooms are read-only.

Peer registration is automatic on startup and heartbeat; there is no
manual peer-upsert tool.

## Development

```bash
bun test          # Run tests
bun run build     # Build for Node.js
```
npm package: @jcyamacho/agent-memory
Description: Persistent memory for MCP-powered coding agents.
Latest version: 0.1.0

# agent-memory

Persistent memory for MCP-powered coding agents.

`agent-memory` is a stdio MCP server that gives your LLM durable memory backed
by SQLite. It helps your agent remember preferences, project context, and prior
decisions across sessions.

It exposes four tools:

- `remember` -> save facts, decisions, preferences, and project context
- `review` -> load workspace and global memories sorted by most recently updated
- `revise` -> update an existing memory when it becomes outdated
- `forget` -> delete a memory that is no longer relevant

## Quick Start

Claude CLI:

```bash
claude mcp add --scope user memory -- npx -y @jcyamacho/agent-memory
```

Codex CLI:

```bash
codex mcp add memory -- npx -y @jcyamacho/agent-memory
```

OpenCode:

```jsonc
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "memory": {
      "type": "local",
      "command": ["npx", "-y", "@jcyamacho/agent-memory"]
    }
  }
}
```

## Optional LLM Instructions

Optional LLM instructions to reinforce the MCP's built-in guidance. The server
instructions and tool descriptions already cover most behavior -- this prompt
targets the habits models most commonly miss:

```md
## Agent Memory

- Use `memory_review` at conversation start to load workspace memories into
  context. During the session, use `memory_remember`, `memory_revise`, and
  `memory_forget` to keep memories accurate.
- Pass `workspace` on `memory_remember` for project-scoped memory. Omit it
  only for facts that apply across projects.
- Do not store secrets, temporary task state, or facts obvious from current
  code or git history.
```

## Web UI

Browse, edit, and delete memories in a local web interface:

```bash
npx -y @jcyamacho/agent-memory@latest --ui
```

Opens at `http://localhost:6580`. Use `--port` to change:

```bash
npx -y @jcyamacho/agent-memory@latest --ui --port 9090
```

The web UI uses the same database as the MCP server.

## How Review Works

`review` requires a `workspace` and returns memories saved in that workspace
plus global memories (saved without a workspace), sorted by most recently
updated. Results are paginated -- pass `page` to load older memories.

When you save a memory from a git worktree, `agent-memory` stores the main repo
root as the workspace. `review` applies the same normalization to incoming
workspace queries so linked worktrees still match repo-scoped memories exactly.

## Configuration

### Database Location

By default, the SQLite database is created at:

```text
~/.config/agent-memory/memory.db
```

Override it with:

```bash
AGENT_MEMORY_DB_PATH=/absolute/path/to/memory.db
```

Set `AGENT_MEMORY_DB_PATH` when you want to:

- keep memory in a project-specific location
- share a memory DB across multiple clients
- store the DB somewhere easier to back up or inspect

Schema changes are migrated automatically, including workspace normalization for
existing git worktree memories when the original path can still be resolved.

## License

MIT