Skip to main content
Glama
deenesjakoruzh
f-is-h

MCP Easy Copy

by f-is-h
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

MCP 轻松复制

MCP 服务器 平台 npm 版本 Node.js 铁匠徽章执照

模型上下文协议服务器可以轻松发现和复制 Claude Desktop 中可用的 MCP 服务。

目的

此 MCP 服务器旨在成为您使用 Claude Desktop 时的第一站。它通过以下方式解决了必须记住 MCP 服务名称或在配置文件中查找它们的问题：

  1. 自动读取Claude Desktop配置文件

  2. 提取所有已配置的 MCP 服务的名称

  3. 以易于复制的格式将它们呈现在工具列表的顶部

虽然 Claude 现在可以在大多数情况下自动选择合适的 MCP 服务，但在某些情况下，用户仍然需要明确指定 MCP 服务名称。这些情况包括：

  • 当您配置了许多 MCP 服务时，工具列表会变得很长，难以导航

  • 当特定的 MCP 服务提供多个可调用操作时，进一步增加列表长度

  • 当你需要指示 Claude 使用特定服务而不是依赖其自动选择时

  • 排除故障或比较不同 MCP 服务之间的结果时

该工具弥补了这一差距，使得所有可用的服务都可以轻松访问，而无需搜索配置文件。

Related MCP server: discord-mcp

特征

  • 出现在工具列表顶部：使用特殊名称格式始终出现在最前面

  • 动态更新：始终显示最新的可用服务

  • 复制友好格式：编号列表，方便参考

  • 零外部依赖：只需要 Node.js

安装

选项 1：通过 npm 安装（推荐）

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

然后添加到您的 Claude Desktop 配置：

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

选项 2：通过 Smithery 安装

要通过Smithery自动安装 Claude Desktop 的 Easy Copy：

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

选项 3：手动安装

  1. 克隆存储库：

    git clone https://github.com/f-is-h/mcp-easy-copy.git
cd mcp-easy-copy

  2. 安装依赖项并构建：

    npm install
npm run build

  3. 配置Claude桌面：

    **对于 macOS：**编辑~/Library/Application Support/Claude/claude_desktop_config.json

    **对于 Windows：**编辑%APPDATA%\Claude\claude_desktop_config.json

    添加以下配置：

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

  4. 重启Claude桌面

使用工具

安装后，您可以通过两种方式使用该服务：

  1. **通过工具菜单：**单击 Claude Desktop 中的锤子图标并选择列表顶部的服务（它将在其描述中显示所有可用的服务）

  2. 通过提示：向Claude 询问以下问题：

    Please list all MCP services that are available to you

    或者

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

发展

MCP Easy Copy 使用 TypeScript 构建并使用模型上下文协议 SDK。

# Install dependencies
npm install

# Build the project
npm run build

# Test with the MCP Inspector
npm run inspector

故障排除

如果该工具没有按预期工作：

  1. 检查日志：查看日志文件

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

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

  2. 验证配置：确保您的claude_desktop_config.json是有效的 JSON

  3. 检查 Node.js ：确保 Node.js 已正确安装（ node --version ）

  4. 重启 Claude ：更改配置后务必重启 Claude Desktop

  5. 使用检查器：运行npm run inspector来使用 MCP 检查器进行调试

其他徽章

执照

MIT 许可证

未来愿景

虽然我们目前尚不清楚 Anthropic 的具体路线图，但我们推测 Claude 客户端的未来版本可能会实现诸如使用“@”符号时自动完成的功能。该功能可能会显示一个可用 MCP 服务的下拉列表，让用户更轻松地明确指示 Claude 使用特定服务。

即使这些改进最终会让这个项目变得过时，我们也乐见 Claude 的界面能够不断改进，从而提升用户体验。毕竟，这款工具的目标是让 MCP 服务更易于访问，而将这一功能直接内置到 Claude 中将是最终的成功。

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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • Changed_________available_mcp_services_for_easy_copy_________1 field changed
      • removedInput schema / additionalProperties
        Removed value: -false
  2. 1 tool update
    • First observed_________available_mcp_services_for_easy_copy_________
Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

B3.2/5.0

Scored across 1 tool

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

Related MCP Connectors

Related MCP Servers

Appeared in Searches