dev-workflow vs Bitbucket MCP Server
dev-workflow is a plugin bundle for AI coding tools published by hiropon. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Bitbucket MCP Server is an MCP server published by lawp09. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-23. 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 |  Bitbucket MCP Server | |
|---|---|---|
| Community marketplace hiroro-work/claude-plugins | Listed Version: 2.7.0 Forks (GitHub): 3 Stars (GitHub): 47 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.29.1 Downloads/month (PyPI): 966 Downloads/week (PyPI): 275 Forks (GitHub): 1 Stars (GitHub): 3 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 1.29.1 Downloads/month (PyPI): 966 Downloads/week (PyPI): 275 Forks (GitHub): 1 Stars (GitHub): 3 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 | dev-workflow | Bitbucket MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 47 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 1 (worse) |
| Last release (differs) | 2026-10-21 | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (bitbucket-mcp-py) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | MIT | MIT |
| Repository (differs) | github.com/hiroro-work/claude-plugins | github.com/lawp09/bitbucket-mcp |
| Changes in the last 7 days (differs) | 3 | 0 |
| First seen (differs) | 2026-10-21 | 2026-10-11 |
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
dev-workflow
Guided development workflow: task decomposition, planning, peer plan review, browser plan approval, implementation, tidy, check/test, rules and code review, one commit per build step, rule updates, retrospectives, an optional demo; mob mode for a junior navigator
Bitbucket MCP Server
MCP server for Bitbucket API - manage repositories, pull requests, comments, pipelines and more
How to run each
dev-workflow As a Claude Code plugin
/plugin marketplace add hiroro-work/claude-plugins
/plugin install dev-workflow@hiropon-pluginsBitbucket MCP Server As a local MCP server: PyPI package
claude mcp add --transport stdio bitbucket-mcp -- uvx bitbucket-mcp-pyCommands built only from what the marketplaces declare; the full set for every client is on each card.
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: dev-workflow · What it can do: Bitbucket MCP Server · 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. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.