Copy-Paste MCP
Копировать-вставить MCP
Сервер протокола контекста модели (MCP), предоставляющий инструмент для извлечения определенных строк из текстового содержимого.
Функции
Простой инструмент для извлечения определенных диапазонов строк из любого текстового содержимого
Сохраняет точное форматирование содержимого и переводы строк
Никакого изменения содержимого — чистое извлечение.
Реализация сервера MCP для легкой интеграции с инструментами ИИ
Related MCP server: MCP PDF Reader
MCP-сервер
В этот пакет входит сервер MCP, который представляет собой инструмент извлечения строк, который может использоваться любым клиентом MCP, например Claude Desktop, VS Code или другими приложениями, совместимыми с MCP.
Доступные инструменты
extract-lines — извлечение определенного диапазона строк из текстового содержимого
Установка
Клонировать репозиторий
Установить зависимости:
npm installИспользование
Запуск MCP-сервера
npm startЭто запустит сервер MCP, использующий транспорт stdio, к которому могут подключаться клиенты MCP.
Подключение к серверу
В MCP-совместимом клиенте (например, Claude Desktop) вы можете добавить этот сервер с помощью:
Имя: Копировать-Вставить
Команда:
node /path/to/copy-paste-mcp/dist/index.jsТранспорт: стдио
Использование инструмента
После подключения вы сможете использовать инструмент через интерфейс вашего клиента MCP:
Извлечь линии
Tool: extract-lines
Parameters:
- text: "Your multi-line text content goes here\nSecond line\nThird line"
- start_line: 1
- end_line: 2Это вернет первые две строки предоставленного текстового содержимого.
Примеры
Извлечь строки 10–20 из большого текстового блока:
Tool: extract-lines
Parameters:
- text: [your text content with many lines]
- start_line: 10
- end_line: 20Извлеките только одну строку (строка 5):
Tool: extract-lines
Parameters:
- text: [your text content]
- start_line: 5
- end_line: 5Зачем это использовать?
Этот инструмент полезен, когда вам необходимо:
Извлечение определенных разделов из больших текстовых блоков
Копировать точные диапазоны строк из кода или документации
Обеспечить точное извлечение контента без каких-либо изменений
Интеграция возможностей извлечения линий в рабочие процессы ИИ через MCP
Работа с отдельными частями больших документов
Available Tools
1 toolextract-linesB
Extract a specific range of lines from text content
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | The full text content to extract lines from | |
| start_line | Yes | Starting line number (inclusive) | |
| end_line | Yes | Ending line number (inclusive) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the extraction action but doesn't describe what happens with invalid inputs (e.g., start_line > end_line), whether the operation is read-only or has side effects, error handling, or output format. This leaves significant behavioral gaps for an agent.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with zero wasted words. It's appropriately sized for this simple tool and front-loads the core functionality clearly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple text processing tool with no annotations, no output schema, and 100% schema coverage, the description is minimally adequate. It covers the basic purpose but lacks behavioral details and usage context that would help an agent use it correctly in practice.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The schema description coverage is 100%, with all three parameters well-documented in the schema. The description adds no additional parameter semantics beyond implying a range operation. This meets the baseline of 3 when the schema does the heavy lifting.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool's purpose with a specific verb ('extract') and resource ('lines from text content'), and specifies the scope ('a specific range'). It doesn't need sibling differentiation since there are no sibling tools. However, it could be slightly more specific about what 'extract' means operationally.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool versus alternatives, prerequisites, or constraints. It simply states what the tool does without context about appropriate use cases or limitations.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
extract-lines
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap with other tools, making disambiguation perfect.
The single tool uses a clear verb_noun pattern (extract-lines), and with no other tools to compare, consistency is inherently perfect.
One tool is too few for a server named 'Copy-Paste MCP', which suggests broader copy-paste functionality, making the scope feel incomplete and thin.
The tool only extracts lines from text, lacking obvious operations like copying full text, pasting, or handling other copy-paste tasks, indicating significant gaps for the domain.
Maintenance
Related MCP Connectors
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Model Context Protocol server for Studex tools, notifications, and profile integrations
Model Context Protocol server for todo.vu task management and time tracking.
Related MCP Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol server that provides tools to find regex pattern positions in files and list allowed directories, enabling text analysis with LSP-like functionality.25 npm1MIT
- AlicenseAqualityCmaintenanceA Model Context Protocol server that enables the extraction of text, metadata, and embedded images from PDF files. It provides tools for searching text with context, reading specific pages, and counting total pages within a document.719 npm1MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides line-oriented text file editing capabilities through a standardized API. Optimized for LLM tools with efficient partial file access to minimize token usage.MIT
- FlicenseAqualityDmaintenanceA Model Context Protocol server that enables keyword search within files, returning matching lines with line numbers.11-