Ext Ops Panel
Open dashboard
Comparison

keynot vs Krita Codex MCP

keynot is a plugin bundle for AI coding tools published by shawnzam. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Krita Codex MCP is an MCP server published by cyyprezz. Marketplaces we read that list it: 3 (Official MCP Registry, PyPI (MCP servers), Community GitHub marketplaces). As of our marketplace pass on 2026-10-24. 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
MarketplacekeynotKrita Codex MCP
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 1
Stars (GitHub): 15
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Downloads/month (PyPI): 654
Downloads/week (PyPI): 250
Forks (GitHub): 4
Stars (GitHub): 10
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.2.2
Downloads/month (PyPI): 654
Downloads/week (PyPI): 250
Forks (GitHub): 4
Stars (GitHub): 10
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

keynot vs Krita Codex MCP
FactkeynotKrita Codex MCP
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)15 (better)10 (worse)
Forks (GitHub) (differs)1 (worse)4 (better)
Last release (differs)Not published2026-10-23
Where it runs (differs)Installs as a plugin bundleOn your machine (krita-codex-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)12
LicenceMITMIT
Repository (differs)github.com/shawnzam/keynotgithub.com/cyyprezz/krita-codex-mcp
Changes in the last 7 days (differs)03
First seen2026-10-112026-10-11

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

keynot

In its own words, on Claude Code: claude-plugins-community:

A Claude Code skill that turns any prompt into a polished, self-contained HTML slide deck — keyboard navigation, swipe, fullscreen, animated reveals, brand-accurate design. Single file. Opens anywhere. No runtime dependencies. Built for the moment you need to present something and you don't want to open PowerPoint.

Krita Codex MCP

In its own words, on Official MCP Registry:

Control Krita through a secure local MCP server and authenticated Windows bridge.

How to run each

keynot As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install keynot@claude-community

Krita Codex MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio krita-codex-mcp -- uvx krita-codex-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: keynot · What it can do: Krita Codex MCP · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). 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.

Where the data comes from: how the catalog is built