Clipboard History MCP server
io.github.d-khomenko/clipboard-history-mcp·v0.5.0-alpha.0·19 starsYour clipboard, but Claude can read it. Type-classified, secret-encrypted. macOS + Linux.
19 stars
Reviews
Write oneNobody has reviewed Clipboard History MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Clipboard History MCP tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 57 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Clipboard History MCP compares
Against every graded Security MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 80/100
- higher than 64% of 915 Security servers
- GitHub stars
- 19
- more than 93% of 587 Security servers
Install Clipboard History MCP in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the Clipboard History MCP repository's README, as published. We do not edit it. Read it on GitHub
clipboard-history-mcp
Your clipboard, but Claude can read it. Type-classified, secret-encrypted, macOS-native.
flowchart LR
U[You ⌘C something] --> D[Rust daemon<br/>launchd-managed]
D -->|classify + encrypt| DB[(SQLite + FTS5)]
D -. non-secret clips .-> O[Obsidian vault<br/>optional]
C[Claude] -->|MCP stdio| M[15 tools]
M --> DB
M -->|Touch ID| V[Vault<br/>AES-256-GCM]One Rust binary. No Node.js, no Swift toolchain, no other apps to install. Drag a .mcpb into Claude Desktop, done.
One process · ~1 mW idle · ~24 MB RAM. Replaces the clipboard-manager + secret-scanner + Obsidian-export stack a typical setup needs three or four background apps to assemble.
What this gets you
You're working in Claude. You've copied 47 things today — URLs, JSON snippets, an OpenAI key from a dashboard, a SQL query from your DB tool, half a Stripe webhook payload. Now Claude can use any of them:
You: "Find that API key I copied from the OpenAI dashboard yesterday"
Claude: Found 1 secret matching "OpenAI" — kind: openai_api_key,
source: Safari, copied 14h ago. Last 4 chars: ab12.
To reveal, call unlock_secret(id=23, reason="...").
You: "Give me all the GitHub URLs I copied"
Claude: Returns 12 unique GitHub URLs deduplicated by repo,
ranked by how often you pasted them back.
You: "There was a Stripe JSON config in the buffer — restore it to my clipboard"
Claude: Found, restoring. ✓ ready to ⌘V.
You: "What code did I copy from ChatGPT over the last 2 hours?"
Claude: 3 Python snippets, 1 SQL query, 1 shell command.
You: "Show me the screenshot I just copied"
Claude: Returns a 142×120 PNG, mime image/png, captured from Preview 2 minutes ago.Search uses SQLite FTS5 + window-title indexing — you find clips by where you copied them, not just by content.
Why nothing else does this
The other ~20 clipboard-mcp repos on GitHub only read the current clipboard. None capture history.
Install
One-click — Claude Desktop
- Download clipboard-history-mcp.mcpb from the latest release.
- Claude Desktop → Settings → Extensions → "Install from file" → pick the .mcpb.
- Restart Claude Desktop. Ask: "List my recent clipboard URLs."
Manual — Claude Code / CLI
curl -L https://github.com/d-khomenko/clipboard-history-mcp/releases/latest/download/clipboard-history-mcp.mcpb \
-o clipboard-history-mcp.mcpb
unzip clipboard-history-mcp.mcpb -d ext
# register MCP
claude mcp add -s user clipboard-history -- ./ext/server/clipboard-history-mcp serve
# install background daemon (captures even when Claude is closed)
./ext/server/clipboard-history-mcp installQuick install — cargo install
If you have a Rust toolchain (Rust 1.95+) and use Claude Code:
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Clipboard History MCP: common questions
- Is Clipboard History MCP server safe?
- Mostly: it is graded B (80/100). Read the Clipboard History MCP safety report
- Does Clipboard History MCP need an API key?
- No secret keys are declared. It reads 6 settings from the environment.
- Is Clipboard History MCP maintained?
- The last commit was 95 days ago (2026-08-01). The latest release is v0.5.0-alpha.0.
- What can I use instead of Clipboard History MCP?
- Servers from other publishers that do the same job: PyMemoryEditor MCP server, Skylos MCP server and chunk-invariance MCP server.
- How does Clipboard History MCP compare with other Security MCP servers?
- safety score 80/100 (higher than 64% of 915 Security servers); github stars 19 (more than 93% of 587 Security servers). Full comparison.
Alternatives to Clipboard History MCP
Same job from other publishers: the closest match first, then the best rated.
- PyMemoryEditorRead, write and scan process memory, Cheat Engine style, on Windows, Linux and macOS.not reviewedEstablishedA
- SkylosDead code, security, secrets detection and code quality for Python, TypeScript, Go.not reviewedEstablishedC
- chunk-invarianceChecks whether your streaming redactor leaks a secret split across chunks; writes a pytest for it.not reviewedGrowingA
- Dechonet30 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.not reviewedGrowingA
- SafeWeaveSecurity scanner for AI-written code: SAST, secrets, dependencies, IaC, containers and DAST.not reviewedGrowingC