peacock-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch-peacock-docsB | Fetches the Peacock for VS Code extension docs from its GitHub repository and answers questions based on the documentation |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.