miro vs Junê
miro is a plugin bundle for AI coding tools published by miroapp. Marketplaces we read that list it: 4 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community, Community GitHub marketplaces). Junê is an MCP server published by Junemind. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-10-26. 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 |  miro |  Junê |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 2.0.0 Forks (GitHub): 24 Stars (GitHub): 164 Not marked · First seen |
Not listed |
| Claude: knowledge-work-plugins | Listed Version: 2.0.0 Forks (GitHub): 24 Stars (GitHub): 164 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Listed Version: 1.3.0 Forks (GitHub): 24 Stars (GitHub): 164 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.8.1 Downloads/month (PyPI): 3 414 Downloads/week (PyPI): 2 493 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.8.1 Downloads/month (PyPI): 3 414 Downloads/week (PyPI): 2 493 Forks (GitHub): 0 Stars (GitHub): 1 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 | miro | Junê |
|---|---|---|
| Marketplaces that list it (differs) | 4 (better) | 2 (worse) |
| Stars (GitHub) (differs) | 164 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 24 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.miro.com) | On your machine (june-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 13, secrets among them: 2 |
| Parts of the bundle (differs) | 8 | Not a bundle |
| Licence (differs) | MIT | LicenseRef-Junemind-EULA |
| Repository (differs) | github.com/miroapp/miro-ai | github.com/junemind/june-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 3 days ago, requires a key | no 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
miro
Secure access to Miro boards. Enables AI to read board context, create diagrams, and generate code with enterprise-grade security.
Junê
Shared, cited knowledge-graph memory for agents — ask, search, remember, keep standing instructions
How to run each
miro As a Claude Code plugin
/plugin install miro@claude-plugins-officialJunê As a local MCP server: PyPI package
claude mcp add --env "JUNE_API_KEY=<YOUR_JUNE_API_KEY>" --env "JUNE_BASE_URL=<YOUR_JUNE_BASE_URL>" --env "JUNE_CANVAS=<YOUR_JUNE_CANVAS>" --env "JUNE_LLM_KEY=<YOUR_JUNE_LLM_KEY>" --transport stdio june-mcp -- uvx june-mcpRequires: JUNE_API_KEY (secret), JUNE_BASE_URL, JUNE_CANVAS, JUNE_LLM_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only miro 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
The marketplaces of miro publish no settings it asks for, so we do not compare settings.
What it can do: miro · What it can do: Junê · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.