What is the key difference between Screenpipe and Threadctx MCP?

Screenpipe belongs to the Knowledge & Memory category with local stdio execution, while Threadctx MCP belongs to the Knowledge & Memory category with local stdio execution.

How do I install Screenpipe or Threadctx MCP in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Screenpipe and Threadctx MCP free or paid?

Screenpipe operates under a Freemium model (API Key required). Threadctx MCP operates under a Freemium model (API Key required).

Which MCP server has more tools and community activity?

Screenpipe lists 6 tools with 1 views and 21,583 GitHub stars. Threadctx MCP lists 2 tools with 2 views and 1 GitHub stars.

Can I use both Screenpipe and Threadctx MCP together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Screenpipe vs Threadctx MCP

In-depth architectural comparison of the Screenpipe and Threadctx MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Screenpipe

Knowledge & Memory · Local stdio

Quality: 69/100 (Great) | Auth: API Key required

Threadctx MCP

Knowledge & Memory · Local stdio

Quality: 57/100 (Good) | Auth: API Key required

Verdict Summary: Choose Screenpipe if you need specialized Knowledge & Memory tools running via a local process. Choose Threadctx MCP if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Screenpipe when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: SCREENPIPE_LOCAL_API_KEY.
Primary tools included: search_content, export-video, list-meetings.

Explore Screenpipe Details

Choose Threadctx MCP when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Freemium).
You have access to required keys: THREADCTX_API_KEY, THREADCTX_MODE, THREADCTX_NO_AUTO_RULES.
Primary tools included: memory_write, memory_query.

Feature & Specification Comparison

Specification	Screenpipe Knowledge & Memory	Threadctx MCP threadctx-dev Knowledge & Memory
Summary	Local-first workflow memory for AI agents. screenpipe lets MCP clients search selected screen, audio, app, and meeting context and turn real work into cited notes, SOPs, workflow reports, and automation candidates.	Shared team memory for AI coding agents. Decisions, fixes, and gotchas persist per repo and are shared across Claude Code, Cursor, and any MCP client — what one teammate's agent learns, everyone's agents remember. Local-first, zero-dependency. npx -y threadctx-mcp
Category & Scope

Tools & Capabilities Breakdown

Screenpipe Tools (6)

search_content

Search screen recordings, OCR text, and audio transcriptions

export-video

Export video clips from captured screen history

list-meetings

List and inspect recorded meeting events

activity-summary

Generate summaries of computer activity over a time window

search-elements

Search captured UI elements and accessibility tree items

frame-context

Retrieve frame context and OCR details for specific timestamps

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Screenpipe Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "screenpipe": {
      "command": "npx",
      "args": [
        "-y",
        "screenpipe-mcp@latest"
      ],
      "env": {
        "SCREENPIPE_LOCAL_API_KEY": "YOUR_SCREENPIPE_LOCAL_API_KEY_HERE"
      }
    }
  }
}

Threadctx MCP Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "threadctx-dev-threadctx-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "threadctx-mcp"
      ],
      "env": {
        "THREADCTX_API_KEY": "YOUR_THREADCTX_API_KEY_HERE",
        "THREADCTX_MODE": "YOUR_THREADCTX_MODE_HERE",
        "THREADCTX_NO_AUTO_RULES": "YOUR_THREADCTX_NO_AUTO_RULES_HERE"
      }
    }
  }
}

Frequently Asked Questions

Screenpipe is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Threadctx MCP belongs to Knowledge & Memory using local stdio subprocess. Select Screenpipe when you need capabilities focused on knowledge & memory and Threadctx MCP when you require tools for knowledge & memory.

More alternatives to Screenpipe More alternatives to Threadctx MCP Knowledge & Memory category hub