"Designing UI (User Interfaces)" matching MCP tools:

• send_message

  Dock

  Send a direct message to another agent or human in the messaging substrate. Wires through cue.dock.svc, the same path the /live UI uses, so the recipient sees this message in their drawer (and, once they have a Dock-connected agent worker running, their agent harness's inbox). Address format is `<agent_slug>@<user_slug>`: `flint@socrates` targets the `flint` agent owned by user `socrates`; `self@<user_slug>` targets a human's synthetic self-agent (use this to message a human directly when you don't know which of their agents to ping). Use this when an agent legitimately needs to ask a teammate (human or agent) for help, hand off work, or follow up async; don't use it as a chat-ops side-channel for things that belong in workspace events. Sender identity follows the caller: agent callers send AS themselves, user callers send AS their self-agent (`self@<their_slug>`). Body cap is 32,000 chars. Returns `{ messageId, threadId, to }` on success. The recipient is resolved against the substrate's identity space, NOT against your accessible workspace set, this is messaging, not workspace write access. Pre-cue.dock.svc-deploy environments return `cue_not_configured` (caller treats as 'messaging not deployed yet').

  Connector

• popular_routes

  Tripuck

  Tripuck's Explore service — most popular destinations with current prices from a given origin city, aggregated from live flight inventory data. Use for inspiration-style queries where the destination is unknown: "where can I fly from Istanbul?", "İstanbul'dan nereye?", "وجهات شعبية من دبي", "populäre Reiseziele ab München". The LLM MUST infer the user language from the conversation and pass it via the `locale` parameter ("tr" Turkish, "en" English, "ar" Arabic, "az" Azerbaijani, "de" German, "ka" Georgian, "uz" Uzbek). All widget UI text and the text response are then returned in that language. If `currency` is not specified, a sensible default is picked from the locale (tr→TRY, en→USD, de→EUR, ar→USD, az→AZN, ka→GEL, uz→UZS).

  Connector

• get_context_setup_status

  paid-ads

  Data tool for the current user's saved client context, including client setup status, advertiser profiles, synced account/campaign counts, and any open setup questions. For the user-facing setup UI, prefer render_context_onboarding.

  Connector

• tf_premium_regime

  terminalfeed

  Premium regime classifier. Blends crypto Fear & Greed (alternative.me), VIX (FRED VIXCLS), 24h total crypto market-cap change (CoinLore), and the 10y treasury-yield trend (FRED DGS10) into a labeled regime (risk_on, risk_off, transition, or stress), a risk_score in [-1..+1], a 0-1 confidence, and a per-input drivers[] breakdown showing each signal value, weight, and contribution. A stress override fires when VIX>30 or (Fear&Greed<15 and 24h market cap <-3%). The documented, versioned weighting is the value; the upstreams are free. Saves an agent from fetching and normalizing four sources and designing its own blend. Statistical heuristic, not investment advice. Costs 2 credits ($0.04 USDC). Requires Authorization: Bearer tf_live_<64-char-hex>.

  Connector

• nexbid_purchase

  discovery

  <tool_description> Initiate a purchase for a product found via nexbid_search. Returns a checkout link that the user can click to complete the purchase at the retailer. The agent should present this link to the user for confirmation. </tool_description> <when_to_use> ONLY after user has expressed clear purchase intent for a specific product. Requires a product UUID from nexbid_search or nexbid_product. ALWAYS confirm with user before calling this tool. </when_to_use> <combination_hints> nexbid_search (purchase intent) → nexbid_purchase → present checkout link to user. After purchase → nexbid_order_status to check if completed. Use checkout_mode=wallet_pay when the user has a connected wallet with active mandate. </combination_hints> <output_format> For prefill_link (default): Checkout URL that the user clicks to complete purchase at the retailer. For wallet_pay: Intent ID and status for mandate-based authorization. Include product name and price for user confirmation. </output_format>

  Connector

• set_guild_member_role

  argo-mcp

  Change a guild member's role to Owner, Admin, or Member. Owner/Admin only. Note that promoting another user to Owner transfers the guild — confirm with the user first.

  Connector

• resolve_kb_id

  fixflow

  FIRST STEP in any troubleshooting workflow. Search the collective Knowledge Base (KB) for solutions to technical errors, bugs, or architectural patterns. Uses full-text search across titles, content, tags, and categories. Results are ranked by relevance and success rate. WHEN TO USE: - ALWAYS call this first when encountering any error message, bug, or exception. - Call this when designing a feature to check for established community patterns. INPUT: - `query`: A specific error message, stack trace fragment, library name, or architectural concept. - `category`: (Optional) Filter by category (e.g., 'devops', 'terminal', 'supabase'). OUTPUT: - Returns a list of matching KB cards with their `kb_id`, titles, and success metrics. - If a matching card is found, you MUST immediately call `read_kb_doc` using the `kb_id` to get the full solution.

  Connector

• check_package

  DepScope

  Full machine-readable JSON report (~2k tokens). USE WHEN: you need to programmatically parse specific fields (CI gating, UI, sub-field extraction). Otherwise prefer get_package_prompt. RETURNS: {package, health:{score}, vulnerabilities[], latest, deprecated, maintainers, recommendation}.

  Connector

• get_install_instructions

  petal-components-mcp

  Get the canonical steps for installing petal_components in a Phoenix project. Call this when the user asks to install petal_components, when you are setting up a new Phoenix project that needs UI components, or when verifying an existing installation. Returns step-by-step instructions covering mix.exs, mix deps.get, Tailwind v4 CSS config, and the web module import. Steps are idempotent - safe to follow on a project that is partially configured.

  Connector

• ateam_upload_connector

  ateam-mcp

  Upload connector code to Core and restart — WITHOUT redeploying skills. Use this to update connector source code (server.js, UI assets, plugins) quickly. Set github=true to pull files from the solution's GitHub repo, or pass files directly. Much faster than ateam_build_and_run for connector-only changes.

  Connector

• deviceAuthInspect

  AILANG Parse

  Look up a pending device code by user_code and return its provenance. No authentication required — possession of the user_code is the proof. The dashboard /approve.html page calls this BEFORE showing the approve UI so the user can see where the request came from (IP, User-Agent, Referer, age) and decide whether to trust it. Returns 404 if the user_code does not match any pending device_codes doc. Already-approved or expired codes return as INPUT_NOT_FOUND too — there is nothing to inspect after the fact.

  Connector

• roamzy_get_esim

  mcp-server

  Get a specific eSIM by id, including msisdn, status, balance, and the activation block (qr_payload + lpa_url). ⚠️ QR RENDERING: This tool does NOT return a ready-to-display image. Instead, qr_payload contains the LPA URI string. YOU must generate the QR PNG yourself using your code-execution tools (Python qrcode library, JS qrcode npm package, etc.) and offer the resulting PNG as a downloadable file to the user. DO NOT use external QR-generation services — they show ugly UI dialogs in Claude Desktop and require external trust. Local generation gives the user a real downloadable PNG they can save and scan. ALWAYS caption the QR (once generated) with «Ваш номер eSIM: <msisdn>» / «Your eSIM number: <msisdn>». The lpa_url field is ONLY for users installing on the SAME phone where they're reading the chat (camera can't scan own screen) — surface it as a text fallback for that case, prefixed «LPA URI (manual entry):». Do NOT show internal IDs (id, display_id, iccid) to the user. ⚠️ ANON-MODE RECOVERY REMINDER: If this is an anonymous Roamzy session (no ROAMZY_API_TOKEN env was set), after presenting the QR you MUST also re-surface the claim_url from the original roamzy_create_order response with this framing: «❗ Не забудь сохранить ссылку восстановления — без неё ты не вернёшься к этой eSIM из другого Claude-чата». If the user has already closed-and-reopened the chat and lost the claim_url, instruct them to contact Roamzy support (call roamzy_support tool) with their MSISDN + NowPayments transaction hash for manual recovery — operator can mint a fresh claim_url. If the user follows up with «how do I contact support» or «refund» — call roamzy_support, not web search.

  Connector

• browse_themes

  Slidev MCP

  Show the user a visual theme gallery with preview images. ONLY call this when the user explicitly asks to SEE or BROWSE themes visually (e.g. "show me the themes", "what do they look like", "let me pick a theme"). This renders an interactive gallery in the user's UI. To show a filtered subset (e.g. only dark themes), first call list_themes to identify matching themes, then pass their names here. Do NOT call this to decide which theme to use yourself — use list_themes for that instead.

  Connector

• play_game

  Vocab Voyage

  Use this when the user wants to play a vocabulary game, asks for something fun, or wants to learn through play. Launches one of 11 mini-games inside the host chat. Renders the matching ui://vocab-voyage/game/{slug} widget on supporting hosts; falls back to a deep link elsewhere. Per-question answers persist via record_word_result; round completion fires record_session_complete + award_game_xp so MCP play counts toward streaks, XP, and mastery for signed-in users. Supported slugs: word_match, spelling_bee, speed_round, synonym_showdown, word_scramble, fill_in_blank, context_clues, word_guess, picture_match, crossword, word_search. Do not use for a serious test-prep quiz — call generate_quiz instead.

  Connector

• linkedin_find_campaigns

  paid-ads

  Data tool that finds LinkedIn campaigns by name across one account or all accessible accounts, ranks likely matches, and returns compact campaign identity data for disambiguation. For the user-facing picker UI, prefer render_shared_picker.

  Connector

• flight_details

  Tripuck

  Detailed information for a specific Tripuck flight ID: segments, layovers, baggage allowance, fare rules, refund/change conditions, operating carrier. Use for follow-up questions after `search_flights`: "what is the baggage allowance on this flight?", "bu uçuşta aktarma süresi nedir?", "كم الأمتعة المسموحة؟". The LLM MUST infer the user language from the conversation and pass it via the `locale` parameter ("tr" Turkish, "en" English, "ar" Arabic, "az" Azerbaijani, "de" German, "ka" Georgian, "uz" Uzbek). All widget UI text and the text response are then returned in that language. If `currency` is not specified, a sensible default is picked from the locale (tr→TRY, en→USD, de→EUR, ar→USD, az→AZN, ka→GEL, uz→UZS).

  Connector

• axint.cloud.check

  Axint

  Run an agent-callable Cloud Check against Swift or Axint TypeScript source. Accepts inline source or a sourcePath, then returns a Cloud-style verdict, Apple-specific findings, next... Use: use for Apple-aware source review and repair prompts; provide evidence for UI/runtime claims. Effects: read-only response from provided source/path; may use configured Cloud Check endpoint; no source is sent unless provided.

  Connector

• user

  Fast.io

  User profile, contacts, invitations, assets, and personal AI instructions. Call action='describe' for the full action/param reference. Destructive: close.

  Connector

• projects_list

  WoopSocial Social Media MCP

  Returns projects that belong to the same organization as the API key. A project corresponds to a "Business Profile" in the UI.

  Connector

• get-quickstart-guide

  JxBrowser MCP Server

  Provides step-by-step instructions for an AI assistant to set up a new JxBrowser project. This tool is meant for fully automated project creation and should be called when the user asks to create, start, scaffold, bootstrap, init, template, or generate a JxBrowser project, app, or sample. CRITICAL RULES: 1. NEVER call this tool before knowing the user’s preferences. If the user hasn’t specified them, ASK first: - UI Toolkit: Swing, JavaFX, SWT, or Compose Desktop - Build Tool: Gradle or Maven 2. Immediately after calling this tool, you MUST execute all setup commands returned by this tool using the Bash tool to actually create the project.

  Connector