code-copy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ALLOWED_DIRECTORIES | No | Comma-separated list of directories where file operations are allowed. If not specified, defaults to user's home directory, Documents, Desktop, and Projects folders. | User's home directory, Documents, Desktop, Projects |
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": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| copy_codeA | Copy code lines from source file. Args: source_file: Path to source file start_line: Starting line number (1-based) end_line: Ending line number (1-based), defaults to start_line include_line_numbers: Whether to include line numbers in output Returns: Copied code content as string |
| paste_codeA | Paste code at specific line in target file. Args: target_file: Path to target file line_number: Line number to paste at (1-based, inserts before this line) code: Code content to paste create_backup: Whether to create backup file before modification Returns: Success message with details |
| copy_entire_fileA | Copy entire content of source file. Args: source_file: Path to source file include_line_numbers: Whether to include line numbers Returns: Full file content as string |
| search_and_replaceA | Search and replace text in target file. Args: target_file: Path to target file search_pattern: Text to search for replacement: Replacement text case_sensitive: Whether search is case sensitive replace_all: Whether to replace all occurrences or just first create_backup: Whether to create backup file Returns: Success message with replacement count |
| get_file_infoC | Get basic information about a file. Args: file_path: Path to file Returns: File information as string |
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 5 tools
Each tool targets a distinct operation: full file read, partial read, metadata read, text replacement, and line insertion. There is no ambiguity because the descriptions clearly differentiate between copying content and modifying files.
All tool names follow a consistent verb_noun snake_case pattern, such as copy_entire_file, get_file_info, and paste_code. Even search_and_replace uses a verb-first structure, maintaining predictability.
With 5 tools, the server is well-scoped for its purpose of copying and manipulating code. The count is neither too sparse nor excessive, and each tool serves a clear role in the workflow.
The tools cover the core operations for code copying: reading an entire file, reading a range, replacing text, and inserting code. A minor gap is the lack of a create_file operation, but agents can work around this by using existing files.