SmartBear MCP vs CloudBees Unify MCP Server
SmartBear MCP is an MCP server published by smartbear.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). CloudBees Unify MCP Server is an MCP server published by cloudbees. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 |  SmartBear MCP |  CloudBees Unify MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.42.0 Downloads/month (npm): 45 350 Downloads/week (npm): 4 476 Forks (GitHub): 51 Stars (GitHub): 44 Not marked · First seen |
Listed Version: 1.0.3 No figure published Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:8a64acae01b6 Forks (GitHub): 51 Pulls (Docker Hub): 14 440 Stars (Docker Hub): 0 Stars (GitHub): 44 Not marked · First seen |
Not listed |
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 | SmartBear MCP | CloudBees Unify MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 44 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 14 440 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 51 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server or your machine | Remote server (mcp.cloudbees.io/v1/mcp) |
| Transport (differs) | Streamable HTTP, stdio | Streamable HTTP |
| Tools it declares (differs) | 160 | Not published |
| Environment variables it asks for (differs) | 17, secrets among them: 10 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/smartbear/smartbear-mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 400 (5 days ago) | Responded 2 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
SmartBear MCP
MCP server for AI access to SmartBear tools, including BugSnag, Reflect, Swagger, PactFlow, QTM4J.
CloudBees Unify MCP Server
Connect AI agents to CloudBees Unify: feature flags, CI/CD, release orchestration, and security
How to run each
SmartBear MCP As a remote MCP server
claude mcp add --transport http smartbear-mcp https://bugsnag.mcp.smartbear.com/mcpRequires: BEARQ_API_TOKEN (secret), BUGSNAG_AUTH_TOKEN (secret), PACT_BROKER_PASSWORD (secret), PACT_BROKER_TOKEN (secret), QTM4J_API_KEY (secret), QTM4J_AUTOMATION_API_KEY (secret), REFLECT_API_TOKEN (secret), SWAGGER_API_KEY (secret), SWAGGER_FUNCTIONAL_TESTING_API_TOKEN (secret), ZEPHYR_API_TOKEN (secret)
CloudBees Unify MCP Server As a remote MCP server
claude mcp add --transport http unify-mcp-server https://mcp.cloudbees.io/v1/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of CloudBees Unify MCP Server responded at the last daily check. How we check endpoints
Tools each declares
The marketplaces of CloudBees Unify MCP Server publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of CloudBees Unify MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: SmartBear MCP · What it can do: CloudBees Unify MCP Server · Compare two other plugins
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.