Access Peacock VS Code Extension Docs
Peacock MCP Server: Fetch Peacock extension docs and answer questions about it.
Maintainer of this project? Claim this page to edit the listing.
1.1.15Add to Favorites
Why it matters
Integrate with the Peacock VS Code extension to access its documentation and configuration assistance. This MCP server allows you to query information about Peacock's features and customization options.
Outcomes
What it gets done
Fetch and retrieve documentation for the Peacock VS Code extension.
Answer questions regarding Peacock extension functionality and configuration.
Provide assistance with customizing colors and themes in VS Code using Peacock.
Install
Add it to your toolbox
Run in your project directory:
curl -fsSL https://spark.entire.vc/get/vb-peacock-for-vs-code | bash Capabilities
Tools your agent gets
Fetches documentation for the Peacock extension for VS Code from its GitHub repository
Overview
Peacock for VS Code MCP Server
This MCP server allows you to fetch documentation for the Peacock VS Code extension and ask questions about it. It demonstrates how an MCP server can interact with APIs. Use this MCP server when you need to programmatically access information about the Peacock VS Code extension or integrate API interactions via an MCP server.
What it does
MCP Server for the Peacock extension for VS Code, coloring your world, one Code editor at a time. The main goal of the project is to show how an MCP server can be used to interact with APIs. All data used by this MCP server is fetched from the official Peacock documentation.
Features
- Fetch Peacock docs: Get detailed info on Peacock.
Tools
fetch_peacock_docs: Fetches the Peacock for VS Code extension docs from its GitHub repository and answers questions based on the documentation.- Input:
prompt(query): The question about Peacock. - Returns: Your answer!
- Input:
Setup
Install Peacock for VS Code HERE.
To install the Peacock MCP server in VS Code, add the following to your VS Code User Settings JSON:
{
"mcp": {
"servers": {
"peacock-mcp": {
"command": "npx",
"args": ["-y", "@johnpapa/peacock-mcp"],
"env": {}
}
}
},
"chat.mcp.discovery.enabled": true
}
Alternatively, use the CLI command:
code --add-mcp '{"name":"peacock-mcp","command":"npx","args":["-y","@johnpapa/peacock-mcp"],"env":{}}'
Source README
MCP Server for the Peacock extension for VS Code, coloring your world, one Code editor at a time. The main goal of the project is to show how an MCP server can be used to interact with APIs.
Note: All data used by this MCP server is fetched from the official Peacock documentation.
🔧 Features
- Fetch Peacock docs: Get detailed info on Peacock.
🧰 Tools
1. fetch_peacock_docs 🔍🦸♂️
- Description: Fetches the Peacock for VS Code extension docs from its GitHub repository and answers questions based on the documentation
- Input:
prompt(query): The question about Peacock.
- Returns: Your answer!
🛠️ Setup
Install Peacock for VS Code HERE.
Running the MCP Server hosted in GitHub Copilot with VS Code Insiders
Note: If you already have the MCP server enabled with Claude Desktop, add
chat.mcp.discovery.enabled: truein your VS Code settings and it will discover existing MCP server lists.
If you want to associate the MCP server with a specific repo, create a .vscode/mcp.json file with this content:
{
"inputs": [],
"servers": {
"peacock-mcp": {
"command": "npx",
// "command": "node",
"args": [
"-y",
"@johnpapa/peacock-mcp"
// "_git/peacock-mcp/dist/index.js"
],
"env": {}
}
}
}
If you want to associate the MCP server with all repos, add the following to your VS Code User Settings 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 Manual Installation
Note: For quick installation, click the install buttons at the top of this README.
Using VS Code Settings
To manually install the Peacock MCP server in VS Code, follow these steps:
- Open VS Code Settings (JSON) by pressing
Cmd+Shift+P(macOS) orCtrl+Shift+P(Windows/Linux) and searching for "Preferences: Open User Settings (JSON)" - Add the following JSON to your settings file:
{
"mcp": {
"servers": {
"peacock-mcp": {
"command": "npx",
"args": ["-y", "@johnpapa/peacock-mcp"],
"env": {}
}
}
},
"chat.mcp.discovery.enabled": true
}
Using CLI Commands
For VS Code Stable:
code --add-mcp '{"name":"peacock-mcp","command":"npx","args":["-y","@johnpapa/peacock-mcp"],"env":{}}'
For VS Code Insiders:
code-insiders --add-mcp '{"name":"peacock-mcp","command":"npx","args":["-y","@johnpapa/peacock-mcp"],"env":{}}'
Installing via Smithery
To install Peacock MCP Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install @johnpapa/peacock-mcp --client claude
Run the MCP Server Locally with MCP Inspector
If you'd like to run MCP Inspector locally to test the server, follow these steps:
Clone this repository:
git clone https://github.com/johnpapa/peacock-mcpInstall the required dependencies and build the project.
npm install npm run build(Optional) To try out the server using MCP Inspector run the following command:
# Start the MCP Inspector npx @modelcontextprotocol/inspector node build/index.jsVisit the MCP Inspector URL shown in the console in your browser. Change
Argumentstodist/index.jsand selectConnect. SelectList Toolsto see the available tools.
Using Tools in GitHub Copilot
Now that the mcp server is discoverable, open GitHub Copilot and select the
Agentmode (notChatorEdits).Select the "refresh" button in the Copilot chat text field to refresh the server list.
Select the "🛠️" button to see all the possible tools, including the ones from this repo.
Put a question in the chat that would naturally invoke one of the tools, for example:
How do I set my VS Code accent colors?Note: If you see "Sorry, the response was filtered by the Responsible AI Service. Please rephrase your prompt and try again.", try running it again or rephrasing the prompt.
FAQ
Common questions
Discussion
Questions & comments · 0
Sign In Sign in to leave a comment.