Ext Ops Panel
Open dashboard
Comparison

AWS Diagram vs PitchBoost

AWS Diagram is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). PitchBoost is an MCP server published by pitchboost.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
MarketplaceAWS DiagramPitchBoost
Docker MCP Catalog Listed
Version: sha256:453d5fc6b50b
Forks (GitHub): 1 855
Pulls (Docker Hub): 61 996
Stars (Docker Hub): 1
Stars (GitHub): 9 889
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.1
No figure published
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

AWS Diagram vs PitchBoost
FactAWS DiagramPitchBoost
Marketplaces that list it11
Stars (GitHub) (differs)9 889No figure on GitHub
Pulls (Docker Hub) (differs)61 996No figure on Docker Hub
Forks (GitHub) (differs)1 855No figure on GitHub
Last release (differs)Not published2026-10-22
Where it runs (differs)On your machine (mcp/aws-diagram)Remote server (app.pitchboost.ai/api/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)3Not published
Environment variables it asks forNot publishedNot published
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/mcpNot stated
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-16
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 43 h ago returned HTTP 405

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

AWS Diagram

In its own words, on Docker MCP Catalog:

Seamlessly create diagrams using the Python diagrams package DSL. This server allows you to generate AWS diagrams, sequence diagrams, flow diagrams, and class diagrams using Python code.

PitchBoost

In its own words, on Official MCP Registry:

Make or redesign presentations: lessons, reports, talks and pitches, in any language. Share links.

How to run each

AWS Diagram As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio aws-diagram -- docker run -i --rm mcp/aws-diagram

PitchBoost As a remote MCP server

Claude Code
claude mcp add --transport http pitchboost https://app.pitchboost.ai/api/mcp

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

Only PitchBoost has a remote endpoint we check. How we check endpoints

Tools each declares

Only AWS Diagram has

  • generate_diagram
  • get_diagram_examples
  • list_icons

Only PitchBoost has

  • create_deck
  • create_sample_deck
  • get_deck
  • get_rebuild_status
  • list_decks
  • publish_deck
  • rebuild_deck

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (PitchBoost as of 2026-11-04). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: AWS Diagram · What it can do: PitchBoost · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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