A
licenseA
qualityD
maintenanceA 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.
2
5 npm
1
MIT
Copy-Paste MCP
by ananddtyagi
Copiar y pegar MCP
Un servidor de Protocolo de Contexto de Modelo (MCP) que proporciona una herramienta para extraer líneas específicas del contenido de texto.
Características
Herramienta sencilla para extraer rangos de líneas específicos de cualquier contenido de texto
Conserva el formato exacto del contenido y las nuevas líneas.
Sin modificación del contenido - extracción pura
Implementación del servidor MCP para una fácil integración con herramientas de IA
Related MCP server: MCP PDF Reader
Servidor MCP
Este paquete incluye un servidor MCP que expone la funcionalidad de extracción de líneas como una herramienta que puede ser utilizada por cualquier cliente MCP como Claude Desktop, VS Code u otras aplicaciones compatibles con MCP.
Herramientas disponibles
extract-lines : extrae un rango específico de líneas del contenido del texto
Instalación
Clonar el repositorio
Instalar dependencias:
npm installUso
Iniciar el servidor MCP
npm startEsto iniciará el servidor MCP utilizando el transporte stdio, al cual pueden conectarse los clientes MCP.
Conectarse al servidor
En un cliente compatible con MCP (como Claude Desktop), puedes agregar este servidor con:
Nombre: Copiar y pegar
Comando:
node /path/to/copy-paste-mcp/dist/index.jsTransporte: stdio
Uso de la herramienta
Una vez conectado, podrá utilizar la herramienta a través de la interfaz de su cliente MCP:
Extraer líneas
Tool: extract-lines
Parameters:
- text: "Your multi-line text content goes here\nSecond line\nThird line"
- start_line: 1
- end_line: 2Esto devolverá las dos primeras líneas del contenido de texto proporcionado.
Ejemplos
Extraiga las líneas 10 a 20 de un bloque de texto grande:
Tool: extract-lines
Parameters:
- text: [your text content with many lines]
- start_line: 10
- end_line: 20Extraiga sólo una línea (línea 5):
Tool: extract-lines
Parameters:
- text: [your text content]
- start_line: 5
- end_line: 5¿Por qué usar esto?
Esta herramienta es útil cuando necesitas:
Extraer secciones específicas de bloques de texto grandes
Copiar rangos de líneas exactos del código o la documentación
Asegúrese de que la extracción de contenido sea precisa y sin alteraciones
Integre capacidades de extracción de líneas en flujos de trabajo de IA a través de MCP
Trabajar con porciones específicas de documentos grandes
Available Tools
1 toolextract-linesB
Extract a specific range of lines from text content
ParametersJSON Schema
| 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
B3.1/5.0
Behavior2/5
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.
Conciseness5/5
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.
Completeness3/5
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.
Parameters3/5
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.
Purpose4/5
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.
Usage Guidelines2/5
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
B3.2/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusion or overlap with other tools, making disambiguation perfect.
Naming Consistency5/5
The single tool uses a clear verb_noun pattern (extract-lines), and with no other tools to compare, consistency is inherently perfect.
Tool Count2/5
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.
Completeness2/5
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
ActivityInactive
ResponsivenessNo issues
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
- 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-