Paste vs Clipboard History MCP

In-depth architectural comparison of the Paste and Clipboard History 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.

Which MCP Server Should You Choose?

P

Choose Paste when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Paste Details

Choose Clipboard History MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Clipboard History MCP Details

Feature & Specification Comparison

Specification	P Paste Developer Tools	Clipboard History MCP Developer Tools
Summary	Give AI tools access to your Mac clipboard history and pinboards from Paste. Runs locally.	Your clipboard, but Claude can read it. Type-classified, secret-encrypted. macOS + Linux.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

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).

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

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

Related MCP Server Comparisons