copyq-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| COPYQ_MCP_SESSION | No | Existing CopyQ session name | |
| COPYQ_MCP_EXECUTABLE | No | Exact path to the CopyQ executable |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| clipboard_readA | Read one page of CopyQ text history, newest first. |
| clipboard_searchA | Search CopyQ text history from a row and return matching items. |
| clipboard_tabsA | List all CopyQ tabs and their item counts. |
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 3 tools
Each tool targets a distinct operation: listing tabs, reading paginated history, and searching history. There is no overlap that would cause an agent to select the wrong tool.
All tools share the clipboard_ prefix, but clipboard_tabs uses a noun while clipboard_read and clipboard_search use verbs. This is a minor deviation from a consistent verb_noun pattern.
With only 3 tools, the set is well-scoped for a clipboard history reader. Each tool serves a clear purpose without unnecessary bloat.
The surface covers the core operations of a clipboard history viewer: listing tabs, reading pages of history, and searching. There are no obvious missing operations for this domain.