Skip to main content
Glama
enesjakozh
johnpapa

peacock-mcp

by johnpapa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

在 GitHub Codespaces 中打开项目 铁匠徽章节点版本 执照

在 VS Code 中使用 NPM 安装 在 VS Code Insiders 中使用 NPM 安装

在 VS Code 中使用 Docker 安装 在 VS Code Insiders 中使用 Docker 安装

功能•工具•设置•配置 MCP 主机

VS Code Peacock 扩展的 MCP 服务器，一次一个代码编辑器，为你的世界增添色彩。该项目的主要目标是展示如何使用 MCP 服务器与 API 交互。

注意：此 MCP 服务器使用的所有数据均来自官方 Peacock 文档。

🔧 功能

  • 获取 Peacock 文档：获取有关 Peacock 的详细信息。

Related MCP server: mcp-server-code-runner

🧰 工具

1. fetch_peacock_docs

  • 描述：从 GitHub 存储库获取 Peacock for VS Code 扩展文档，并根据文档回答问题

  • 输入：

    • prompt （查询）：关于孔雀的问题。

  • 返回：您的答案！

🛠️ 设置

在此处为 VS Code 安装 Peacock 。

使用 VS Code Insiders 运行托管在 GitHub Copilot 中的 MCP 服务器

注意：如果您已经使用 Claude Desktop 启用了 MCP 服务器，请在 VS Code 设置中添加chat.mcp.discovery.enabled: true ，它将发现现有的 MCP 服务器列表。

如果您想要将 MCP 服务器与特定的 repo 关联，请创建包含以下内容的.vscode/mcp.json文件：

{
  "inputs": [],
  "servers": {
    "peacock-mcp": {
      "command": "npx",
      // "command": "node",
      "args": [
        "-y",
        "@johnpapa/peacock-mcp"
        // "_git/peacock-mcp/dist/index.js"
      ],
      "env": {}
    }
  }
}

如果您想要将 MCP 服务器与所有存储库关联，请将以下内容添加到您的 VS Code 用户设置 JSON 中：

"mcp": {
  "servers": {
    "peacock-mcp": {
      "command": "npx",
      // "command": "node",
      "args": [
        "-y",
        "@johnpapa/peacock-mcp"
        // "/Users/papa/_git/peacock-mcp/dist/index.js"
        // "_git/peacock-mcp/dist/index.js"
      ],
      "env": {}
    }
  }
}
"chat.mcp.discovery.enabled": true,

VS Code 手动安装

注意：为了快速安装，请单击此自述文件顶部的安装按钮。

使用 VS Code 设置

要在 VS Code 中手动安装 Peacock MCP 服务器，请按照以下步骤操作：

  1. 按Cmd+Shift+P （macOS）或Ctrl+Shift+P （Windows/Linux）并搜索“首选项：打开用户设置（JSON）”来打开 VS Code 设置（JSON）

  2. 将以下 JSON 添加到您的设置文件：

{
  "mcp": {
    "servers": {
      "peacock-mcp": {
        "command": "npx",
        "args": ["-y", "@johnpapa/peacock-mcp"],
        "env": {}
      }
    }
  },
  "chat.mcp.discovery.enabled": true
}

使用 CLI 命令

对于 VS Code Stable：

code --add-mcp '{"name":"peacock-mcp","command":"npx","args":["-y","@johnpapa/peacock-mcp"],"env":{}}'

对于 VS Code 内部人员：

code-insiders --add-mcp '{"name":"peacock-mcp","command":"npx","args":["-y","@johnpapa/peacock-mcp"],"env":{}}'

通过 Smithery 安装

要通过Smithery自动为 Claude Desktop 安装 Peacock MCP 服务器：

npx -y @smithery/cli install @johnpapa/peacock-mcp --client claude

使用 MCP Inspector 在本地运行 MCP 服务器

如果您想在本地运行 MCP Inspector 来测试服务器，请按照以下步骤操作：

  1. 克隆此存储库：

    git clone https://github.com/johnpapa/peacock-mcp

  2. 安装所需的依赖项并构建项目。

    npm install
npm run build

  3. （可选）要使用 MCP Inspector 试用服务器，请运行以下命令：

    # Start the MCP Inspector
npx @modelcontextprotocol/inspector node build/index.js

    访问浏览器控制台中显示的 MCP Inspector URL。将Arguments更改为dist/index.js并选择Connect 。选择List Tools查看可用的工具。

使用 GitHub Copilot 中的工具

  1. 现在 mcp 服务器已可发现，打开 GitHub Copilot 并选择Agent模式（而不是Chat或Edits ）。

  2. 选择 Copilot 聊天文本字段中的“刷新”按钮来刷新服务器列表。

  3. 选择“🛠️”按钮查看所有可能的工具，包括来自此 repo 的工具。

  4. 在聊天中提出一个自然会调用其中一种工具的问题，例如：

    How do I set my VS Code accent colors?

    注意：如果您看到“抱歉，响应已被负责任的 AI 服务过滤。请重新措辞您的提示并重试。”，请尝试再次运行它或重新措辞提示。

Available Tools

1 tool
fetch-peacock-docsB

Fetches the Peacock for VS Code extension docs from its GitHub repository and answers questions based on the documentation

ParametersJSON Schema
NameRequiredDescriptionDefault
queryYesThe question to answer based on the Peacock documentation

TDQS

B3.3/5.0
Behavior2/5

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

The description does not disclose how answers are generated, source repository specifics (branch, version), caching, error handling, or rate limits. With no annotations, the description carries full burden and 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence that is concise, though slightly run-on. No wasted words, but could be structured more clearly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With one parameter and no output schema, the description should explain what the tool returns and how it works. It mentions 'answers questions' but not the format or completeness. Additional details are needed.

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?

Schema coverage is 100% and the description adds little beyond the schema's own description of the 'query' parameter. Baseline 3 as schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it fetches Peacock documentation and answers questions, with a specific verb and resource. No sibling tools exist, so differentiation is not required.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit guidance on when to use or not use this tool, but the purpose is implied. Since there are no sibling tools, the lack of alternatives is acceptable, but prerequisites or context are missing.

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 observedfetch-peacock-docs
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

A3.6/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion between tools. An agent will always select this tool correctly when needed.

Naming Consistency5/5

The single tool uses a clear verb_noun pattern (fetch-peacock-docs), which is consistent and descriptive. As there is only one tool, naming consistency is not an issue.

Tool Count3/5

One tool is minimal for a server, but it may be acceptable if the entire functionality is covered by a single combined action (fetching docs and answering questions). However, it feels thin compared to typical MCP servers that offer multiple operations.

Completeness4/5

The tool appears to fully cover its stated purpose: fetching Peacock documentation and answering questions about it. There is no obvious missing functionality for a Q&A tool over static docs, though a separate fetch tool could be argued.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches