render vs Charming
render is a plugin bundle for AI coding tools published by render-oss. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community). Charming is an MCP server published by tambo-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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 |  render | |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 0.2.2 Forks (GitHub): 2 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Claude: knowledge-work-plugins | Listed Version: 0.2.2 Forks (GitHub): 2 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Listed Version: 0.2.1 Forks (GitHub): 2 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Forks (GitHub): 2 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 | render | Charming |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 (worse) | 4 (better) |
| Forks (GitHub) | 2 | 2 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.render.com/mcp) | Remote server (charm.ing/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 26 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/render-oss/render-plugin-claude-code | github.com/tambo-labs/charming-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check | not checked yet | not checked yet |
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
render
Deploy, debug, and monitor applications on Render. Includes skills, an agent, slash commands, and a render.yaml validation hook.
Charming
Build personal interactive apps with real URLs and persistent storage, using any AI.
How to run each
render As a Claude Code plugin
/plugin install render@claude-plugins-officialCharming As a remote MCP server
claude mcp add --transport http charming https://charm.ing/mcpCommands 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: render · What it can do: Charming · 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 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.