Clipboard MCP 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 |
|---|---|
| copy_pasteC | Copy/paste content between files using text patterns. Find content by search pattern, insert at marker location. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'copy_paste' has a clear, distinct purpose described as copying and pasting content between files using text patterns.
Since there is only one tool, naming consistency is inherently perfect. The tool name 'copy_paste' follows a clear verb-based pattern (copy and paste), and there are no other tools to compare it against for inconsistency.
A single tool is generally too few for a server's purpose, as it limits functionality and may indicate an incomplete or overly narrow scope. For a clipboard server, one might expect additional tools like 'cut', 'clear', or operations on different data types, making this count insufficient for robust coverage.
The server's domain appears to be clipboard operations, but with only one tool for copy/paste, there are significant gaps. Missing operations likely include cutting, clearing, or handling clipboard history, which are common in clipboard functionality, leading to an incomplete surface that could cause agent failures.