Peacock vs PickShade color tools
Peacock is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑17.
Peacock is a plugin bundle for AI coding tools published by b-open-io. No marketplace we read lists it any more. PickShade color tools is an MCP server published by pickshade.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  PickShade color tools | |
|---|---|---|
| Community marketplace b-open-io/claude-plugins | Removed on 2026-10-17 Version: 2.0.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Peacockno longer listed · | PickShade color tools |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (pickshade.com/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 13 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/b-open-io/claude-peacock | github.com/tenzo-run/pickshade-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of Peacock
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
MCP server for creating, validating, and exporting Oh My Posh terminal prompt configurations.
-
Animated terminal pet that reacts to your coding (hooks + statusline + slash commands)
-
A Claude Code statusline that shows reasoning effort and thinking. 5 presets (xsmall-xlarge), Catppuccin, no Node/Nerd Font, native PowerShell on Windows.
-
Automatically updates terminal title with emoji + project + topic context for quick visual cues when switching terminals
-
Tailwind CSS palettes (50-950) from any color, the closest Tailwind color, and Tailwind's defaults
-
Drive the herdr terminal workspace manager: panes, tabs, workspaces, and sibling coding agents
What each says it does
Peacock
Project color theming for your terminal — sets iTerm2 tab colors to match VSCode Peacock themes, with full color management commands
PickShade color tools
18 color tools: OKLCH, WCAG and APCA contrast fixes, palettes, gradients, color blindness, tokens.
How to run each
Peacock
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
PickShade color tools As a remote MCP server
claude mcp add --transport http pickshade https://pickshade.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only PickShade color tools has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Peacock · What it can do: PickShade color tools · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.