Ext Ops Panel
Open dashboard
Comparison

pluginos-figma-operations-platform vs Anima MCP Server

pluginos-figma-operations-platform is a plugin bundle for AI coding tools published by LSDimi. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Anima MCP Server is an MCP server published by AnimaApp. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-16. 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
Marketplacepluginos-figma-operations-platformAnima MCP Server
Claude Code: claude-plugins-community Listed
Version: 0.8.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Forks (GitHub): 2
Stars (GitHub): 6
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

pluginos-figma-operations-platform vs Anima MCP Server
Factpluginos-figma-operations-platformAnima MCP Server
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)3 (worse)6 (better)
Forks (GitHub) (differs)0 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (pluginos)Remote server (public-api.animaapp.com/v1/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)24
Licence (differs)MITNot stated
Repository (differs)github.com/lsdimi/pluginosgithub.com/animaapp/mcp-server-guide
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 days ago, requires a key

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

pluginos-figma-operations-platform

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

Run any Figma operation from any LLM agent at ~230 tokens per call instead of ~28,000 — a 15× cost reduction on real design workflows. PluginOS bridges your Figma files to Claude, Cursor, Windsurf, or any MCP-compatible agent through 5 focused tools that discover operations on demand. No giant tool schemas bloating context. No raw node dumps confusing your agent. ⚠️ Requires the free PluginOS Bridge plugin running in Figma: 👉 https://www.figma.com/community/plugin/1626608701431483287 Open it once before your first agent call, it auto-reconnects after that. - 5 MCP tools, unlimited operations, discovered dynamically at runtime - ~6,600 tokens per multi-step workflow vs ~105,000 with traditional approaches - Pre-summarized, structured results: your agent reasons faster with less noise - 28 built-in operations: lint, audit, content, components, accessibility, more - Custom operations: add a manifest + execute pair, no server changes - Multi-file support: connect several Figma files at once Compatible with Claude

Anima MCP Server

In its own words, on Official MCP Registry:

Connect AI coding agents to Anima Playground, Figma, and your design system.

How to run each

pluginos-figma-operations-platform As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install pluginos-figma-operations-platform@claude-community

Anima MCP Server As a remote MCP server

Claude Code
claude mcp add --transport http anima https://public-api.animaapp.com/v1/mcp

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

Only Anima MCP Server 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: pluginos-figma-operations-platform · What it can do: Anima MCP Server · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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