The MCP server that ships as one binary.

Drop-in for Claude Desktop, Zed, Cursor, and every MCP-native client. Zero Node, zero Python, zero runtime deps. Statically linked, signed, auto-updating.

Join beta → See install

Install

One command. One binary.

The installer detects your OS, fetches the right binary, verifies the signature, and registers it with any MCP-native client it finds.

# Install the REM MCP server (macOS, Linux, Windows/WSL)
curl -fsSL https://remlabs.ai/install/mcp | sh

# Apple Silicon
curl -fsSL https://remlabs.ai/install/mcp-darwin-arm64 -o /usr/local/bin/rem-mcp
chmod +x /usr/local/bin/rem-mcp

# Intel
curl -fsSL https://remlabs.ai/install/mcp-darwin-amd64 -o /usr/local/bin/rem-mcp
chmod +x /usr/local/bin/rem-mcp

# Or via Homebrew
brew install remlabs/tap/mcp

# x86_64
curl -fsSL https://remlabs.ai/install/mcp-linux-amd64 -o /usr/local/bin/rem-mcp
chmod +x /usr/local/bin/rem-mcp

# arm64
curl -fsSL https://remlabs.ai/install/mcp-linux-arm64 -o /usr/local/bin/rem-mcp
chmod +x /usr/local/bin/rem-mcp

# Verify signature
rem-mcp verify --release latest

# PowerShell
Invoke-WebRequest https://remlabs.ai/install/mcp-windows-amd64.exe -OutFile rem-mcp.exe

# Or via winget
winget install RemLabs.MCP

# Or via scoop
scoop bucket add remlabs https://github.com/RemLabs/scoop-bucket
scoop install rem-mcp

Claude Desktop

Open ~/Library/Application Support/Claude/claude_desktop_config.json on macOS — or the equivalent on Windows/Linux — and drop this in.

{
  "mcpServers": {
    "rem": {
      "command": "rem-mcp",
      "args": ["serve", "--stdio"],
      "env": {
        "REM_API_KEY": "sk_live_…",
        "REM_NAMESPACE": "default"
      }
    }
  }
}

Restart Claude Desktop. The tools appear automatically in the tool picker.

What it exposes

Eight tools. Zero glue code.

Every MCP-native client sees the same primitives. No per-client adapters. No re-plumbing.

remember

Write a memory with optional namespace, tags, and source metadata.

recall

Semantic + keyword hybrid search. Returns ranked memories with confidence scores.

forget

Delete by id, tag, or filter. Tombstoned, reversible for 30 days.

ask

Natural-language query over your full graph. Cited, typed, and streamable.

dream

Trigger Dream Engine consolidation. Nine strategies, one call.

graph

Traverse entities and relations. Cypher-style queries, JSON-shaped output.

channel

Subscribe to memory events and real-time streams for collaborative agents.

federate

Share scoped memory with another REM namespace over the A2A protocol.

FAQ

The short list.

Why a single binary and not a Node package?

Because npx cold-start is a tax. Single-binary means no runtime to install, no version drift, no native-module rebuild loop. It starts in under 40ms and ships signed builds for every major platform.

Which clients does it work with?

Claude Desktop, Zed, Cursor, Continue, and any MCP-native client that speaks stdio or websocket transport. If a client implements MCP, the REM binary just works.

Is my data sent to REM Labs?

Only if you configure the cloud backend with REM_API_KEY. The binary also runs fully local against a SQLite-backed self-hosted store — same tools, same protocol, your data never leaves the machine.

When does this ship?

Public beta end of Q3 2026. GA shortly after. Early access is open now — join the waitlist to get the signed pre-release build.

Commitment

This page flips from Building to Shipped the same day the binary ships — no vaporware, no surprise pivots. Track progress on the roadmap, see changes in the changelog, or drop into Discord to steer what lands first.