"Figma – Collaborative Design and Prototyping Tool" matching MCP tools:

• get_design_system

  Mozaika

  Get a product's full, LLM-verified design system so you can match its exact look. Use this for "design like <product>" (e.g. site="Linear", "Stripe", "Figma"). Returns (default): color_scheme; colors with named roles (background, text, primary, secondary, accent, link, button_bg, button_text); fonts + font_roles; type_scale; spacing; primary/secondary button; framework + personality. All hex normalized. Deep-decoded products additionally include measured button hover/focus states, a shadow elevation scale (card/overlay/subtle), motion durations + easings, the measured spacing scale, the brand's own CSS custom properties (css_vars), and Icon DNA (icons: style outline/filled/duotone/3d, grid, stroke_weight, corner) — all measured from the live page, not guessed. Match them exactly; pass the domain to generate_asset(style_from=...) to strike icons in this exact style. Your own private BYODS design systems (call list_my_design_systems) resolve first. format: leave empty for the raw token dict. Pass "all" to also get paste-ready DESIGN.md / Tailwind v4 / CSS variables / W3C tokens JSON, or a single format name ("tailwind", "css", "design_md", "tokens", "astryx") to get just that text. "astryx" returns a ready Meta-Astryx defineTheme TypeScript file (measured hover/press states + [light,dark] tuples baked in) — save it and run `npx astryx theme build` for production CSS.

  Connector

• designesy_readiness_score

  Designesy

  Score a URL for design-system AI readiness — the 6th maturity axis (zeroheight 2026). 10 checks probe the target origin for machine-readable artifacts: DTCG token files, llms.txt, agent.json, MCP endpoint (tools/list), DESIGN.md, token $description, component schemas, sitemap.xml, robots.txt, and Open Graph/Twitter meta. Use this to verify whether a design system is the default context AI tools build from, or whether AI is silently working around it. When NOT to use: for full design-contract scoring, use designesy_score; for AI-drift detection, use designesy_drift_score. Executable — fetches the URL and probes the origin via HEAD/GET for each artifact. No browser needed. Returns JSON: { ok, url, score (0-100), grade (A-F), pass, warn, fail, total, checks[{id, item, category, status, detail}] }. Results cached ~24h per URL.

  Connector

• compose_landing

  Layero

  Drive the 3-step quiz flow and produce a complete landing. This is the **main entry point**. Don't ask the user questions in chat before calling this — the tool opens native quiz dialogs in the IDE itself. Call this immediately when the user describes what they want. The three quizzes are: 1. **Motivation** — what's being built, for whom, the desired action. 2. **Look & feel** — palette, tone, optional references. 3. **Final picks** — design system (top 3 matched), where submissions go, project name slug. Returns a ``ComposeResult`` with the file bundle to write to disk. The agent then writes the files using the IDE's filesystem tool and proceeds to integration setup / deploy.

  Connector

• create_mail_quote

  PostAgent

  Verifies the recipient and sender US addresses and locks a 15-minute USDC price for a documentId. Does not charge or mail anything. Returns a `paymentUrl` (a per-quote x402-payable URL); the preferred way to actually mail the letter is for the agent's wallet to perform an in-band x402 payment against that URL (e.g. `npx awal@latest x402 pay <paymentUrl>`). The MCP `submit_paid_mail_job` tool is a fallback for clients that can emit a standalone signature header. In all cases, show the recipient, sender, options, selected-route `design` constraints, price, AND any `fulfillment.warnings` to the user and get explicit confirmation before paying. The response includes a `fulfillment` block with `requested` (what you asked for), `selected` (what will actually be printed/mailed) and `warnings` (any soft-preference downgrades — e.g. `service_level_downgraded` or `extra_service_unavailable`); do not pay through a non-empty warnings list without re-confirming the trade-off with the user. The response also includes a provider-neutral `design` block; inspect it and the preview before paying because the selected delivery method determines print address/no-ink zones.

  Connector

• designesy_design_review

  Designesy

  Get the Designesy Design Review framework — an 8-dimension rubric (Purpose, Clarity, Context, Inclusion, System coherence, Durability, Delight, Responsibility) plus the agent prompt, output format, and verification checklist for a qualitative design critique. Use this when you want a structured rubric to critique a design holistically, rather than a numeric compliance score. When NOT to use: for a deterministic numeric score, use designesy_score; this tool gives you a rubric, not a number. Read-only — returns the rubric + prompt. The calling agent performs the actual critique (this tool does not evaluate the design for you). Returns JSON: { rubric, dimensions[8], agent_prompt, output_format, verification_checklist }. Pass artifact/purpose/context/rules to get a pre-filled critique prompt; omit all four to get the blank framework.

  Connector

