MCP CopyQ Server
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 |
|---|---|
| mcp_readA | Read from CopyQ clipboard manager. MCP tabs (full read/write access):
External tabs (READ-ONLY access with scope="all" or scope="external"):
Modes:
Parameters:
Examples:
Errors: TAB_NOT_FOUND, INDEX_OUT_OF_BOUNDS, INVALID_MODE |
| mcp_writeA | Write to CopyQ clipboard manager. IMPORTANT: All data stored under "mcp/" prefix. When you use tab="info", actual CopyQ path is "mcp/info". Available tabs:
Modes:
Response shows full_path (e.g. "mcp/info") confirming where data was written. Errors: TAB_NOT_FOUND, INDEX_OUT_OF_BOUNDS, PERMISSION_DENIED, MISSING_PARAM |
| mcp_validateA | Validate parameters for mcp_read or mcp_write without executing. Use to check if a call will succeed before making it. Parameters:
Returns:
|
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
The three tools have clearly distinct purposes: mcp_read is for reading data from the clipboard manager, mcp_write is for writing data to it, and mcp_validate is for validating parameters before operations. There is no overlap in functionality, making it easy for an agent to select the correct tool.
All tool names follow a consistent 'mcp_' prefix with a descriptive verb (read, write, validate), using snake_case uniformly. This predictable pattern enhances readability and reduces confusion.
With three tools, the count is appropriate for the server's purpose of clipboard management, covering read, write, and validation operations. It is well-scoped, though a slightly larger set might offer more granularity, but this is reasonable.
The tool set provides complete CRUD and lifecycle coverage for clipboard data management: mcp_read handles retrieval (including search and listing), mcp_write supports creation, updates, deletion, and movement, and mcp_validate ensures parameter integrity. No obvious gaps exist for the domain.