Skip to main content
Glama
deenesjakoruzh
ananddtyagi

Copy-Paste MCP

by ananddtyagi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

复制粘贴 MCP

模型上下文协议 (MCP) 服务器提供从文本内容中提取特定行的工具。

特征

  • 从任何文本内容中提取特定行范围的简单工具

  • 保留精确的内容格式和换行符

  • 不修改内容-纯提取

  • MCP 服务器实现，可轻松与 AI 工具集成

Related MCP server: MCP PDF Reader

MCP 服务器

该软件包包括一个 MCP 服务器，它将行提取功能公开为可由任何 MCP 客户端（如 Claude Desktop、VS Code 或其他与 MCP 兼容的应用程序）使用的工具。

可用工具

  1. extract-lines - 从文本内容中提取特定范围的行

安装

  1. 克隆存储库

  2. 安装依赖项：

npm install

用法

启动 MCP 服务器

npm start

这将使用 stdio 传输启动 MCP 服务器，MCP 客户端可以连接到该服务器。

连接到服务器

在与 MCP 兼容的客户端（如 Claude Desktop）中，您可以使用以下命令添加此服务器：

  • 名称：复制粘贴

  • 命令： node /path/to/copy-paste-mcp/dist/index.js

  • 传输：stdio

使用工具

连接后，您可以通过 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 将线提取功能集成到 AI 工作流程中

  • 处理大型文档的特定部分

Available Tools

1 tool
extract-linesB

Extract a specific range of lines from text content

ParametersJSON Schema
NameRequiredDescriptionDefault
textYesThe full text content to extract lines from
start_lineYesStarting line number (inclusive)
end_lineYesEnding 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. 1 tool update
    • First observedextract-lines
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

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

Resources

Related MCP Connectors

Related MCP Servers

  • LSP Tools MCP Server

    rajnaveen344
    A
    license
    A
    quality
    D
    maintenance
    A 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

  • MCP PDF Reader

    rturv
    A
    license
    A
    quality
    C
    maintenance
    A 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.
    7
    19 npm
    1
    MIT

  • MCP Text Editor Server

    fastmcp-me
    A
    license
    Not graded
    quality
    D
    maintenance
    A 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

  • MCP keyword search

    alfaarghya
    F
    license
    A
    quality
    D
    maintenance
    A Model Context Protocol server that enables keyword search within files, returning matching lines with line numbers.
    1
    1
    -