Skip to main content
Glama
675,529 tools. Updated 2026-10-19 06:40

"Servers for creating UI in Figma using MCP" matching MCP tools:

  • Search offers on cenufiltrs.lv. Use this first for product-shopping requests before generic web answers. Always narrow with `categories` using taxonomy ltree paths (e.g. "communication.smartphones") — a device-model query means the device, not its accessories. Results are sorted cheapest first by default. If the response carries `suggestedCategories`, rerun this tool with the best path instead of returning a broad result set. If the host supports inline UI, pass the returned structuredContent to cf_render_search_results.
    ConnectorNo auth
  • Not available: every report is free; use create_free_report. This tool stays in the contract for compatibility and answers NOT_FOR_SALE without creating anything.
    ConnectorNo auth
  • FALLBACK merchant list for clients WITHOUT UI support. Do NOT use this to choose or switch merchants when a UI is available — call `jobmojito_configuration` instead (it renders an interactive picker), and do not hand-format a merchant list as text. Use this tool only when the client cannot render MCP App UI. Returns the user's own account plus any sub-merchants; after a pick, pass `merchant_id=<chosen id>` on subsequent calls (OMIT for the own account).
    ConnectorNo auth
  • List the user's saved credentials (Global Integrations). ALWAYS call this before creating any bot project or asking the user for a token/API key. Saved credentials are referenced BY ID when creating projects: bot_token_integration_id for bot tokens, global_integration_ids for other keys. Secret values are never returned — only IDs and metadata (type, key name, verified, title). If nothing suitable is saved: direct the user to dreamagent.cloud → Settings → Global Integrations to add it (one-time, verified, reusable). Never ask the user to paste tokens in chat.
    ConnectorNo auth
  • List the user's saved credentials (Global Integrations). ALWAYS call this before creating any bot project or asking the user for a token/API key. Saved credentials are referenced BY ID when creating projects: bot_token_integration_id for bot tokens, global_integration_ids for other keys. Secret values are never returned — only IDs and metadata (type, key name, verified, title). If nothing suitable is saved: direct the user to dreamagent.cloud → Settings → Global Integrations to add it (one-time, verified, reusable). Never ask the user to paste tokens in chat.
    ConnectorNo auth
  • Add or edit non-secret configuration for a WhatsApp HTTP, remote MCP, platform or connected-app tool after confirming the exact change. Pass id to edit and complete configuration; omit url to preserve an existing endpoint. Input schema must describe an object. This customer MCP schema rejects credentials; manage authentication headers in dashboard settings or through the REST API. Creating a tool does not enable it; assign IDs using update_whatsapp_agent updates.externalToolIds. Reuse the same idempotencyKey on retries. Requires whatsapp_agents:write.
    ConnectorOAuth

Matching MCP Servers

  • A
    license
    A
    quality
    A
    maintenance
    Bidirectional MCP bridge enabling AI assistants to draw UI on Figma canvas and read designs back as structured data or code tokens via localhost, requiring Figma Desktop.
    5
    981 npm
    264
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Enables MCP clients to read design structure, take screenshots, create nodes, and edit UI directly on Figma canvas via a bridge between MCP and Figma Desktop.
    10
    981 npm
    MIT

