Skip to main content
Glama
758,747 tools. Updated 2026-11-08 03:24

"User interface design or related topics" matching MCP tools:

  • Search Flevy's marketplace of consulting frameworks, PowerPoint templates, Excel financial models, business toolkits, and management case studies. Use this whenever a user needs a best-practice framework, methodology, template, financial model, or real-world case example on any business or management topic (strategy, digital transformation, supply chain, pricing, operational excellence, M&A, etc.). Returns up to 10 relevance-ranked recommendations across two content types: "document" (premium documents authored by management consultants) and "case_study" (management case studies). ALWAYS include each recommended item's url as a clickable link when you mention it in your reply — never reference a document without its link, because the link is the only way the user can open it. Each result carries a content_id for get_content_details. Filters: topic (single, or "topics" for documents covering ALL of several topics), author (list more documents from an author seen in results), filetype (including tier1_consulting_deck for McKinsey-style strategy decks), content_type. Topic-filtered responses also list related_topics to pivot to. Provide at least one of query, topic(s), or author; use list_topics to map user phrasing to a canonical topic.
    ConnectorNo auth
  • Read live X/Twitter data: look up a single tweet or user profile, batch-read up to 100 tweets or users at once, check whether one account follows another, fetch trending topics by region, extract a long-form article, or download tweet media. Pay per call in USDC — no API key, no signup; failed calls are never charged. Guidance: resource=get-tweet|get-user (id), batch-tweets|batch-users (ids array, ≤100), check-follower (source+target usernames), trends (optional woeid/count), article (tweet id), followers-you-know (id + mandatory resultsLimit), download-media (id or ids ≤50 — returns media file URLs on THIS origin; links live 7 days). Fixed-price per call/id except followers-you-know which is per-result.
    ConnectorNo auth
  • Use this when the user asks what Alicia or digitalgarden.si has written about a subject (for example Houdini, Three.js, WebGPU, glTF/USD, Gaussian splats, AI coding agents, or the garden itself). Ranks published notes by keyword match on title, topics, summary and full text, in English and Chinese, and returns short cards (no full text). Follow up with get_article to read one. Do not use it for general web search, news, or topics unrelated to Alicia's published notes. An empty articles array means no published note matches. Scores are relative to this query and catalog, not confidence percentages; check titles and read the full note before presenting a match as relevant. Every result includes canonicalUrl and author Alicia (Person @id https://digitalgarden.si/#alicia). Cite the canonical URL when quoting. digitalgarden.si is an interactive 3D garden, not a knowledge-base wiki.
    ConnectorNo auth
  • Use this when the user asks what Alicia or digitalgarden.si has written about a subject (for example Houdini, Three.js, WebGPU, glTF/USD, Gaussian splats, AI coding agents, or the garden itself). Ranks published notes by keyword match on title, topics, summary and full text, in English and Chinese, and returns short cards (no full text). Follow up with get_article to read one. Do not use it for general web search, news, or topics unrelated to Alicia's published notes. An empty articles array means no published note matches. Scores are relative to this query and catalog, not confidence percentages; check titles and read the full note before presenting a match as relevant. Every result includes canonicalUrl and author Alicia (Person @id https://digitalgarden.si/#alicia). Cite the canonical URL when quoting. digitalgarden.si is an interactive 3D garden, not a knowledge-base wiki.
    ConnectorNo auth
  • Find where a feature lives in the Buzzberg interface. Read-only, no data is changed. Use this for every "where do I find X", "how do I open X", "which section has X" question instead of guessing. It searches only the verified navigation catalog of user-facing surfaces; internal, admin and API routes are deliberately not covered. If nothing matches, say the location is not confirmed rather than inventing one. Args: query: What the user is looking for, in their own words (any language). locale: UI locale for section names, e.g. "en", "ru", "ko". limit: Max matches to return (default 5).
    ConnectorOAuth
  • Full Rams design review of UI code (React, Vue, Svelte, HTML, CSS, SwiftUI). Returns a 0-100 score (criticals cap it: one caps at 59, two at 49, three or more at 39), issues with severity, category, file:line, and concrete fixes as patches. Call it once at the end: before a commit, or when the user wants a score or a final check. Pass each file with its real path, or for pasted code a path that fits it (pasted/Card.tsx). Each call uses one review credit. Reviewing a few files needs no permission. Ask the user before a whole-codebase audit (dozens of files), since it spends their allowance. For quick feedback while you work, use quick_review.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Provides AI agents with real-time trending topics from Weibo, Baidu, Zhihu, Google Trends, and HackerNews/StackExchange community intel, enabling content and marketing agents to stay aware of current conversations before creating content.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to query OpenRouter model information including prices, ELO rankings, context, and perform comparisons.
    41 npm
    1
    MIT

