Ext Ops Panel
Open dashboard
Comparison

monday.com vs com.mcparmory/miro

monday.com is a plugin bundle for AI coding tools published by mondaycom. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). com.mcparmory/miro is an MCP server published by mcparmory.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-11. 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
Marketplacemonday.comcom.mcparmory/miro
Claude: knowledge-work-plugins Listed
Version: 0.1.0
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
Downloads/month (PyPI): 817
Downloads/week (PyPI): 151
Forks (GitHub): 4
Stars (GitHub): 32
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

monday.com vs com.mcparmory/miro
Factmonday.comcom.mcparmory/miro
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)32 (better)
Forks (GitHub) (differs)1 (worse)4 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.monday.com/mcp)On your machine (mcparmory-miro)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)6Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/mondaycom/monday-claude-cowork-plugingithub.com/mcparmory/registry
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 25 h ago, requires authenticationno 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

monday.com

In its own words, on Claude: knowledge-work-plugins:

The official monday.com plugin for Claude Cowork. Manage boards, items, docs, and forms across work management, CRM, dev, service, and campaigns. Full read and write access via OAuth.

com.mcparmory/miro

In its own words, on Official MCP Registry:

Create and manage collaborative boards, items, and diagrams programmatically

How to run each

monday.com As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install monday-com@knowledge-work-plugins

com.mcparmory/miro As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio miro -- uvx mcparmory-miro

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

Only monday.com 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

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

What it can do: monday.com · What it can do: com.mcparmory/miro · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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