peacock-mcp
Related Servers
Alternatives to peacock-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceMCP server to expose VS Code editing features to an LLM for AI coding9106 npm392MIT
- AlicenseAqualityDmaintenanceMCP server to interact with Obsidian via the Local REST API community plugin.134,400MIT
- AlicenseCqualityDmaintenanceA simple MCP server that provides a basic greeting tool for saying hello with customizable names. Serves as a boilerplate template for developers to quickly create and deploy new MCP servers.16 npmMIT
- FlicenseNot gradedqualityCmaintenanceConverts VSCode into an MCP server that enables external clients to remotely execute VSCode internal commands, query workspace information, and interact with the editor through HTTP streaming. Built on the FastMCP framework with security controls and real-time monitoring.63-
- AlicenseBqualityFmaintenanceMCP Server for running code snippet and show the result.1520 npm246MIT
- AlicenseNot gradedqualityDmaintenanceA minimal WebSocket-based MCP server implementation that enables modern tool integrations with VSCode, Claude, and other applications.6 npmISC
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.