Matching MCP Connectors

  • Carbon Interface MCP — Carbon Interface API (v1)

  • The topics in a set of documents in one call, with each document's topic mixture. Nothing stored.

  • Full Rams design review of UI code (React, Vue, Svelte, HTML, CSS, SwiftUI). Returns a 0-100 score (criticals cap it: one caps at 59, two at 49, three or more at 39), issues with severity, category, file:line, and concrete fixes as patches. Call it once at the end: before a commit, or when the user wants a score or a final check. Pass each file with its real path, or for pasted code a path that fits it (pasted/Card.tsx). Each call uses one review credit. Reviewing a few files needs no permission. Ask the user before a whole-codebase audit (dozens of files), since it spends their allowance. For quick feedback while you work, use quick_review.
    ConnectorNo auth
  • Submit a content correction, copyright concern, or factual error report. USE WHEN: user (via your interface) flags a wrong answer, broken translation, attribution issue, or DMCA concern. INPUTS: at least one of (questionId UUID, questionText, questionUrl), type (translation|factual|inappropriate|attribution|other), comment (optional, max 2000), reporterEmail (optional). OUTPUT on success: {ok:true, reportId}. On failure the result is marked isError:true with structuredContent {error, message} — error codes: invalid_input, not_found, rate_limit_exceeded (per-IP 5/min), internal_error.
    ConnectorNo auth
  • Get Lenny Zeltser's expert CTI writing guidelines. Topics include tone, words, structure, executive_summary, voice, articles, summary, brief (one-page brief section guidance), handoffs (cross-server routing), methodology (the three subsections), fields (per-field guidance), and CTI-specific topics: attribution (full Six Signals prose), confidence (ICD-203 ladder), pyramid_of_pain, six_signals (signals table only), and anti_patterns. The general writing topics (tone/words/structure/executive_summary) now defer to `get_security_writing_guidelines` for the canonical Five Elements rules; CTI-specific content lives in the other topics. Pair the 'fields' topic with field_id for single-field guidance. This server never requests your campaign or threat-intel notes and instructs your AI to keep them local—templates and guidelines flow to your AI for local analysis.
    ConnectorNo auth
  • Fetch full details for one skill by slug. Call AFTER search_skills or popular_skills when a user selects a specific result — do NOT batch-call for every item. Returns: name, description, category, tags, version, author, downloads, stars, install_command, homepage_url, repo_url. Error lifecycle: slug not found → {error: "Skill not found"} → fall back to search_skills with related keyword. Never guess slugs; only use slugs from prior tool results.
    ConnectorNo auth
  • Create a job (or reuse job_id) and start a generative run. Omitting job_id ALWAYS creates a NEW job — call at most ONCE per user request. If you already have a job_id (including from a prior create_design error), pass it or use update_design; never call create_design again without job_id for the same request. The API rejects a second run on a job while one is still queued or running (409) — if a run fails or stalls, report it and ask the user before cancelling or re-running. Always tell the user job_id and run_id as soon as this returns. If the result includes concurrency_notice, show that reminder (pay-as-you-go accounts run one design at a time). Do not set wait:true. If the user asked to be emailed (including in the original request), set notify_email:true here immediately — do not wait until after wait_for_run. After create, call wait_for_run ONCE (default ~45s). If still_running and they have not already asked for email, stop polling, show the IDs, and offer notify_run_email. Photos/logos: prefer request_file_upload (or upload_file on stdio) then pass file_ids — never compress or generate a replacement. asset_paths is stdio-only; asset_files base64 is a last resort for tiny files. After completion, return viewer_url and offer export (pdf/html/png) — do not publish unless the user asks.
    Connector
    Destructive
    OAuth
  • Return the workspace's knowledge graph: topics, links and clusters. Use it to draw or reason about the overall shape of the brain (which topics are hubs, how areas connect), not to read content: for page text use ``get_page``, for code dependencies use ``impact``. It takes no arguments and can be large. Returns ``{nodes, links, communities, stats}``, the graph the app's Map shows, with pages you cannot open left out, or ``{error}`` when no graph has been built for this workspace yet. It costs no AI tokens.
    ConnectorAPI key
  • Generate a document as a PDF and store it in the workspace. It never emails or sends anything, so a request to email or send a document is not a request to generate one. Pass exactly one source: - `params`: values you provide, with a `document_slug`. Call well_list_generative_documents first: it gives each design's document_slug and the JSON Schema its params must satisfy. Values that do not match are refused with the path and reason of each problem, so fix them and call again. The design prints light unless `params.theme` is "dark". Each call prints and stores a new document, unless you pass `document_id`. - `document_id` (with `params` only): when the user asks to change, fix or redo a document you already generated in this conversation, pass its document_id so it is replaced in place instead of adding a new file. Its document_id and links keep working and serve the new PDF. Only a document this tool generated from values can be replaced. - `invoice_id`: an invoice already in Well. The PDF prints that invoice, in its own chosen ink, and is attached to it as its document. Pass a `document_slug` to choose the design; without one, the invoice's own chosen design prints. Refused when the invoice already carries a file a user or connector supplied: a generated PDF never replaces one. Generating again updates that same document in place, so its document_id and links keep working. - `design` (with `invoice_id` only): the options the invoice-design card returned, passed exactly as the card gave them. `layout`, `theme` and `locale` choose the design, the ink and the language of this print, on an issued invoice too. `payment_terms_note_id`, `tax_rate_id`, `legal_mentions_note_id` and `payment_means_id` must equal what is saved on the invoice, or be null when nothing is saved: an id that differs is refused, so save a change with well_update_invoice_design first. Each option is optional, and every option left out keeps the value the invoice already holds. `theme` is a key of `design`, not a top-level input. Do not pass `design.layout` together with a different `document_slug`, or `design.locale` together with a different `locale`: the call is refused. Totals are never supplied: every sum is computed from the lines, so a printed total cannot disagree with the lines above it. The tool returns the stored PDF's document_id. `file` carries the PDF's name and size plus the links to fetch it. The result renders as a card with Download and View in Well; when no card is shown, hand the user `download_url`. - `download_url` saves the PDF and `signed_url` opens it in a browser. Both work with a plain HTTP GET and no auth header, and stop working at `expires_at`. - `preview_url` is a PNG image of the first page, for showing the document; add `page=N` for page N, up to `page_count`. Same token and expiry as the other links. - `sheet_url` is the document's HTML sheet, which the card draws with zoom and pan. Same token and expiry. - When the user wants to do more with a PDF already generated (attach it to an email, upload it elsewhere, read or analyse it, pass it to another tool), fetch `download_url` with a plain HTTP GET to get the bytes. - If the links have expired, call this tool again: with `params` it prints a new document with fresh links; with `invoice_id` it refreshes the same document and its links. - `app_url` opens the document in Well and never expires. - The links grant access to the file on their own: share them only with the user, never in a public place. With `invoice_id` of an issued invoice, the PDF is the issued invoice and `portal_url` is its customer page, the page its QR code opens, for the owner to forward to the customer. It is null when the invoice has no customer page.
    ConnectorNo auth
  • Get resolved preference values for the caller in this workspace. Each key resolves to the caller's own override when they have set one, otherwise the workspace-wide default, otherwise it is absent from the result. Known keys: connector_write_trust, invoice_default_layout, invoice_design, action_trust, preferred_name, form_of_address, mail_sender_choice, timezone, bank_account_offer, invoice_payment_account, invoice_card_payment_link, payment_link_reconnect_offer, sunday_routines, message_policy, proactive_messages, touchbase_afternoon, touchbase_eod, touchbase_afternoon_workspace, touchbase_eod_workspace, customer_facts_note_id, extension_install_offer, cash_scope, missing_invoice_duplicate_verdicts, todo_kind_mutes, customer_answers_alone_topics, pre_meeting_note, bank_connect_offer, email_weekly_digest, email_connection_updates, email_well_notifications, brief_section_header, brief_section_cash, brief_section_carousel, brief_section_agenda, brief_section_todos, brief_section_tomorrow-meetings, brief_section_business-watch, brief_section_detail, brief_section_main-button, brief_email, unassigned_task_default. Pass `keys` to limit the read to specific keys; omit it to get every preference currently set. A key with no value set anywhere is simply absent from `preferences`, never returned as null or an empty string. `invoice_design` comes back as the invoice design options object `{ layout, theme, locale, payment_terms_note_id, tax_rate_id, legal_mentions_note_id, payment_means_id }`, the same object `well_generate_document` takes as `design`. To save it on an invoice with `well_update_invoice_design`, convert each key to its `design_*` attribute (`layout` → `design_layout`, `payment_means_id` → `design_payment_means_id`, …). Pass `namespace` to read the values saved for one subject, e.g. `"customer:<company_id or person_id>"` for one customer's invoice design. A namespaced read returns only that namespace's values and never falls back to the un-namespaced ones; read without `namespace` too when the house default should apply. The pre-meeting note is off until the member's `pre_meeting_note` is "on", whatever the schedule list shows; an un-namespaced read always returns it as "on" or "off". `mail_sender_choice` is a member-private key read one sender at a time: pass `namespace` set to the `namespace` that `well_list_mail_senders` returns for that sender, and it comes back as `{ choice, sender }` from the caller's own saved row only. No other member's choice and no workspace default is returned for it. To read the choices of many senders at once, call `well_get_mail_sender_choices`. A read without `namespace` also returns `invoice_layouts`: every invoice design, as `{ layout, name, description: { fr, en } }`, the default design first. Name a design to the user only with its `name` and its `description` in the conversation's language, and save the `layout` of the one they pick. When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass `workspace_id` on the call.
    ConnectorNo auth
  • Use this when the user wants to check whether people talk about a topic or an angle in public, such as "is there discussion about personalised dog food?". Pass one to five short phrases. Searches Hacker News and, if stack_site is given, one Stack Exchange site, for posts in the last year (or since_days). Returns per phrase the number of matching posts, the top three with title, link, score and comment count, and a plain signal. It is a weak signal skewed to technical and hobby topics, not a market size, and it does not search Reddit.
    ConnectorNo 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
  • Search the PUBLIC Awareness knowledge graph — 1,000+ sourced scientific papers. Use this when the user (especially a researcher or a research agent) asks for peer-reviewed findings: "latest evidence on X", "highly-cited papers about Y", "what does the literature say about Z". This is NOT a memory tool — it does not read the user's private memory, and it needs no per-user API key, so it works even when Awareness memory is not configured (the MCP connection itself still needs its own token). Coverage: condensed-matter, quantum-information, materials, machine-learning, renewable-energy, chemistry, biology, medicine, neuroscience, computer-science (2022-2026, cited >= 50), plus a business supply/demand domain. What comes back (anonymous preview mode): title, snippet (preview), confidence, source_ref (DOI), citation_count, domain/topic, and a detail page URL. Full content is NOT in the preview — tell the user it is paid retrieval via POST /api/v1/public/retrieve with an API key (see https://awareness.market/en/knowledge for the KaaS product). Args: query: Natural-language research question or keywords (2-1000 chars). domain: "science" (default) or "business". topic: Optional sub-topic slug, e.g. "medicine", "condensed-matter", "supply-chain". Empty = search all topics in the domain. top_k: Max results, 1-20 (default 5; anonymous callers are capped at 3). include_graph: When true, also return same-topic related items. Returns: {"results": [{id, title, snippet, confidence, source_ref, citation_count, domain, topic, url}], "related": [...], "total": int, "mode": str} `mode` is "preview" (anonymous) or "full" (authenticated).
    ConnectorNo auth
  • Upload the released board (Gerbers, BOM, placement) to a manufacturer and return the page where the user pays. This publishes the design to a third party: call it only when the user has explicitly asked to order from that provider, and set user_confirmed only then. Some providers need a shipping address.
    Connector
    Destructive
    No auth
  • Upload the released board (Gerbers, BOM, placement) to a manufacturer and return the page where the user pays. This publishes the design to a third party: call it only when the user has explicitly asked to order from that provider, and set user_confirmed only then. Some providers need a shipping address.
    Connector
    Destructive
    No auth
  • Have Mondovo's AI make changes to an existing site from a natural-language instruction (e.g. "make the hero bigger with a dark background", "change the primary color to navy", "add a testimonials section"). This is the right tool for open-ended design work, or when you cannot see the source. For copy-only changes prefer patch_variation_content, and when this connection holds `source:read` and you can author the exact change yourself, prefer read_design → update_variation_file — both are instant, deterministic, and land in the same version history as a refinement. Pass `image_urls` to attach REFERENCE images the change should be modelled on — a screenshot of a layout to match, a mockup, a competitor's section — and say what to do with them in the instruction ("make the hero section match this layout"). They are shown to the model as pictures, so use them whenever the target is easier to show than to describe; a described layout is reproduced far less faithfully than one the model can see. The images are a REFERENCE for the design, not content to insert — to place an actual photo on the page, describe where it goes and pass its url in the instruction. URLs must be on Mondovo storage: call upload_asset first and pass the permanent url it returns. For retry safety, reuse the same optional `idempotency_key` for one refinement attempt. Returns a `job_id` immediately; poll `get_job` every ~10s until its status is "completed" (a refinement typically takes 30-120s). The work runs server-side and completes even if this conversation ends, so a lost connection is not a failed refinement. If the site already has another operation running you get `site_busy` with that operation's `job_id` — poll it, then retry. `page` targets one page by slug — including a PAGE DRAFT's slug (from create_page_draft), which edits the draft and leaves the live page alone. `variation_id` selects the design to edit. On a design site with several alternatives it is REQUIRED: show the choices from list_variations and let the user choose, rather than assuming the active or first design. On a built or single-design site, omit it for the chosen design. A page draft that lives in a different design is edited with patch_variation_content / update_variation_file instead.
    ConnectorOAuth
  • Publish a site to make it live on the web at its platform address (the `deployment_url` in the response is the exact live URL — report that, never guess a host). Choose a subdomain matching the business name (lowercase, hyphens). IF THE SITE STILL HOLDS SEVERAL DESIGNS you MUST pass `variation_id` — the design to publish, taken from list_variations (a UUID, not an index). Do not choose for the user: list_variations attaches a thumbnail of each design, so show them and let the user pick. Publishing a design turns it into its own site: Mondovo builds the chosen design into a new site and publishes THAT, so the response carries a different `site_id` — use that id from then on (the original id stays the design draft, and get_site on it will keep saying unpublished). Calling publish twice reuses the same built site rather than creating another. Sites that already have one design ignore `variation_id`. A design only has its home page, but its menu links to the rest of the site: when it does, publish_site first BUILDS those pages and then publishes automatically — it returns status "building" with `pages_being_built`, a `job_id` and the new `site_id`. Before publishing a design, tell the user which pages its menu links to and that they will be built. On "building", tell the user which pages are being built, poll get_job with the job_id until "completed" (`failed` lists pages that could not be built — their menu links are removed; `publish` says whether the site went live), then poll get_site until "published". Do not call publish_site again meanwhile. If a response carries `missing_pages`, those menu links have no page and 404 on the live site: tell the user and offer add_pages for them. This tool RETURNS IMMEDIATELY with status "publishing" once the site is accepted for deployment — it does NOT wait for the deploy. Compiling and deploying takes 1-3 minutes and continues server-side even if this conversation ends. Poll get_site (with the returned site_id) every ~15s until status is "published" to get the live URL — or "publish_held", which means the new build crashed in a browser check before going live and was not published (tell the user its `publish_message`). NEVER call publish_site a second time to check on or hurry along a publish you already started: while one is in flight the publish lock rejects the call, and a transport timeout on this tool does NOT mean the publish failed — it is almost always still running, so poll get_site before concluding anything. If the response is `contact_info_needs_confirmation`, its `reason` says why: "placeholders" means contact details that look AI-invented (listed in `placeholders`) — refine them to the real values first, or (if they are already correct) call again with `confirm_contact_info: true`; "missing_details" means nothing was invented but the email or phone in `missing_fields` is absent — ask the user for it, or call again with `confirm_contact_info: true` if the site should go live without it. Never make up a contact detail. Retrying with the same arguments will NOT clear that warning. Success responses carry `after_publish` (plan, custom domain, editor link): once get_site reports "published", relay its `tell_user` to the user.
    ConnectorOAuth