studio-producer vs GitHub
studio-producer is a plugin bundle for AI coding tools published by Michael Galpert. Marketplaces we read that list it: 1 (Community GitHub marketplaces). GitHub is an MCP server published by github. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-21. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  GitHub | |
|---|---|---|
| Community marketplace ccplugins/awesome-claude-code-plugins | Listed Version: 1.0.0 Forks (GitHub): 744 Stars (GitHub): 977 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.0.2 Forks (GitHub): 5 412 Stars (GitHub): 33 793 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:ffced0d76e77 Forks (GitHub): 5 412 Stars (GitHub): 33 793 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 | studio-producer | GitHub |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 977 (worse) | 33 793 (better) |
| Forks (GitHub) (differs) | 744 (worse) | 5 412 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP, stdio |
| Tools it declares (differs) | Not published | 40 |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/ccplugins/awesome-claude-code-plugins | github.com/github/github-mcp-server |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
studio-producer
PROACTIVELY use this agent when coordinating across multiple teams, allocating resources, or optimizing studio workflows. This agent specializes in cross-functional coordination, resource management, and process optimization within the 6-day development cycle. Should be triggered automatically when team dependencies arise, resource conflicts occur, or workflow improvements are needed. Examples:\n\n<example>\nContext: When multiple teams need to collaborate\nuser: "We need the design and engineering teams to work together on the new creator dashboard"\nassistant: "Cross-team collaboration requires careful orchestration. Let me use the studio-producer agent to coordinate schedules, define handoffs, and ensure smooth collaboration between design and engineering."\n<commentary>\nEffective cross-team coordination prevents bottlenecks and ensures aligned delivery.\n</commentary>\n</example>\n\n<example>\nContext: During resource allocation discussions\nuser: "We have three high-priority features but only two senior
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
How to run each
studio-producer As a Claude Code plugin
/plugin marketplace add ccplugins/awesome-claude-code-plugins
/plugin install studio-producer@awesome-claude-code-pluginsGitHub As a remote MCP server
claude mcp add --transport http github-mcp-server https://api.githubcopilot.com/mcp/ --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only GitHub has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of studio-producer publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of studio-producer publish no settings it asks for, so we do not compare settings.
What it can do: studio-producer · What it can do: GitHub · 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.