Clipboard MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_clipboardA | Read the current text content from the system clipboard. Returns the text currently stored in the clipboard. If the clipboard is empty or contains non-text data, an empty string is returned. |
| write_clipboardA | Write text content to the system clipboard. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have perfectly distinct purposes: one reads from the clipboard and the other writes to it. There is no overlap or ambiguity in their functions, making it impossible for an agent to confuse them.
Both tools follow a consistent verb_noun pattern (read_clipboard, write_clipboard) with clear action-object naming. The snake_case style is uniform throughout, making the tools predictable and easy to understand.
With only two tools, the server feels minimal but functional for basic clipboard operations. While it covers the essential read/write actions, it might be considered thin for a broader utility scope, though appropriate for its focused purpose.
The tools provide complete CRUD-like coverage for clipboard text operations (read and write), with no dead ends. A minor gap exists in handling non-text data or advanced features like clipboard history, but core functionality is well-covered.