OpenClaw - AI assistant with screenpipe memory

OpenClaw is a self-hosted personal AI assistant that connects to your messaging apps (WhatsApp, Telegram, Discord, iMessage, etc.) and can take actions on your behalf.

With screenpipe, OpenClaw can recall what you've seen on screen, reference past conversations, and answer questions about your digital history.

same machine

If OpenClaw and screenpipe run on the same machine, setup is straightforward.

MCP (recommended)

Add screenpipe to your OpenClaw MCP config:

{
  "mcpServers": {
    "screenpipe": {
      "command": "npx",
      "args": ["-y", "screenpipe-mcp"]
    }
  }
}

Restart OpenClaw — it will now have access to your screen history, audio transcriptions, and more.

You can test the MCP server independently:

npx @modelcontextprotocol/inspector npx screenpipe-mcp

custom skill (alternative)

Create ~/openclaw/skills/screenpipe/skill.md:

---
name: screenpipe
description: Search screen recordings and audio transcriptions from the user's computer
tools:
  - Bash
---

# screenpipe skill

Query the user's screen history via the local API at http://localhost:3030.

## search content

```bash
curl -s "http://localhost:3030/search?q=QUERY&limit=20"
```

## get recent activity

```bash
curl -s "http://localhost:3030/search?limit=10&content_type=ocr"
```

Restart OpenClaw to load the skill.

different machines

If OpenClaw runs on a different machine (e.g., a VPS or home server) than screenpipe, there are two ways to connect them:

option 1: query screenpipe's REST API directly

If both machines are on the same network, OpenClaw can query screenpipe's API directly. Use a custom skill:

Create ~/openclaw/skills/screenpipe/skill.md:

---
name: screenpipe
description: Search screen recordings and audio transcriptions from the user's computer
tools:
  - Bash
---

# screenpipe skill

Query the user's screen history via their screenpipe REST API at http://SCREENPIPE_IP:3030.

## search content

```bash
curl -s "http://SCREENPIPE_IP:3030/search?q=QUERY&limit=20"
```

## filter by type

```bash
# screen content (accessibility + OCR)
curl -s "http://SCREENPIPE_IP:3030/search?q=QUERY&content_type=all"

# audio transcriptions
curl -s "http://SCREENPIPE_IP:3030/search?q=QUERY&content_type=audio"
```

## activity summary

```bash
curl -s "http://SCREENPIPE_IP:3030/activity-summary?start_time=2024-01-15T10:00:00Z&end_time=2024-01-15T18:00:00Z"
```

## list meetings

```bash
curl -s "http://SCREENPIPE_IP:3030/meetings?limit=20"
```

Replace SCREENPIPE_IP with the IP of the machine running screenpipe. If the machines aren't on the same network, use Tailscale to create a private network between them.

option 2: sync data to the OpenClaw machine

Use screenpipe's built-in cloud sync feature to synchronize your data to the machine running OpenClaw:

1. In the screenpipe app, go to Settings → Cloud and enable sync
2. On the OpenClaw machine, install screenpipe and log in with the same account
3. Your data will sync automatically — OpenClaw can then query localhost:3030 as if it were running on the same machine

available MCP tools

When connected via MCP (same machine setup), OpenClaw gets access to these tools:

The MCP server also provides resources (screenpipe://context for current time, screenpipe://guide for search strategy) and prompts (search-recent, find-in-app, meeting-notes).

example prompts

Once configured, message OpenClaw from any chat app:

• "what was I reading about yesterday afternoon?"
• "find the slack message from john about the deployment"
• "what code was I looking at in cursor this morning?"
• "summarize my meetings from last week"
• "what tabs did I have open when researching that bug?"
• "when did I last see the budget spreadsheet?"
• "what did I copy to clipboard recently?"
• "show me what buttons I clicked in Figma today"

troubleshooting

MCP not connecting?

• Test the server: npx @modelcontextprotocol/inspector npx screenpipe-mcp
• Check screenpipe is running: curl http://localhost:3030/health

remote machine can't reach screenpipe?

• Check Tailscale is connected: tailscale status
• Check SSH tunnel is up: curl http://localhost:3030/health on the remote
• Make sure screenpipe is running on your computer

no results from queries?

• Verify screenpipe is running: curl http://localhost:3030/health
• Ensure screenpipe has screen recording permissions