Ext Ops Panel
Open dashboard
Comparison

Qovery MCP Server vs Containerization Assist

Qovery MCP Server is an MCP server published by qovery.com. Marketplaces we read that list it: 1 (Official MCP Registry). Containerization Assist is an MCP server published by Azure. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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

Where each is published
MarketplaceQovery MCP ServerContainerization Assist
Official MCP Registry Listed
Version: 1.0.1
No figure published
Not marked · First seen
Listed
Version: 1.5.0
Downloads/month (npm): 2 199
Downloads/week (npm): 359
Forks (GitHub): 20
Stars (GitHub): 43
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

Qovery MCP Server vs Containerization Assist
FactQovery MCP ServerContainerization Assist
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub43
Forks (GitHub) (differs)No figure on GitHub20
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp-api-ai.qovery.com/mcp)On your machine (containerization-assist-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/azure/containerization-assist
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 404 (18 h ago)no remote endpoint we check

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

Qovery MCP Server

In its own words, on Official MCP Registry:

Deploy apps and manage Kubernetes on AWS, GCP, Azure, and On-Premise with natural language.

Containerization Assist

In its own words, on Official MCP Registry:

TypeScript MCP server for AI-powered containerization workflows with Docker and Kubernetes support

How to run each

Qovery MCP Server

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Containerization Assist As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio containerization-assist -- npx -y containerization-assist-mcp start

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Qovery MCP Server 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

The marketplaces of Qovery MCP Server publish no settings it asks for, so we do not compare settings.

What it can do: Qovery MCP Server · What it can do: Containerization Assist · Compare two other plugins

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.

Where the data comes from: how the catalog is built