• designesy_compare

  Designesy

  Diff two design systems from live URLs — the only URL-scoped design-token diff engine. Fetches both URLs in parallel, extracts their :root custom properties, and produces a structured diff across 8 dimensions: tokens added (in A not B), removed (in B not A), renamed (heuristic Levenshtein ≤ 2), value-changed (same name, different value), scale-stop-changed (spacing/radius/color scale steps), contrast-drift-per-pair (WCAG contrast ratio change for shared color tokens), structure-delta (token count + category distribution), and score-delta (runs /score on both URLs and diffs). Use this to answer "what actually changed between two design systems" or "how does our design system differ from a reference". When NOT to use: for single-site drift detection, use designesy_drift_score; for continuous monitoring, use designesy_monitor_score. Executable — fetches both URLs, extracts CSS + tokens, computes diff. No browser needed. Returns JSON: { ok, urlA, urlB, score (0-100, diff completeness), grade, pass, warn, fail, total, tokensA, tokensB, added[], removed[], renamed[], valueChanged[], scaleDiff, structureDelta, contrastDrift[], scoreDelta, checks[] }. Results cached ~24h per URL pair.

  Connector

• get_fabrication_quote

  Agent Fabrication Network (UFP)

  Get ranked, purchasable offers (price, ETA, preview image) for fabricating a physical item from a design file. process=fdm_print for 3D printing a model (STL/OBJ/PLY/3MF/AMF/STEP/IGES), process=cnc or process=sheetmetal for machined/bent metal parts (STEP, IGES, DXF), process=decal for stickers/decals from artwork (any common image or design file — PNG/JPG/HEIC/TIFF/GIF/BMP/WEBP/AVIF/SVG/PDF/AI/EPS/PSD/CDR, auto-converted). A .ufp file (UFP part container: the design plus saved spec/constraints in one) is accepted anywhere a design file is — its saved intent applies automatically and anything the user states now wins. If the user just drops a file and asks for a price, omit process — UFP routes it. Provide the design either as design_file (an image/file the user attached or you generated — preferred) or file_url (a public URL). REORDERS: if the user has a UFP part number (from a receipt email or a previous session, looks like UFP-… or part_…), pass it as part_number INSTEAD of any file — the stored design and spec are reused and re-shopped across all current vendors. Locked parts additionally require share_key (from the owner's share link). Returns offers across vendors like Google Flights returns flights.

  Connector

• get_design_history

  Mozaika

  Measured design CHANGE HISTORY for a live-decoded domain — the Decode Ledger. Token-level diffs between deep decodes over time: "radius 4px→8px", "primary hover #4032C8→#0A2540", "motion dominant 150ms→200ms", each dated. Use it to see how a product's design system is EVOLVING (no screenshot library can backfill this). site = a domain ("stripe.com") or product name. Returns first/last decode dates, decode_count and the dated change entries; empty history = measured, stable so far.

  Connector

• plan_build

  space0

  Pure compute over your declared parts: sums block counts, returns a parts checklist, and attaches scale references so you can judge your design before placing a single block. You declare the parts; this computes block counts + scale references. It does not invent geometry. Workflow: call plan_build first to get target_blocks + scale_refs, then call set_goal(description, target_blocks, footprint, height) to persist the plan — set_goal is where plan metadata is stored. Returns { target_blocks, parts_checklist, scale_refs, overlap_warning? }. goal_id is accepted but is a no-op in this tool; persistence happens via set_goal.

  Connector

• create_mail_quote

  PostAgent

  Verifies the recipient and sender US addresses and locks a 15-minute USDC price for a documentId. Does not charge or mail anything. Returns a `paymentUrl` (a per-quote x402-payable URL); the preferred way to actually mail the letter is for the agent's wallet to perform an in-band x402 payment against that URL (e.g. `npx awal@latest x402 pay <paymentUrl>`). The MCP `submit_paid_mail_job` tool is a fallback for clients that can emit a standalone signature header. In all cases, show the recipient, sender, options, selected-route `design` constraints, price, AND any `fulfillment.warnings` to the user and get explicit confirmation before paying. The response includes a `fulfillment` block with `requested` (what you asked for), `selected` (what will actually be printed/mailed) and `warnings` (any soft-preference downgrades — e.g. `service_level_downgraded` or `extra_service_unavailable`); do not pay through a non-empty warnings list without re-confirming the trade-off with the user. The response also includes a provider-neutral `design` block; inspect it and the preview before paying because the selected delivery method determines print address/no-ink zones.

  Connector

• view_dxf

  Aspicio

  Open an interactive viewer the user can pan, zoom, and toggle layers in (renders in-chat on MCP Apps-capable hosts). Reads DXF and vector PDF; for a PDF it shows line work and text rather than a page facsimile, so images, shadings, and transparency are absent by design. Use this when the user wants to see or explore the drawing themselves; for your own analysis use a describe_* tool (facts) or a render_* tool (image). The viewer shows only the drawing from this call. Delivery is handled by the widget itself: small drawings are embedded in the result and larger URL-sourced drawings are fetched by the widget through its own tool call — never re-fetch or inline the file for the viewer's sake, and don't blind-retry if the user reports an empty viewer (the viewer posts its actual status back to the conversation context).

  Connector

• set_design_overview

  Forge Engine

  Write the Design Document's Overview — the human-readable page a new team member reads first. WRITES DIRECTLY (no Inbox): it is a derived, clearly-labelled AI summary, not design truth, and the owner can clear or rewrite it in one click. HARD RULES, same as the in-app button: use ONLY facts stated in the design (call get_design_document with for_summary:true first); invent no mechanics, numbers or names; describe, never evaluate; write in the design's dominant language. Structure: `### What this is` · `### The core loop` · `### How the systems fit` (which system feeds which — the part a raw spec list cannot give) · `### Edges` (ONLY if the design states scope limits / open questions). 250-400 words, no top-level heading. Forge stamps the project version it was compiled from, so the owner is told when the design has moved past it.

  Connector

• get_services

  turva-mcp

  Returns turva.dev's service catalog: agent-readiness audit, advisory, implementation, agent operations, and MCP server design, plus the engagement model and pricing (fixed list prices for audit, advisory and implementation; agent operations and MCP server design on request). Use this when a user asks what turva.dev offers, what it costs, or how an engagement works. Read-only: returns static JSON and changes nothing.

  Connector

• get_clinical_trial

  Scite

  Fetch full details for a single clinical trial by NCT id. Use this after `search_clinical_trials` when you need the complete record for a specific trial, including the full `description`, study `design`, `enrollment`, `outcomes` (primary/secondary), full `eligibility` inclusion/exclusion criteria, `reportedEvents` (adverse events when the trial has posted results), principal investigator (`pi`), `contacts`, `citations` (related publications), and `resultsUrl`. The search tool returns a slim summary to save tokens; call this tool for a specific NCT id when you need those verbose fields for deeper analysis or patient-trial matching. **Parameters:** - id: NCT identifier (e.g. `NCT02986230`). **Returns:** A compact detail record preserving all trial fields except the low-signal `ontology` classifications.

  Connector

• get_service_packages

  Clutch.co

  Use this tool when the user wants to see service packages with fixed pricing and scope for a specific type of service. This tool returns standardized packages offered by service providers, including pricing tiers, deliverables, and delivery timelines. Do NOT use this tool for custom project questions (e.g. "How much would it cost to build a custom app?"). It only returns providers' pre-defined, fixed-price packages, not a quote tailored to a specific project; use recommend_service_providers for those needs instead. Examples: - "Show me SEO packages" -> service="SEO" - "What web design packages can I get for $5,000?" -> service="Web Design", budget=5000 - "Marketing packages from agencies in New York" -> service="Digital Marketing", location="New York" Use `page`/`limit` for pagination.

  Connector

• render_slides

  Slidev MCP

  Render a Slidev presentation from markdown and return its hosted URL. IMPORTANT: Before calling this tool, you MUST call get_theme with the theme name you plan to use. Each theme has unique layouts, components, and frontmatter options. Apply the theme's specific features in your markdown to produce high-quality slides that match the theme's design. If the user has not specified a theme, call list_themes to pick one. If you are unfamiliar with Slidev markdown syntax, call get_slidev_guide. Images must be remote URLs or base64-encoded inline. Local file paths are not supported.

  Connector

• colour_passports

  Colour Memory

  Batch version of colour_passport. Submit up to 20 hex values in one call. Returns a full Colour Passport for each unique hex: colour science, archive anchor, evidence grade, do_not_say constraints, hex provenance, accessibility, and physics. Deduplicates hex values automatically. Use for multi-colour workflows, Figma palette analysis, or any case where calling colour_passport separately for each colour would be slow.

  Connector

• sygnl47_subscription_plans

  sygnldata — market intelligence for trading agents

  FREE: prepaid-pass plans for SYGNL/47 (the subscription catalog). x402 is per-call by design. A subscription here is a PREPAID TIME-BOXED PASS on the same rails: one payment buys unmetered access to one tier for one window and returns a signed bearer token, which you then send as X-SYGNL47-TOKEN instead of paying per call. Lists each plan with its tier, duration, price and the exact routes it authorizes. Read this before calling any sygnl47_subscribe_* tool.

  Connector

• designesy_contract

  Designesy

  Get the Designesy design-system contract — the canonical tokens, motion, acoustic, takt, cadence, typography, components, and verification rules that define what the Designesy org considers legitimate design. Use this when you need the actual contract values (token names and values, motion timings, accessibility rules) to author, check, or bind a design. When NOT to use: for a pass/fail score of a live site, use designesy_score; for an agent-skill-format export, use designesy_skill_md. Read-only — cached ~24h server-side. Returns the full contract JSON, or a single section when "section" is provided. Pass section to get one slice (e.g. "motion" for just the motion tokens) instead of the full contract — saves tokens when you only need one dimension.

  Connector

• render_motion_tool

  motion-tools

  Render a customized MP4 with a Mographr free tool. Pass the tool slug, optional variantId (a design-system variant from get_motion_tool; defaults to the tool's default variant), optional colorSchemeId, and `fields` — the text values keyed by field key. Returns a renderId to poll with get_motion_render plus the interactive page URL. Free renders carry a small mographr.com watermark and take ~1–3 minutes on the CPU render lane.

  Connector