Ext Ops Panel
Open dashboard
Comparison

pptx-mcp vs designmark

pptx-mcp is an MCP server published by swak. Marketplaces we read that list it: 1 (PyPI (MCP servers)). designmark is an MCP server published by xecin-inc. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
Marketplacepptx-mcpdesignmark
PyPI (MCP servers) Listed
Version: 0.18.0
Downloads/month (PyPI): 974
Downloads/week (PyPI): 109
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Downloads/month (npm): 657
Downloads/week (npm): 82
Forks (GitHub): 0
Stars (GitHub): 0
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

pptx-mcp vs designmark
Factpptx-mcpdesignmark
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)On your machine (pptx-mcp)On your machine (designmark)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/swak/pptx-mcpgithub.com/xecin-inc/designmark
Changes in the last 7 days00
First seen (differs)2026-10-132026-10-24

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

pptx-mcp

In its own words, on PyPI (MCP servers):

AI-powered PowerPoint (.pptx) generation, editing, and review via MCP — 43 tools, 53 slide types, 12 chart types, 8 diagrams, 12 branded presets, 34 archetypes, 8 variant groups, image treatments (mask/duotone/overlay), proportional type-scale, dark-mode palettes, responsive aspect ratios (16:9/4:3/16:10), gradient presets, icon pack, financial primitives, and a 33-rule review engine with WCAG a11y, MECE/parallelism, data-provenance, auto-fix

designmark

In its own words, on Official MCP Registry:

Search and fetch Japanese landing-page design systems (DESIGN.md) from designmark.jp.

How to run each

pptx-mcp

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

designmark As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio designmark -- npx -y designmark mcp

Commands 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: pptx-mcp · What it can do: designmark · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). 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