MCP Overview
Remb's MCP server gives your AI a shared context graph — memories, decisions, feature docs, and conversation history — that grows with every session.
What is MCP?
The Model Context Protocol (MCP) is an open standard for connecting AI assistants to external tools and data sources. Remb implements an MCP server that exposes 100 tools across 21 modules — memory, context, scanning, conversation tracking, plans, graph traversal, cross-project search, scratchpad, briefings, role contracts, skills, and more.
The key idea: your project's context is not a snapshot of its source files — it's a graph that your AI builds and curates over every session. Memories capture why decisions were made. Feature notes document what each part does. Conversation logs record what was accomplished. Scanning adds structural breadth — but it's optional and additive, not the foundation.
Setup
Via CLI (recommended)
The CLI includes a built-in MCP proxy that connects via stdio:
remb serveThis proxies JSON-RPC messages between stdio and the Remb HTTP API. No tool definitions are hardcoded — the CLI dynamically forwards everything the server supports.
Direct HTTP
You can also connect directly to the HTTP MCP endpoint:
POST https://www.useremb.com/api/mcp
Authorization: Bearer rmb_your_api_key
Content-Type: application/json
{ "jsonrpc": "2.0", "method": "tools/list", "id": 1 }IDE Configuration
VS Code (GitHub Copilot)
{
"servers": {
"remb": {
"command": "remb",
"args": ["serve"],
"env": {}
}
}
}Claude Code
{
"mcpServers": {
"remb": {
"command": "remb",
"args": ["serve"]
}
}
}Cursor
{
"mcpServers": {
"remb": {
"command": "remb",
"args": ["serve"]
}
}
}How It Works
- Your IDE starts the MCP server via
remb serve - The AI assistant discovers available tools via
tools/list - When the AI needs context, it calls tools like
remb__memory_load_context - The CLI proxies the request to the Remb API and returns the result
- All data is persisted server-side across sessions, IDEs, and machines
Tool Budget
100 tools is too many to keep loaded at once for a focused task. Pass _meta.tool_budget on tools/list to get the top-K most relevant tools for the current task. Optionally pass _meta.context_hint with a short description of what you’re working on to score relevance. Always-included tools (session_start, memory_load_context, tool_discover) are guaranteed even under tight budgets.
{
"method": "tools/list",
"params": {
"_meta": {
"tool_budget": 20,
"context_hint": "refactor authentication"
}
}
}Tool Categories
Memory (11 tools)
Create, search, update, promote, and manage persistent memories. Includes memory_get for JIT body fetching and the 'example' category for canonical worked examples.
Conversations (3 tools)
Log work, load history (with compact mode for long-running agents), semantic search. Domain-aware summariser supports coding / research / support / ops / general agents.
Projects (6 tools)
CRUD for projects, including project_init_local for lightweight no-repo projects.
Context (4 tools)
Save, retrieve, and bundle project context. session_start returns XML-structured output with context_budget hint and lean mode for JIT loading.
Scans (4 tools)
Trigger scans, check progress, analyze diffs.
Plans (6 tools)
Manage multi-phase plans with IDE sync.
Graph (4 tools)
Traverse knowledge graphs and code dependency graphs.
Features (4 tools)
List, inspect, update, and delete features.
Cross-Project (2 tools)
Search patterns across all projects.
Previews (5 tools)
Deploy and manage live preview environments.
Repo (2 tools)
Read files and browse trees from GitHub.
Audit (3 tools)
Trigger and inspect AI code audits.
Action Log (5 tools)
Multi-agent coordination — claim, log, check actions.
Sessions (9 tools)
Checkpoints, file history, timelines.
Personal (12 tools)
Personal-memory primitives — focus, blockers, lessons, recurring problems, people, decision conflicts, weekly brief.
Profile (3 tools)
Cross-project user profile — name, role, stack, never-do.
Skills (6 tools)
Procedural memory — search, load, record outcomes, self-heal reusable skills.
Scratchpad (4 tools)
Session-scoped file-based context offload — keep large outputs out of the prompt.
Briefing (2 tools)
Typed session-handoff payloads (focus, decisions, blockers, files) for next session.
Telemetry (2 tools)
Memory feedback (success/rejection/undo) and quarantine candidates for context poisoning.
Roles (3 tools)
Multi-agent role contracts — typed planner → implementer → reviewer handoffs.
Full reference
See the Tools Reference for the complete list of all 100 tools with parameters and descriptions.