Ext Ops Panel
Open dashboard
Comparison

dev.agentbrush/mcp-server vs SVGApp

dev.agentbrush/mcp-server is an MCP server published by agentbrush.dev. Marketplaces we read that list it: 1 (Official MCP Registry). SVGApp is an MCP server published by Xyz3R. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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
Marketplacedev.agentbrush/mcp-serverSVGApp
Official MCP Registry Listed
Version: 1.1.1
Downloads/month (npm): 222
Downloads/week (npm): 38
Not marked · First seen
Listed
Version: 1.0.0
No figure published
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

dev.agentbrush/mcp-server vs SVGApp
Factdev.agentbrush/mcp-serverSVGApp
Marketplaces that list it11
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@agentbrush/mcp-server)Remote server (web.svgapp.ai/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/xz3dev/svgapp.ai
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 17 h ago

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

dev.agentbrush/mcp-server

In its own words, on Official MCP Registry:

On-brand image generation (product shots, app icons, OG cards, sprites) for AI coding agents.

SVGApp

In its own words, on Official MCP Registry:

Create consistent mascot assets and animations for products through AI agents.

How to run each

dev.agentbrush/mcp-server As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio dev-agentbrush-mcp-server -- npx -y @agentbrush/mcp-server

SVGApp As a remote MCP server

Claude Code
claude mcp add --transport http svgapp https://web.svgapp.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only SVGApp 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: dev.agentbrush/mcp-server · What it can do: SVGApp · Compare two other plugins

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