Loading ToolBench
A minimalist, production-ready Model Context Protocol server that gives Claude Desktop seamless access to your system clipboard with automatic history tracking
Clayboard provides 6 tools with clear naming (verb_noun pattern) and detailed descriptions (100-300 chars each). However, input schemas are minimal or absent for most tools. read_clipboard, write_clipboard, get_clipboard_history, get_clipboard_item, clear_clipboard_history, and get_platform_info have either empty schemas {} or single-parameter schemas with basic type info. Descriptions are verbose and helpful but lack conciseness (50-200 char baseline). No output schemas documented. Error handling is present in implementation but not surfaced in tool definitions. Security considerations (clipboard access) are not annotated.
TIME MACHINE: Clear the entire clipboard history. This permanently removes all stored clipboard history items. Use with caution - this action cannot be undone. Use this tool when: - User explicitly asks to "clear my clipboard history" - User wants to "reset" the clipboard history - User is concerned about privacy and wants to remove stored items - User says "forget everything I've copied"
TIME MACHINE: Retrieve the clipboard history (last 15 unique items). This is THE KEY TOOL for accessing things you copied minutes or hours ago. The history persists during the MCP server session and tracks both: - Things you copied from other apps (captured via read_clipboard) - Things the AI generated for you (captured via write_clipboard) Use this tool when: - User asks "what did I copy earlier?" - User references something they copied before (e.g., "the API key from before") - User wants to see their clipboard timeline - User asks to retrieve something from N items ago - Debugging or reviewing past clipboard operations
TIME MACHINE: Retrieve a specific item from clipboard history by index. Use this when you need to get a particular item from the history rather than viewing the entire history list. Use this tool when: - User asks for "the 3rd thing I copied" - User wants to retrieve a specific historical clipboard item - You need to access a particular entry from the history - User references "the API key from 5 items ago"
Get detailed platform information for debugging. Returns information about the operating system and hardware the MCP server is running on. Use this tool when: - Debugging clipboard access issues - User asks what platform they're on - Troubleshooting platform-specific clipboard problems
Output schemas not documented. Tools return strings or objects but LLMs cannot infer structure of history entries (timestamp, hash, preview fields) or error responses.
Descriptions exceed 200 chars and include implementation details ('TIME MACHINE FEATURE', platform-specific help text) that dilute core intent. Baseline for A+ tools is 50-200 chars.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint). write_clipboard and clear_clipboard_history are destructive/state-modifying but not marked. Agents cannot infer safety properties.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 61 | <=2025-11-25 | v2 |
Read the current content from the system clipboard. TIME MACHINE FEATURE: Automatically tracks clipboard changes in history. Each time you read, if the content is different from the last read, it gets added to the 15-item history buffer. Works on: macOS, Windows, Linux (with xclip/xsel installed) Use this tool when: - The user asks to "check my clipboard" - The user references "the error in my clipboard" - The user says "use what I just copied" - You need to analyze or process clipboard content
Write text content to the system clipboard. TIME MACHINE FEATURE: Automatically adds written content to history. This allows you to go back and retrieve things you generated earlier. Works on: macOS, Windows, Linux (with xclip/xsel installed) Use this tool when: - The user asks to "copy this to my clipboard" - The user wants to "save this for later" - You generate code/text the user wants to paste elsewhere - The user says "put this in my clipboard"
Error handling in implementation (try/catch, platform-specific messages) is not reflected in tool definitions. LLMs cannot plan recovery or understand failure modes from schema alone.
get_clipboard_history and get_clipboard_item lack pagination parameters (limit, offset) and return structure documentation. History is capped at 15 items but no max_items or total_count in response schema.