VS Code MCP Setup

Use VS Code's native MCP support with the Remb CLI. The Remb marketplace extension and Desktop Agent are paused for now.

Extension paused

The Remb VS Code marketplace extension and Desktop Agent are paused while the MCP path is hardened. New VS Code projects should use the native MCP configuration below with remb serve.

CLI Installation

Ensure the Remb CLI is installed and you're authenticated:

brew tap samie105/remb && brew install remb
remb login

Native MCP

Configure the Remb MCP server in your workspace:

.vscode/mcp.json

{
  "servers": {
    "remb": {
      "command": "remb",
      "args": ["serve"],
      "env": {}
    }
  }
}

Once configured, GitHub Copilot starts with 12 core Remb tools (prefixed with remb__) and can discover from 93 active tools when a workflow needs more depth.

Skills

Skills are reusable instruction packs that teach Copilot how to use Remb effectively:

# Assign a skill to the current project
remb skills add remb-context

# Or several at once
remb skills add remb-context && remb skills add remb-memory && remb skills add remb-scan

Assigned skills are compiled into the instructions block injected at the start of every MCP session, so Copilot picks them up automatically without any local files to commit.

Copilot Instructions

The remb init command generates a .github/copilot-instructions.md file with mandatory session protocol:

Session start: call remb__session_start
During work: log completed tasks as conversation entries
Session end: save summary for next session pickup
Discovery: save important patterns and decisions as memories

Extension Status

The older Remb extension and Desktop Agent path is not the launch path. Keep existing installs only if you already depend on them, and use the MCP tools directly for new projects:

remb__session_start loads the current project context.
remb__tool_discover finds specialized tools only when needed.
remb__conversation_log records completed work for future sessions.
remb__memory_create saves durable decisions and patterns.

No generated file required

You do not need remb-context.md or a background daemon for the supported VS Code path. Copilot talks to Remb through MCP.

Available Skills

remb-setup

Base configuration with session protocol and tool references.

remb-context

How to save and retrieve feature-level context entries.

remb-memory

Memory management — tiers, categories, promotion, search.

remb-scan

Scanning workflow — local scans, cloud push, scan status.

remb-import

Importing context from existing documentation files.

remb-cross-project

Cross-project search and pattern reuse.

Usage

Once configured, Copilot will automatically:

Load project context at session start
Use memories for coding decisions
Log significant work as conversation entries
Save discovered patterns as new memories

Trigger manually

You can also ask Copilot directly: "Load my Remb context" or "Save this as a memory" — the skills teach it how to respond.