VS Code (GitHub Copilot) Persistent Memory

GitHub Copilot Chat in VS Code supports MCP servers natively — no extension needed beyond Copilot itself. Wire it to Rohrpost and Copilot gets a knowledge base of your project's decisions and history, shared with any other MCP-speaking tool you use alongside it.

Download the binary

Log in to app.rohrpost.ioand grab rohrpost-mcp for your platform from the Downloads tab, or build it from source:

git clone https://codeberg.org/ftieben/rohrpost.io
cd rohrpost.io
cargo build --release --bin rohrpost-mcp
# binary is at target/release/rohrpost-mcp

chmod +x rohrpost-mcp-*
mv rohrpost-mcp-* ~/.local/bin/rohrpost-mcp

Configure

Create .vscode/mcp.json in your project (note the VS Code schema differs slightly from Claude/Cursor's — it uses "servers" and an explicit"type"):

{
  "servers": {
    "rohrpost": {
      "type": "stdio",
      "command": "/path/to/rohrpost-mcp",
      "env": {
        "ROHRPOST_GATEWAY_URL": "https://app.rohrpost.io",
        "ROHRPOST_API_KEY": "rp_your_api_key"
      }
    }
  }
}

Self-hosting? Point ROHRPOST_GATEWAY_URL at http://localhost:7878(or your gateway's address) instead. Generate an API key from the API Keystab of your admin panel.

VS Code will prompt you to start the server the first time it sees the config — accept it, or start it manually from the MCP indicator in the Chat panel.

Verify it's working

Open Copilot Chat, click the tools icon, and confirm rohrpost is listed with its tools enabled. Ask it to remember something project-specific, start a new chat, and ask about it again — a working connection recalls the fact instead of asking you to repeat it.

Troubleshooting

Server doesn't start

Check the Output panel (select "GitHub Copilot Chat" or "MCP" from the dropdown) for the startup error. The most common cause is a relative or ~-prefixedcommand path — VS Code needs an absolute path to the binary.

Tools icon doesn't show Rohrpost

Confirm you're using a recent VS Code version with MCP support enabled in Copilot settings, and that .vscode/mcp.json is valid JSON — a stray comma silently breaks the whole file with no visible error in the editor.

Workspace vs. user-level config

.vscode/mcp.json in the workspace root scopes Rohrpost to that project — the recommended setup, since it lets you point different projects at different tenants. For a server available in every workspace, add the same block to your VS Code user settings instead (Command Palette → "Preferences: Open User Settings (JSON)").