blueprint-trigger vs Figma MCP Server
blueprint-trigger is a plugin bundle for AI coding tools published by DanielaGallardoio. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Figma MCP Server is an MCP server published by oabolade. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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 |  blueprint-trigger |  Figma MCP Server |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.1.0 Downloads/month (npm): 102 Downloads/week (npm): 17 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 | blueprint-trigger | Figma MCP Server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@oabolade-pegasus/figma-mcp-server) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/danielagallardoio/blueprint-trigger | github.com/oabolade/figma_mcp_server_actor |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
blueprint-trigger
Blueprint Trigger helps product and design teams capture incoming requests clearly before anyone opens Figma. It acts as a structured intake interviewer — asking the right questions, detecting ambiguous or mixed requests, and producing a ready-to-use Trigger card. This is Step 1 of the Blueprint Hub methodology, designed for teams working under pressure, especially when the Design System is still being built. The skill adapts automatically to three roles: Designer, Product Manager, and Functional Analyst. Works in English and Spanish.
Figma MCP Server
MCP server enabling AI assistants to interact with Figma designs via natural language commands
How to run each
blueprint-trigger As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install blueprint-trigger@claude-communityFigma MCP Server As a local MCP server: npm package
claude mcp add --env "FIGMA_ACCESS_TOKEN=<YOUR_FIGMA_ACCESS_TOKEN>" --transport stdio figma-mcp-server-actor -- npx -y @oabolade-pegasus/figma-mcp-serverRequires: FIGMA_ACCESS_TOKEN (secret)
Commands 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
The marketplaces of blueprint-trigger publish no settings it asks for, so we do not compare settings.
What it can do: blueprint-trigger · What it can do: Figma 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 public marketplace files in GitHub repositories of their authors. 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.