Skip to main content
An assistant needs an actual connection to retrieve Screenpipe history. Pasting a prompt into a separate chat does not grant access to your computer. Connecting a model account to Screenpipe and connecting an assistant to Screenpipe’s tools are different directions.

Start here

Use the MCP setup guide for a supported local client such as Claude Desktop, Claude Code, or Codex. Keep Screenpipe running on the recording computer and verify the connection with a narrow recent search.

Copy this prompt

Use this in Screenpipe chat or an assistant with the required connections. Replace the brackets with your details. If the assistant lacks access, provide a reviewed excerpt; a prompt alone does not connect it to your history.

Check the result

Ask the assistant to quote one harmless test phrase and give its source time. A confident summary without a tool result is not a connection test.
A remote service cannot reach your computer’s localhost just because you put that address in a prompt. Do not expose the local API publicly as a shortcut. Use the documented client connection and keep authentication credentials out of prompts.For a chat that has no connection, export a short reviewed note containing the time range, relevant facts, source labels, and open questions. Say explicitly that the assistant should answer only from that excerpt. This works as a portable context handoff without claiming direct access.

Continue

MCP server · ChatGPT · agent memory workflow