Skip to main content
Glama
f-is-h

MCP Easy Copy

by f-is-h

MCP Easy Copy

MCP Server Platforms npm version Node.js License

A Model Context Protocol server that makes it easy to discover and copy available MCP services in Claude Desktop.

Purpose

This MCP server is designed to be your first stop when working with Claude Desktop. It solves the problem of having to remember MCP service names or looking them up in configuration files by:

  1. Automatically reading the Claude Desktop configuration file

  2. Extracting the names of all configured MCP services

  3. Presenting them in an easy-to-copy format at the top of the tools list

Although Claude can now automatically select the appropriate MCP services in most scenarios, there are still situations where users need to explicitly specify an MCP service name. These situations include:

  • When you have many MCP services configured, making the tools list long and difficult to navigate

  • When specific MCP services offer multiple callable actions, further increasing the list length

  • When you need to direct Claude to use a specific service rather than relying on its automatic selection

  • When troubleshooting or comparing results between different MCP services

This tool bridges that gap, making all available services easily accessible without having to search through configuration files.

Related MCP server: discord-mcp

Features

  • Appears at the top of tools list: Uses special name formatting to always appear first

  • Dynamic updates: Always shows the latest available services

  • Copy-friendly format: Numbered list for easy reference

  • Zero external dependencies: Just needs Node.js

Installation

npm install -g @fishes/mcp-easy-copy

Then add to your Claude Desktop configuration:

{
  "mcpServers": {
    "mcp-easy-copy": {
      "command": "npx",
      "args": [
        "-y",
        "@fishes/mcp-easy-copy"
      ]
    }
  }
}

Option 2: Installing via Smithery

To install Easy Copy for Claude Desktop automatically via Smithery:

npx -y @smithery/cli install @fisheepx/mcp-easy-copy --client claude

Option 3: Manual Installation

  1. Clone the repository:

    git clone https://github.com/f-is-h/mcp-easy-copy.git
    cd mcp-easy-copy
  2. Install dependencies and build:

    npm install
    npm run build
  3. Configure Claude Desktop:

    For macOS: Edit ~/Library/Application Support/Claude/claude_desktop_config.json

    For Windows: Edit %APPDATA%\Claude\claude_desktop_config.json

    Add the following configuration:

    {
      "mcpServers": {
        "mcp-easy-copy": {
          "command": "node",
          "args": [
             "/ABSOLUTE/PATH/TO/mcp_easy_copy/build/index.js"
          ]
        }
      }
    }
  4. Restart Claude Desktop

Using the Tool

Once installed, you can use the service in two ways:

  1. Via the tools menu: Click the hammer icon in Claude Desktop and select the service at the top of the list (it will show all available services in its description)

  2. Via a prompt: Ask Claude something like:

    Please list all MCP services that are available to you

    or

    Please use _________mcp-easy-copy_________ to show me all available MCP services

Development

MCP Easy Copy is built with TypeScript and uses the Model Context Protocol SDK.

# Install dependencies
npm install

# Build the project
npm run build

# Test with the MCP Inspector
npm run inspector

Troubleshooting

If the tool doesn't work as expected:

  1. Check logs: Look at the log files

    • macOS: ~/Library/Logs/Claude/mcp-server-mcp-easy-copy.log

    • Windows: %APPDATA%\Claude\logs\mcp-server-mcp-easy-copy.log

  2. Verify configuration: Make sure your claude_desktop_config.json is valid JSON

  3. Check Node.js: Ensure Node.js is properly installed (node --version)

  4. Restart Claude: Always restart Claude Desktop after making configuration changes

  5. Use the Inspector: Run npm run inspector to debug with the MCP Inspector

Other Badges

Glama

MseeP.ai

License

MIT License

Future Vision

While we have no specific knowledge of Anthropic's roadmap, we imagine that future versions of Claude's client could potentially implement features like autocomplete when using the '@' symbol. Such a feature might display a dropdown list of available MCP services, making it much easier for users to explicitly instruct Claude to utilize specific services.

Even if such improvements eventually make this project obsolete, we'd be delighted to see Claude's interface evolve in ways that improve user experience. After all, the goal of this tool is to make MCP services more accessible, and having that functionality built directly into Claude would be the ultimate success.

Available Tools

1 tool
_________available_mcp_services_for_easy_copy_________B

List all MCP services available in this Claude instance

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'List all' implies a read-only operation, it doesn't specify whether this requires permissions, what format the output returns, or any rate limits or side effects. For a tool with zero annotation coverage, this is insufficient.

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 that directly states the tool's purpose without any unnecessary words or structural issues. It is appropriately sized and front-loaded.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is adequate but has clear gaps. It explains the basic purpose but lacks behavioral details like output format or usage context, making it minimally viable but not fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters with 100% schema description coverage, so the schema already fully documents the lack of inputs. The description appropriately doesn't add parameter details, maintaining a baseline of 4 for tools with no parameters.

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 action ('List all') and the resource ('MCP services available in this Claude instance'), providing a specific verb+resource combination. However, since there are no sibling tools mentioned, it cannot demonstrate differentiation from alternatives, which prevents a perfect score of 5.

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 contextual constraints. It simply states what the tool does without any usage instructions or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

TDQS

B3.2/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear and distinct purpose: listing available MCP services.

Naming Consistency5/5

With only one tool, naming consistency is inherently perfect. The tool name follows a descriptive snake_case pattern that clearly indicates its function.

Tool Count2/5

A single tool is too few for most practical server purposes, as it severely limits functionality. While the tool's purpose is clear, the server feels incomplete and under-scoped with just one operation.

Completeness1/5

The server is severely incomplete for any meaningful domain. With only a listing tool and no actual copy or manipulation capabilities, there are significant gaps that will prevent agents from performing useful work beyond basic discovery.

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

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/f-is-h/mcp-easy-copy'

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