AWS Labs Nova Canvas vs SlideForge
AWS Labs Nova Canvas is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). SlideForge is an MCP server published by slideforge.dev. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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 |  AWS Labs Nova Canvas |  SlideForge |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:5582496accaa Forks (GitHub): 1 806 Pulls (Docker Hub): 11 104 Stars (Docker Hub): 0 Stars (GitHub): 9 779 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 5.9.0 Downloads/month (PyPI): 227 Downloads/week (PyPI): 48 Forks (GitHub): 1 Stars (GitHub): 4 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 | AWS Labs Nova Canvas | SlideForge |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 9 779 (better) | 4 (worse) |
| Pulls (Docker Hub) (differs) | 11 104 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 806 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/nova-canvas-mcp-server) | Remote server (api.slideforge.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 2 | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 2 | 1, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 5 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/awslabs/mcp | github.com/smartdatabrokers/slideforge-mcp |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 46 h ago |
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 Labs Nova Canvas
AI image generation using Amazon Nova Canvas.
SlideForge
Deterministic, fully editable PowerPoint from typed slide intents. 200+ layouts, brand templates.
How to run each
AWS Labs Nova Canvas As a local MCP server: Docker image
claude mcp add --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --env "AWS_SESSION_TOKEN=<YOUR_AWS_SESSION_TOKEN>" --transport stdio awslabs-nova-canvas -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN mcp/nova-canvas-mcp-serverRequires: AWS_SECRET_ACCESS_KEY (secret), AWS_SESSION_TOKEN (secret)
SlideForge As a remote MCP server
claude mcp add --transport http slideforge https://api.slideforge.dev/mcp/Requires: SLIDEFORGE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only SlideForge has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of SlideForge publish no list of tools, so we do not compare tools.
Settings each asks for
Only AWS Labs Nova Canvas asks for
AWS_ACCESS_KEY_IDAWS_PROFILEAWS_REGIONAWS_SECRET_ACCESS_KEY (secret)AWS_SESSION_TOKEN (secret)
Only SlideForge asks for
SLIDEFORGE_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: AWS Labs Nova Canvas · What it can do: SlideForge · 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. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.