mcp-clipboard
Related Servers
Alternatives to mcp-clipboard
- AlicenseAqualityFmaintenanceProvides tools for reading and writing system clipboard data across Linux, macOS, Windows, and WSL platforms.2AGPL 3.0
Related Servers
- AlicenseAqualityCmaintenanceMCP server that gives Claude Code reliable access to clipboard images and screenshots, fixing broken paste in iTerm2.23MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that gives Claude and other AI assistants access to your Maccy clipboard history, allowing search, retrieval, and management of copied content through natural conversation.9MIT
- FlicenseAqualityDmaintenanceA Windows-native MCP server that enables users to paste images, Excel tables, rich text, and plain text directly into Claude via a dedicated popup interface. It supports multi-item management and format conversion to streamline sharing complex clipboard data with the model.1-
- AlicenseNot gradedqualityDmaintenanceA simple MCP server that allows AI assistants to read from and write to the system clipboard.3MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that gives AI agents access to your Maus clipboard on macOS, enabling them to write clean text into history, search, and manage clipboard items locally.4 npmMIT
- FlicenseNot gradedqualityDmaintenanceA local MCP server providing text utilities, math functions, and a persistent todo list, enabling task automation via natural language in Claude Desktop.-
TDQS
Scored across 7 tools
The read/write split is clear, and copy vs copy_image vs copy_markdown are well distinguished by content type. clipboard_paste vs clipboard_read_raw have the most overlap, but descriptions explicitly frame read_raw as a diagnostic-only escape hatch, reducing confusion.
Nearly all tools follow a clean clipboard_<verb>_<noun> pattern (paste, read_raw, list_formats, copy, copy_image, copy_markdown). clipboard_version is a minor deviation since it drops the verb, but it remains readable and predictable.
Seven tools is a well-scoped set for clipboard operations. Most earn their place, though clipboard_version is borderline trivial and could arguably be folded into diagnostics.
The surface covers the full lifecycle: read (paste/raw/list_formats), write text, write rich text/markdown, write images, plus version introspection. No obvious gaps in clipboard read/write workflows.