peacock-mcp
Características • Herramientas • Configuración • Configuración de un host MCP
Servidor MCP para la extensión Peacock de VS Code : colorea tu mundo, un editor de código a la vez. El objetivo principal del proyecto es mostrar cómo se puede usar un servidor MCP para interactuar con las API.
Nota : Todos los datos utilizados por este servidor MCP se obtienen de la documentación oficial de Peacock .
🔧 Características
Obtener documentos de Peacock : obtenga información detallada sobre Peacock.
Related MCP server: mcp-server-code-runner
🧰 Herramientas
1. fetch_peacock_docs 🔍🦸♂️
Descripción : Obtiene los documentos de la extensión Peacock para VS Code de su repositorio de GitHub y responde preguntas basadas en la documentación.
Aporte :
prompt(consulta): La pregunta sobre Peacock.
Devoluciones :¡Tu respuesta!
🛠️ Configuración
Instale Peacock para VS Code AQUÍ .
Ejecución del servidor MCP alojado en GitHub Copilot con VS Code Insiders
Nota : Si ya tiene el servidor MCP habilitado con Claude Desktop, agregue
chat.mcp.discovery.enabled: trueen la configuración de VS Code y descubrirá las listas de servidores MCP existentes.
Si desea asociar el servidor MCP con un repositorio específico, cree un archivo .vscode/mcp.json con este contenido:
{
"inputs": [],
"servers": {
"peacock-mcp": {
"command": "npx",
// "command": "node",
"args": [
"-y",
"@johnpapa/peacock-mcp"
// "_git/peacock-mcp/dist/index.js"
],
"env": {}
}
}
}Si desea asociar el servidor MCP con todos los repositorios, agregue lo siguiente a su JSON de configuración de usuario de VS Code:
"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,Instalación manual de VS Code
Nota : Para una instalación rápida, haga clic en los botones de instalación en la parte superior de este README.
Uso de la configuración de VS Code
Para instalar manualmente el servidor Peacock MCP en VS Code, siga estos pasos:
Abra la configuración de VS Code (JSON) presionando
Cmd+Shift+P(macOS) oCtrl+Shift+P(Windows/Linux) y buscando "Preferencias: Abrir configuración de usuario (JSON)".Agregue el siguiente JSON a su archivo de configuración:
{
"mcp": {
"servers": {
"peacock-mcp": {
"command": "npx",
"args": ["-y", "@johnpapa/peacock-mcp"],
"env": {}
}
}
},
"chat.mcp.discovery.enabled": true
}Uso de comandos CLI
Para VS Code Stable:
code --add-mcp '{"name":"peacock-mcp","command":"npx","args":["-y","@johnpapa/peacock-mcp"],"env":{}}'Para miembros de VS Code Insiders:
code-insiders --add-mcp '{"name":"peacock-mcp","command":"npx","args":["-y","@johnpapa/peacock-mcp"],"env":{}}'Instalación mediante herrería
Para instalar Peacock MCP Server para Claude Desktop automáticamente a través de Smithery :
npx -y @smithery/cli install @johnpapa/peacock-mcp --client claudeEjecute el servidor MCP localmente con MCP Inspector
Si desea ejecutar MCP Inspector localmente para probar el servidor, siga estos pasos:
Clonar este repositorio:
git clone https://github.com/johnpapa/peacock-mcpInstale las dependencias necesarias y compile el proyecto.
npm install npm run build(Opcional) Para probar el servidor usando MCP Inspector, ejecute el siguiente comando:
# Start the MCP Inspector npx @modelcontextprotocol/inspector node build/index.jsVisita la URL del Inspector MCP que se muestra en la consola de tu navegador. Cambia
Argumentsadist/index.jsy seleccionaConnect. SeleccionaList Toolspara ver las herramientas disponibles.
Uso de herramientas en GitHub Copilot
Ahora que el servidor mcp es detectable, abra GitHub Copilot y seleccione el modo
Agent(noChatniEdits).Seleccione el botón "actualizar" en el campo de texto del chat de Copilot para actualizar la lista de servidores.
Seleccione el botón "🛠️" para ver todas las herramientas posibles, incluidas las de este repositorio.
Coloque una pregunta en el chat que invoque naturalmente una de las herramientas, por ejemplo:
How do I set my VS Code accent colors?Nota : Si ve "Lo sentimos, la respuesta fue filtrada por el Servicio de IA responsable. Reformule su mensaje e inténtelo de nuevo.", intente ejecutarlo nuevamente o reformule el mensaje.
Available Tools
1 toolfetch-peacock-docsB
Fetches the Peacock for VS Code extension docs from its GitHub repository and answers questions based on the documentation
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The question to answer based on the Peacock documentation |
TDQS
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.
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.
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.
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.
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.
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 tool update
- First observed
fetch-peacock-docs
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. An agent will always select this tool correctly when needed.
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.
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.
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
Related MCP Connectors
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
The official MCP Server for the Mux API
Related MCP Servers
- AlicenseAqualityDmaintenanceMCP server to interact with Obsidian via the Local REST API community plugin.22134,467MIT
- AlicenseBqualityFmaintenanceMCP Server for running code snippet and show the result.1808 npm243MIT
- AlicenseAqualityDmaintenanceMCP server to expose VS Code editing features to an LLM for AI coding9188 npm391MIT
- AlicenseNot gradedqualityDmaintenanceA minimal WebSocket-based MCP server implementation that enables modern tool integrations with VSCode, Claude, and other applications.9 npmISC