setup
VS Code
- install Continue from the VS Code marketplace
- open Continue settings
- edit
~/.continue/config.json:
- restart VS Code
JetBrains
- install Continue from JetBrains marketplace
- open Continue settings
- add the same MCP configuration
- restart the IDE
usage
once configured, Continue can access your screen history:example workflows
code with context:available tools
via MCP, Continue gets access to:| tool | description |
|---|---|
search-content | search screen text (accessibility-first, OCR fallback), audio transcriptions, and input |
activity-summary | lightweight overview of app usage, speakers, and recent texts for a time range |
search-elements | search structured UI elements from the accessibility tree |
frame-context | full accessibility tree, URLs, and text for a specific frame |
list-meetings | list detected meetings with duration, app, and attendees |
export-video | export screen recordings as MP4 for a time range |
requirements
- screenpipe running on localhost:3030
- Continue extension in VS Code or JetBrains
- Node.js >= 18.0.0
troubleshooting
MCP server not appearing in Continue?-
check screenpipe is running:
you should see
{"status":"healthy"} -
verify the config file location:
- VS Code:
~/.continue/config.json(check it exists and is valid JSON) - JetBrains: open Continue settings and confirm the MCP config is saved
- VS Code:
- restart the IDE completely (not just the Continue extension)
- if the server still doesn’t appear, remove and re-add it in Continue settings
-
verify screenpipe has data:
if empty, screenpipe hasn’t recorded anything yet — let it run for a minute and try again
- check screen recording permissions are granted (System Settings on macOS)
- confirm you’re querying a time range with recorded data
-
check the screenpipe process is still running (it may have crashed):
-
check screenpipe logs:
- macOS/Linux:
~/.screenpipe/screenpipe.log - Windows: check event viewer or
%APPDATA%\screenpipe\logs
- macOS/Linux:
-
restart screenpipe if needed:
- reload the Continue extension: use VS Code’s Command Palette (Cmd+Shift+P) → “Reload Window”
- verify
config.jsonis valid JSON (check for trailing commas) - ensure Node.js >= 18.0.0:
node --version