Skip to main content
Glama
741,983 tools. Updated 2026-11-04 13:58

"A platform for collaborative design and prototyping (Figma)" matching MCP tools:

  • Make one narrow, retry-safe edit to an existing collaborative session. After every attempt, the next Keyboardia call must be get_session for the same session. A successful call includes a backwards-compatible compact snapshot plus an acknowledgement. That snapshot is not authoritative verification; do not make another edit or finish from it. Read with get_session next. Supported operations: add_track, set_track_instrument, set_track_pan, set_steps, and set_tempo. set_steps changes only the named steps; it never replaces a track or session. set_track_instrument replaces only a track's sound source, keeping its pattern, mix, timing, and custom name.
    Connector
    Destructive
    No auth
  • Planning-time statistical power from a design's REAL model matrix — no data needed. Builds the design and takes `ncp = effect_size² / (X'X)⁻¹_jj`, so it is correct for centre points, axial points and unbalanced designs — unlike `covadoe_power_analysis`, which assumes orthogonality and overstates power on a CCD, Box-Behnken or DSD. Use this when planning an experiment; use `covadoe_post_hoc_power` only once you have measured responses. `design_type` + `n_factors` builds the design (same generator as `covadoe_create_design`, so the answer describes the design you would actually get). Common aliases resolve ("full_factorial", "ccd", "dsd"). Alternatively pass `design`, an explicit coded run matrix, to score a design you already hold — D/I-optimal, mixture, split-plot or hand-built. `n_runs` / `model_terms` are forwarded to the generator for the optimal designs. `model`: "linear" | "interaction" | "quadratic" | "quadratic_no_interaction" (a DSD supports only the last). `term` names the coefficient — "x1", "x1^2", "x1*x2"; omit it to get power for every term and group, which differ sharply on the same design. `alpha` is the significance level; the CCD axial distance is `axial_alpha`, and the two are easy to confuse. CCD variant: `axial_alpha` defaults to ROTATABLE, (2**n_factors)**0.25 — the design JMP, Design-Expert and Minitab hand you. Pass a number, or "orthogonal" for the α where Σx² = n_runs (at 3 factors: main-effect power 0.9400 against the rotatable 0.8846 on the same 17 runs; the orthogonal α is also the premise of `covadoe_power_analysis`, so on that design the two agree for a main effect and disagree for every other term). `face` — "circumscribed" (default), "faced" (star points on the faces, α = 1) or "inscribed"; a bool works, and an unknown value is rejected rather than quietly treated as circumscribed. Returns power, power_by_term, power_by_group, df_error, relative_variance ((X'X)⁻¹_jj), the resolved design_summary (the α and factorial level actually built — read both, an inscribed CCD always reports α = 1), and `orthogonal_shortcut_power` — what `covadoe_power_analysis` would have claimed — with its signed error (signed: the shortcut does not always overstate). Returns `estimable: false` plus a reason when the model cannot be fitted on the design.
    ConnectorAPI key
  • 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.
    ConnectorNo auth
  • Gets the status and result of a design generation job started by create-design. Pass the job_id and continuation_token from the previous create-design or get-async-job response. While the job is still running, wait the number of seconds the response's polling_policy.wait_seconds gives, then poll again with the same job_id and the updated continuation_token. Never poll sooner than that: it returns the same answer and the design arrives no earlier. Follow the polling_policy.instructions in every response, and relay them to the user while they wait. When the job completes, share the design link with them. When the completed response carries design.print.is_printable as true, and you are replying in text alone — no UI surface of your own rendering the design — then alongside the design link tell the user they can also order this design as a physical print with Canva Print and share design.print.print_url. Otherwise say nothing about printing: when print is absent or is_printable is false, there is nothing to do and nothing to relay. Never tell the user a design cannot be printed.
    ConnectorOAuth
  • Gets the status and result of a design generation job started by create-design. Pass the job_id and continuation_token from the previous create-design or get-async-job response. While the job is still running, wait the number of seconds the response's polling_policy.wait_seconds gives, then poll again with the same job_id and the updated continuation_token. Never poll sooner than that: it returns the same answer and the design arrives no earlier. Follow the polling_policy.instructions in every response, and relay them to the user while they wait. When the job completes, share the design link with them. When the completed response carries design.print.is_printable as true, and you are replying in text alone — no UI surface of your own rendering the design — then alongside the design link tell the user they can also order this design as a physical print with Canva Print and share design.print.print_url. Otherwise say nothing about printing: when print is absent or is_printable is false, there is nothing to do and nothing to relay. Never tell the user a design cannot be printed.
    ConnectorOAuth
  • Fallback upload for a design snapshot, for when the PUT to the `uploadUrl` from prepare_design_snapshot is blocked by the environment's network (for example "Host not in allowlist"). Takes the `uploadId` and the complete, self-contained design HTML, and hosts it under that uploadId. The design HTML is temporarily uploaded to TheySaid. Re-using an uploadId replaces the stored design. Returns { uploadId, previewUrl, nextStep }; the next step is check_design_snapshot. This tool does not start a test.
    Connector
    Destructive
    OAuth

Matching MCP Servers

Matching MCP Connectors

  • Move a design (or a board workspace) to the trash: it leaves list_designs and the web app, and restore_design brings it back for 7 days, after which it is removed for good. permanent removes it, its files and its session right away. Refused while a run on it is in progress. The CLI: `koppar delete <design>`.
    Connector
    Destructive
    No auth
  • Move a design (or a board workspace) to the trash: it leaves list_designs and the web app, and restore_design brings it back for 7 days, after which it is removed for good. permanent removes it, its files and its session right away. Refused while a run on it is in progress. The CLI: `koppar delete <design>`.
    Connector
    Destructive
    No auth
  • Pin one of a site's design variations onto a board so it can be presented and compared alongside other options. Boards are organization-owned and may already contain designs from other clients in the same organization. If the target board already has a public share link, the design becomes visible at that link immediately. Identify the design by `variation_index` (from list_variations) — or `variation_id` if you already have it. By default the design lands on the source site's client's main board; pass `board_name` to add it to a named board for that client (matched if one with that name exists, created if not), or `board_id` to target any specific existing board in your organization, including a board owned by another client. Optional `display_label` sets the client-facing name shown for the design on the board (e.g. "Bold & Dark"). Pinning the same design twice is a harmless no-op. Returns the board id/name, the pinned item id, and the board's public share link when it has one.
    Connector
    Destructive
    OAuth
  • Use this to have Tailwind's AI generate a NEW design for an AI-designed (premium) Pin. Asynchronous and metered: it spends about 7 of the user's plan credits, takes a few minutes, and returns an id to poll with get_design_regeneration_status. Only works when get_pin_design lists "regenerate" in supportedOperations. Because it spends the user's credits, confirm with the user before calling it, and say what it will cost. Calling it again after one finishes starts and charges ANOTHER regeneration, so poll before retrying. The result does NOT replace the Pin's design on its own: a finished regeneration returns a variationUrl that you then pass to select_pin_design_variation. Tell the user the new design is ready and let them choose, rather than applying it silently. Afterwards get_pin_design reports workspaceStatus pending_apply with the new design as pendingMediaUrl; that is the expected resting state, not a failure, and it stays that way until the user picks the design. To REVISE the design the Pin already has, rather than replace it, pass selectedVariationUrl as well: the active variation's templateImageUrl from get_pin_design. Without it the generator has nothing to revise and produces an unrelated design for the same credits, which is rarely what someone asking to adjust their current design wants. If the user did not say which Pinterest account to use and list_accounts returns more than one, ask the user which account to use before calling this — do not choose for them.
    ConnectorOAuth
  • Returns the signed-in account's plan and today's usage: Pro prompt access or Prompt Pack credits left, UI generations used and the daily limit, AnimatedWebs Design AI requests used and the daily limit, links to pricing, the UI library and Design, and a design section with the Design workspace URL. Set includeDesignConnect to true to also get ready-to-paste configuration for connecting the separate AnimatedWebs Design MCP server to Claude Code, Cursor and VS Code; that part contains a personal bearer token that opens the user's private workspace, so do not write it to shared files or repositories. Use this to check whether a Pro template, generate_component or refine_component call will succeed before making it, or to set up Design; use get_pricing for plan prices instead. Counts are per UTC day. Read-only; errors when not signed in.
    ConnectorOAuth
  • Fetch the full record for a single creator by ID or exact platform username. Use this when you already have either: - a canonical creator UUID returned by `search_creators`, `semantic_search_creators`, `autocomplete_creators`, or `find_lookalike_creators`; or - an exact platform+username pair such as platform "instagram" and username "niickjackson". Pass `include: ['profiles']` to also receive the creator's social profile summaries when using a creator UUID. For platform+username inputs, this tool resolves through the profile endpoint and returns the profile record plus the underlying creator record, so you already get the matched profile context. Examples: - User: "Get creator 123e4567-e89b-12d3-a456-426614174000" -> call with id. - User: "Get @niickjackson on Instagram" -> call with platform "instagram" and username "niickjackson", or use `get_profile` if profile metrics are the main need. - User: "Tell me about @niickjackson and include his profiles" -> use platform "instagram" and username "niickjackson"; then use `get_profile`/`get_posts` for platform-specific metrics and content if needed. Use `lookup_profiles` for batch exact profile lookups.
    ConnectorNo auth
  • Fetch the full record for a single creator by ID or exact platform username. Use this when you already have either: - a canonical creator UUID returned by `search_creators`, `semantic_search_creators`, `autocomplete_creators`, or `find_lookalike_creators`; or - an exact platform+username pair such as platform "instagram" and username "niickjackson". Pass `include: ['profiles']` to also receive the creator's social profile summaries when using a creator UUID. For platform+username inputs, this tool resolves through the profile endpoint and returns the profile record plus the underlying creator record, so you already get the matched profile context. Examples: - User: "Get creator 123e4567-e89b-12d3-a456-426614174000" -> call with id. - User: "Get @niickjackson on Instagram" -> call with platform "instagram" and username "niickjackson", or use `get_profile` if profile metrics are the main need. - User: "Tell me about @niickjackson and include his profiles" -> use platform "instagram" and username "niickjackson"; then use `get_profile`/`get_posts` for platform-specific metrics and content if needed. Use `lookup_profiles` for batch exact profile lookups.
    ConnectorNo auth
  • Lists every UI component in the project's design system, each with its name, source package, import path, and a short note on its intended use. Read-only and unpaginated: it returns the whole catalog across all packages assigned to the project, so expect a large response on big design systems. Use it to see what exists before building UI, and to get the exact component name other tools need. Do not use it to find a component by need - search_components ranks by description - and do not use it for props, examples, or Figma data, which only get_component returns. project_id is not a display filter: it selects the assigned packages, so two projects in one organization legitimately return different catalogs.
    ConnectorNo auth
  • Convenience tool: generates a post with AI (postType 'CAROUSEL' by default, 'IMAGE' for a single-image post, or 'VIDEO' for a video), waits for it to finish, then creates a scheduled post that attaches the resulting design. May take 30-180 seconds (longer for a rendered video). templateId, brandId, presetId, and responseType are optional if saved via postnitro_set_defaults. The design that gets attached is the completed carousel's design ID (result.designId from the generation output) — NOT the generation job ID. You normally don't set designId; it's resolved automatically. Pass designId only to attach a pre-existing design instead of the freshly generated one. If scheduling fails after the carousel is already generated (e.g. an invalid platform-settings combination), this tool returns the generated designId so you can fix the inputs and retry with postnitro_create_scheduled_post — WITHOUT regenerating (which would burn credits again). Provide the scheduling fields (status, scheduledAt, selectedAccounts, captions, and any required per-platform settings) just as you would for postnitro_create_scheduled_post.
    ConnectorAPI key
  • Explain how Context Studios prices projects: the entry point is a fixed-price workshop (Light Discovery, Strategy Day, or Prototyping Sprint — see the returned `workshops` list), project prices follow scoping with a 48-hour proposal turnaround. Returns the three workshop prices, the phases from discovery to sprint, and what drives the project price. No project price ranges or amounts beyond the workshops — call get_services for what each package includes, and request_consultation or book a call for a project-specific quote.
    ConnectorNo auth
  • The design contract: what a valid Electronics Architect design document looks like. Call with no arguments for the units policy, the top-level shape and the list of every node type. Call with a `type` for that type's full property set — key, unit, default, allowed range and what it means. ALWAYS read this before writing a design by hand: numbers are SI base units with no prefix (0.0006 for 600 µA, 47e-6 for 47 µF) and are JSON numbers, never strings, and unknown property keys are rejected rather than ignored.
    ConnectorAPI key
  • Generates and compares at least two fundamentally different design alternatives on concrete criteria before committing. Use when the user asks to design something twice, or before committing to any significant design of classes, modules, APIs, or architecture. Also use when asked how to structure or architect a feature, or when writing the design or alternatives section of an RFC, design doc, or ADR. Not for judging strategic vs. tactical investment in existing code (use strategic-mindset) or whether a change degrades design (use code-evolution).
    ConnectorNo auth
  • Create a NEW site whose active design is a layout YOU author: pass `business` (name + industry + description), `content` (structured, keyed by section), `files` (self-contained TSX components; exactly one page with slug "/"), and optional `collections` (catalog types like menu/products with sampleItems). Mondovo validates, rehosts images to its CDN, and stands the site up in the design-selection phase — the user compares/confirms designs there (add alternatives via import_design_variation or generate_design_variation) before the site is forked to build. Returns a site_id; poll get_site until status is "ready". For a normal brief-based site, use create_site instead. AUTHORING CONTRACT (see files[].code): author brand colors as var(--color-*) CSS variables so the design is theme-swappable, and prefer @/components/Runtime* platform components (forms, catalog, gallery) over hand-built equivalents — workflow components (portal/funnel/cart/payment/booking) need owner activation, so add those via refine_site rather than authoring them here.
    ConnectorOAuth
  • Return render feedback for a design variation: its screenshots (desktop + mobile), the distinct browser errors real visitors have hit, and static contrast advisories naming any text/background pair below WCAG AA. Use this to self-check an import instead of asking a human to look at it. NOTE: screenshots and errors are historical — a design imported seconds ago has no screenshot and has never run, so those come back empty; the contrast pass works immediately because it reads the code. Omit `index` for the active design.
    ConnectorOAuth
  • Render one design variation NOW and attach its screenshot, so you can check a design you just imported or edited before showing it to anyone. Takes about 30-40 seconds; a design that already has a render answers at once (send `force: true` after an edit to render it again). Use this instead of waiting when list_variations says thumbnails are pending or get_render_diagnostics has no screenshot. Omit `index` for the active design.
    ConnectorOAuth