Skip to main content
Glama
deenesjakoruzh
ananddtyagi

Copy-Paste MCP

by ananddtyagi
OverviewSchemaRelated ServersScoreDiscussions
TypeScript

Copy-Paste MCP

A Model Context Protocol (MCP) server that provides a tool for extracting specific lines from text content.

Features

  • Simple tool to extract specific line ranges from any text content

  • Preserves exact content formatting and newlines

  • No modification of content - pure extraction

  • MCP server implementation for easy integration with AI tools

Related MCP server: MCP PDF Reader

MCP Server

This package includes an MCP server that exposes the line extraction functionality as a tool that can be used by any MCP client like Claude Desktop, VS Code, or other MCP-compatible applications.

Available Tools

  1. extract-lines - Extract a specific range of lines from text content

Installation

  1. Clone the repository

  2. Install dependencies:

npm install

Usage

Starting the MCP Server

npm start

This will start the MCP server using the stdio transport, which can be connected to by MCP clients.

Connecting to the Server

In an MCP-compatible client (like Claude Desktop), you can add this server with:

  • Name: Copy-Paste

  • Command: node /path/to/copy-paste-mcp/dist/index.js

  • Transport: stdio

Using the Tool

Once connected, you can use the tool through your MCP client's interface:

Extract Lines

Tool: extract-lines
Parameters:
  - text: "Your multi-line text content goes here\nSecond line\nThird line"
  - start_line: 1
  - end_line: 2

This will return the first two lines of the provided text content.

Examples

Extract lines 10-20 from a large text block:

Tool: extract-lines
Parameters:
  - text: [your text content with many lines]
  - start_line: 10
  - end_line: 20

Extract just a single line (line 5):

Tool: extract-lines
Parameters:
  - text: [your text content]
  - start_line: 5
  - end_line: 5

Why use this?

This tool is useful when you need to:

  • Extract specific sections from large text blocks

  • Copy exact line ranges from code or documentation

  • Ensure precise content extraction without any alterations

  • Integrate line extraction capabilities into AI workflows via MCP

  • Work with specific portions of large documents

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. Dates show when Glama detected each change.

  1. 1 tool update
    • First observedextract-lines
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.2/5.0
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

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

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
    1
    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
    29
    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
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ananddtyagi/copy-paste-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server