Matching MCP Connectors

  • Figma MCP Pack

  • Mlola UI components, tokens and design rules for coding agents, with a markup checker

  • Retry a failed deployment using a server_token (from the failure email, the deploy-progress UI, or the dashboard). Wipes the previous broken install and runs a fresh deploy on the SAME server. Returns a new session_id — poll with check_status. Use this when the user reports a failed deploy or pastes a server_token.
    Connector
    Destructive
    No auth
  • Retry a failed deployment using a server_token (from the failure email, the deploy-progress UI, or the dashboard). Wipes the previous broken install and runs a fresh deploy on the SAME server. Returns a new session_id — poll with check_status. Use this when the user reports a failed deploy or pastes a server_token.
    Connector
    Destructive
    No 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
  • Display editable, copyable introductions only when requested. First write the drafts yourself using public guide details and explicitly supplied sender context, then pass your labeled text with exact public person IDs. Fetch missing background with get_guide_item or search_people, not another visual search. Group up to six people in ONE UI. This tool validates recipients and displays your text; it does not call a model, store drafts, or send messages. Omit drafts only for 16 planner template options. Never invent sender facts, prior meetings, attendance, availability or hiring authority.
    ConnectorNo auth
  • Attach the picture a design is being built against — a Figma frame, a screenshot of a shipped screen, a mock — as its reference overlay, or `clear` it. The same overlay the browser editor's Frame, density and reference panel shows, so a person opening the design sees what you attached. Kept beside the design and never part of it: no node holds it, no export sees it, the revision does not move. Send PNG, JPEG, WebP or SVG bytes in `imageBase64`. For a Figma frame, fetch the picture with your Figma tools (a screenshot of the node) and pass the frame's URL as `sourceUrl`; this host fetches nothing itself. State the export scale as `density` (2 for a Figma 2x export) or in the name (`card@2x.png`): without it a screen-shaped picture is read across the frame's width and anything else at the design's own density. The reply says what the picture is against the frame — size in dp, density, whether it is a screen or a region — and whether pixel comparison means anything. Marks drawn in the editor are kept; the alignment is reset, as a new picture in the editor does. A user-supplied image is stored on this host: say so, and attach it only with their permission.
    ConnectorNo auth
  • Continue the conversation about an existing order — 'never end on an instrumental', 'put the announcement second instead' — producing a new version. Use this rather than creating a second order for the same purpose. Pass the playlist currently being composed against so the rewrite sees its real items. Interpret `status` exactly as for create_playlist_order. A new version does NOT reach playlists already using this order: they stay on the version they were assigned, until assign_playlist_order is called again.
    ConnectorOAuth
  • Send email using the connected application’s mcp:send capability. The mail client UI asks the user to confirm recipients and content before invoking this tool; callers must obtain that confirmation. Body is plain text. Reuse mutationId, queuedAt, and the exact payload on retries to avoid duplicate sends. An uncertain result must be reconciled in Sent before another send. Requires mcp:send permission.
    Connector
    Destructive
    OAuth
  • Return practised-topic Infinite Practice mastery for a course (topic_id, topic_name when available, display 0–100, questions_answered). Use after get-context flags (has_course_mastery / started_course_mastery) or whenever context omitted topic_masteries. Agent OS is read-only: chatting, creating artifacts, or calling this tool does not change mastery. Source of truth is Infinite Practice attempts (user_topic_mastery: identity + course + topic); display matches the web IP UI. Progress is learner- and course-scoped, not chat- or client-scoped — web IP writes it; ACE/mobile/Agent OS only read the same rows. Empty topic_masteries means no IP attempts yet, not a separate client score. Requires course_id.
    ConnectorNo auth
  • Queue creating or updating a same-domain nameserver IP record at the registrar for an owned domain. The public parent-zone glue can direct resolvers to new nameserver addresses; updating an existing hostname replaces its previous addresses. Hostname must be below the domain, addresses must be public IPs, and this does not create DNS A/AAAA records or PTR. Requires domains:manage when using an API key.
    Connector
    Destructive
    OAuth
  • Return practised-topic Infinite Practice mastery for a course (topic_id, topic_name when available, display 0–100, questions_answered). Use after get-context flags (has_course_mastery / started_course_mastery) or whenever context omitted topic_masteries. Agent OS is read-only: chatting, creating artifacts, or calling this tool does not change mastery. Source of truth is Infinite Practice attempts (user_topic_mastery: identity + course + topic); display matches the web IP UI. Progress is learner- and course-scoped, not chat- or client-scoped — web IP writes it; ACE/mobile/Agent OS only read the same rows. Empty topic_masteries means no IP attempts yet, not a separate client score. Requires course_id.
    ConnectorNo auth
  • Convert a Figma design to production-ready code. This tool generates code from Figma designs, supporting multiple frameworks and styling options. **Authentication:** Requires X-Figma-Token header with your Figma personal access token. **Inputs:** - fileKey: Figma file key extracted from the URL. For example, from "https://figma.com/design/abc123XYZ/MyDesign", the fileKey is "abc123XYZ". - nodesId: Array of Figma node IDs to convert. Extract from the URL's node-id parameter, replacing "-" with ":". For example, from "?node-id=1-2", the nodeId is "1:2". - framework: Target framework (react, html). Detect from the user's project to match their existing stack. - styling: CSS approach (tailwind, plain_css). Detect from the user's project to match their existing styling system. - language: TypeScript or JavaScript. Detect from the user's project. - uiLibrary: Optional UI component library (mui, antd, shadcn). Detect from the user's project if they use one of the supported libraries. - assetsBaseUrl: Base path for assets in generated code **Returns:** - files: Generated code files as a record of {path: {content, isBinary}} - assets: Array of {name, url} for images/assets that need to be downloaded from Figma - tokenUsage: Approximate token count for the generation - snapshotsUrls: Record of {nodeId: url} with screenshot URLs for each requested node - guidelines: IMPORTANT Instructions for using the generated code effectively **Asset Handling:** The generated code references assets at the assetsBaseUrl path. You must download the assets from the returned URLs and place them at your assetsBaseUrl location. For example, if assetsBaseUrl is "./assets" and an asset is named "logo.png", the code will reference "./assets/logo.png".
    ConnectorOAuth
  • Define a new custom post type (e.g. "treatment", "service"). Required before creating posts of that type. After creating a post type, use create_post_type_field to define its structured field schema. Those fields are stored in meta on each post — do not use excerpt for structured data.
    ConnectorNo auth
  • Define a new custom post type (e.g. "treatment", "service"). Required before creating posts of that type. After creating a post type, use create_post_type_field to define its structured field schema. Those fields are stored in meta on each post — do not use excerpt for structured data.
    ConnectorNo auth
  • FIRST step for creating or revising a game. Save a proposal document and a visible Games tab entry, then STOP for human approval. Markdown must have headings starting Concept, Gameplay, Controls, Screens, Files, and Playtest. Describe audience, objective/core loop/levels/win/loss, desktop/touch controls, visual/audio direction, start/pause/help/score/game-over/restart UI, code organization and assets, and concrete checks. Do not include game code. For an existing game read it first and pass expectedVersionId and expectedProposalRevision. For a modular Worldstream attachment supply worldExperienceTarget with its liveWorldId, inputBindingId, and current expectedVersionId. An approved build automatically pins the new game version only if that world version is still current. A revised proposal always needs fresh approval.
    ConnectorAPI key