Ext Ops Panel
Open dashboard
Comparison

mcp-server-guide vs Polymation

mcp-server-guide is a plugin bundle for AI coding tools published by AnimaApp. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Polymation is an MCP server published by paradoxsyn. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
Marketplacemcp-server-guidePolymation
Claude Code: claude-plugins-community Listed
Version: 2.0.0
Forks (GitHub): 2
Stars (GitHub): 6
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.16.2
Downloads/month (npm): 2 917
Downloads/week (npm): 844
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

mcp-server-guide vs Polymation
Factmcp-server-guidePolymation
Marketplaces that list it11
Stars (GitHub) (differs)6 (better)1 (worse)
Forks (GitHub) (differs)2 (better)0 (worse)
Last release (differs)Not published2026-10-13
Where it runs (differs)Remote server (api.agentgrid.io/v1/mcp)On your machine (rivemcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)2Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/animaapp/mcp-server-guidegithub.com/paradoxsyn/rivemcp-releases
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 34 h ago, requires a keyno 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

mcp-server-guide

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

Build apps, clone websites, and implement Figma designs through Anima Playground. Describe what you want, paste a website URL, or drop in a Figma link. Anima handles design, code generation, database, and hosting. Publish to a live URL. Crate in parallel variant creation for rapid prototyping.

Polymation

In its own words, on Official MCP Registry:

Author Rive (.riv/.rev) and convert Lottie, After Effects, Figma and Spline into it, offline.

How to run each

mcp-server-guide As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mcp-server-guide@claude-community

Polymation As a local MCP server: npm package

Claude Code
claude mcp add --env "POLYMATION_LICENSE_KEY=<YOUR_POLYMATION_LICENSE_KEY>" --transport stdio rivemcp -- npx -y rivemcp

Requires: POLYMATION_LICENSE_KEY (secret)

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

Only mcp-server-guide 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 mcp-server-guide publish no settings it asks for, so we do not compare settings.

What it can do: mcp-server-guide · What it can do: Polymation · 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. 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