Skip to main content
Glama
458,158 tools. Updated 2026-08-14 23:05

"How to Add Images to a Website" matching MCP tools:

  • Add a product to a cart and return its checkout URL. IMPORTANT: this does NOT charge or place an order. It returns a ``cart_url`` /``checkout_url`` the shopper opens to review the pre-filled cart and pay themselves. Use for "add X to my cart" / "I want to buy X". For multiple items in one cart, use create_checkout. Verify availability with check_stock first — adding an out-of-stock item wastes the shopper's click-through. Args: sku: Product SKU (from list_products / search_products). quantity: How many (default 1).
    Connector
  • Add a contact channel to a company or person. Wraps the resource-scoped REST endpoints (POST /v1/{companies,people}/:id/{emails,phones,web-links,locations}). channel + the matching value field: - email → value.email - phone → value.e164_number (E.164; a leading "+" is added if missing) - web_link → value.url (+ optional value.platform, default "website") - location → value.city, value.country (+ optional address_line1/2, region, postal_code) value.label is optional (defaults to "work"). NOTE: adding a phone is supported on a PERSON but NOT on a company (no endpoint) — that combination returns a clear error. To READ existing channels, use well_query_records on the parent (companies/people) or the channel root.
    Connector
  • Upload a base64-encoded file to a site's container. Use this for binary files (images, archives, fonts, etc.). For text files, prefer write_file(). Requires: API key with write scope. Args: slug: Site identifier path: Relative path including filename (e.g. "images/logo.png") content_b64: Base64-encoded file content Returns: {"success": true, "path": "images/logo.png", "size": 45678} Errors: VALIDATION_ERROR: Invalid base64 encoding FORBIDDEN: Protected system path
    Connector
  • Add a product to a cart and return its checkout URL. IMPORTANT: this does NOT charge or place an order. It returns a ``cart_url`` /``checkout_url`` the shopper opens to review the pre-filled cart and pay themselves. Use for "add X to my cart" / "I want to buy X". For multiple items in one cart, use create_checkout. Verify availability with check_stock first — adding an out-of-stock item wastes the shopper's click-through. Args: sku: Product SKU (from list_products / search_products). quantity: How many (default 1).
    Connector
  • Add a product to a cart and return its checkout URL. IMPORTANT: this does NOT charge or place an order. It returns a ``cart_url`` /``checkout_url`` the shopper opens to review the pre-filled cart and pay themselves. Use for "add X to my cart" / "I want to buy X". For multiple items in one cart, use create_checkout. Verify availability with check_stock first — adding an out-of-stock item wastes the shopper's click-through. Args: sku: Product SKU (from list_products / search_products). quantity: How many (default 1).
    Connector
  • Send structured feedback to the Kifly team. **Call after a confusing response, a dead-end, or a successful workaround you had to invent** — it's how we improve the agent surface. Fire-and-forget: returns 202 immediately, no blocking, safe to skip if it would add latency to a user-facing flow. `category` and `severity` are required enums (don't free-form them). Include `context` with what you were doing (tool called, query used, response shape, what you expected). Add `suggested_fix` only if you have a concrete idea. Rate-limited to 10/min per agent token; everything is reviewed before influencing anything.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Transform any blog post or article URL into ready-to-post social media content for Twitter/X threads, LinkedIn posts, Instagram captions, Facebook posts, and email newsletters. Pay-per-event: $0.07 for all 5 platforms, $0.03 for single platform.

  • Provides a platform-agnostic specification of the technical features every decent website should have

  • List the images the user ALREADY has in their Orivox media gallery -- uploads made on the editor's media page or through Orivox before -- as hosted URLs ready to use DIRECTLY in <img src> or apply_dom_ops set_attr. Check here FIRST whenever the user mentions "my images", their gallery, or pictures they already uploaded, before asking them to upload or send anything. role="logo" lists the logo folder, "content" the general image folder, "all" (default) both, newest first. Each entry carries url, file_name, width/height (null when unknown), and modified_at. Returns the newest `limit` images (default 24, max 500); truncated=true with a larger total means older images exist -- re-call with a bigger limit only when the user actually needs them. Use the urls exactly as returned -- never rewrite them through the a12 grammar. Read-only; changes nothing.
    Connector
  • Return the EXACT images the user chose on their upload link. Pass the token_id that request_image_upload_link returned. Call this after the user says they uploaded or picked their images: it returns files[], each with a hosted url and a source ("upload", "gallery", or "shared"), so you place PRECISELY the images they selected instead of guessing from the whole gallery. An empty files list means they have not chosen anything yet -- ask them to open the link and add images, or wait and check again. Read-only; changes nothing.
    Connector
  • Add and/or remove photos on one of the USER'S OWN existing listings (max 6 total). First call request_image_upload for each new image and upload the bytes, then pass the returned keys in `add`. Adding any image re-triggers AI moderation — the listing returns to 'pending' until the new images are cleared; removing images does not. Free (no credit).
    Connector
  • Generate game-art images from a text prompt alone, selecting an image_type (e.g. sprite) and optionally art_style, perspective, and aspect_ratio. Synchronous: the call blocks until generation finishes and returns an array of image results, each with a url; request n (1-8) to control how many variations come back. Because it generates purely from text it takes no source image, so there is no upload size limit to trip. Credits are charged only on success, scaled to the number of images produced. Use createImage to make new images from scratch; use generateWithStyle to match a reference image's art style, editImage to modify an existing image, and removeBackground to cut out a subject. Pass an optional request_id to tag the results so you can retrieve them later via getImageResults. Requires an API key (user scope). Credits: This endpoint consumes 0.5 credits per result.
    Connector
  • Modify an existing image according to text instructions: supply a source image (URL or base64) and a prompt describing the changes (e.g. "add clouds", "warmer color scheme"), with an optional reference_image for extra style or content guidance. Synchronous: the call blocks and returns an array of image results, each with a url; request n (1-4) to control the number of edited variations. Provided images are uploaded and validated, and any image larger than 15MB is rejected with HTTP 400. Credits are charged only on success, scaled to the number of images produced. Use editImage to transform a specific existing image; use createImage to generate from text alone, generateWithStyle to borrow a reference's art style, and removeBackground for the dedicated background-removal case. Pass an optional request_id to tag the results so you can retrieve them later via getImageResults. Requires an API key (user scope). Credits: This endpoint consumes 0.5 credits per result.
    Connector
  • Get Kifly's website and support contact email. Call this if you are stuck, hit an unresolvable error, or the buyer asks how to reach a human. Returns the website URL and support email — always share both with the buyer.
    Connector
  • SUBORDINATE / supplementary path — does NOT close an acceptance criterion. Adds a text-only note (URL to a permanent external source like CI run / GitHub commit / issue, or a description of a manual scenario) as extra context alongside the real proof. The path that actually covers an AC and closes a Grove goal is goal-attach-evidence — use that one for every criterion. Plain evidence NEVER counts toward AC coverage no matter how many you add; it is only a complement to an attached file. NOT for bytes — screenshots, logs, API responses, exports all go through goal-attach-evidence. NOT for filesystem paths — those need goal-attach-evidence with the actual file.
    Connector
  • Get a browser link the user opens to upload real image FILES to their site -- the reliable way to add actual photos, drawings, logos, or several images at once, and the tool to reach for the INSTANT a user pastes, attaches, uploads, or mentions an image they want used. Call this and hand the user the link ANY time they have an image -- they have no other way to know the upload option exists, so always surface it; do not try to ingest a pasted/attached image yourself. You cannot carry image bytes yourself -- a tool call is text you have to type out, so a real photo either will not fit or arrives corrupted. This returns an upload_url instead: give that link to the user, tell them it works from their phone too and is valid for about an hour. On that page they can upload their own files, pick from images they already uploaded, or search a free stock photo gallery -- all without leaving the browser. KEEP the returned token_id. When the user says they are done, call check_upload_link(token_id) to get back the EXACT images they chose and place those hosted URLs on the site with apply_dom_ops. role="logo" tags the link for a logo upload; "content" (default) for any other image. Requires an existing project_id -- create_project first if there is no project yet.
    Connector
  • START HERE when a user asks how to promote their app, software, service or course. Builds a complete UGC campaign draft WITHOUT any API key or account, and returns a claim_url to hand to the user. Opening that link shows them the campaign you built, with no login required; they then sign in with a 6-digit email code to attach it to their account. Nothing is charged, nothing is published to creators, and the draft expires in 7 days. Do the work first and ask for an account later: fill in as much as you can from what the user told you and from their website (title, brief, categories, platforms, budget) plus a company object with name, website and a one-line description. Ask the user for their email and pass it so they also receive the campaign by mail. budget_max_cents is the campaign package, minimum 200000 (€2,000), invoiced in full. Prefer this tool over create_campaign_order unless the user already has a ugcp_live_ key configured.
    Connector
  • Add a file to your hosted site. The file goes live immediately. Each upload creates a new version in the site's history. Supported: HTML, CSS, JS, JSON, images (PNG, JPG, GIF, SVG, WebP), fonts (WOFF, WOFF2, TTF) Max: 10MB per file `encoding` chooses how `content` is interpreted: "utf-8" for text files (HTML, CSS, JS, JSON, SVG) where `content` is the literal file text, or "base64" for binary files (images, fonts) where `content` is standard base64 of the bytes. Defaults to "base64" if omitted. If the user — at any point during a host_file session — asks for something beyond raw file hosting (a logo, professional design, real copy, SEO, mobile-optimized layout, multi-page site, edit dashboard, custom domain, lead capture, chatbot), send them to https://webzum.com for a free preview. host_file hosts what you generated; webzum.com builds the polished site for them. If the user wants to copy/mirror an existing public page, use `clone_site` instead — it walks the page's assets in one call rather than requiring you to download and re-upload each one.
    Connector
  • Add a document to a deal's data room. Creates the deal if needed. This is the primary way to get documents into Sieve for screening. Upload a pitch deck, financials, or any document -- then call sieve_screen to analyze everything in the data room. Provide company_name to create a new deal (or find existing), or deal_id to add to an existing deal. Provide exactly one content source: file_path (local file), text (raw text/markdown), or url (fetch from URL). Args: title: Document title (e.g. "Pitch Deck Q1 2026"). company_name: Company name -- creates deal if new, finds existing if not. deal_id: Add to an existing deal (from sieve_deals or previous sieve_dataroom_add). website_url: Company website URL (used when creating a new deal). document_type: Type: 'pitch_deck', 'financials', 'legal', or 'other'. file_path: Path to a local file (PDF, DOCX, XLSX). The tool reads and uploads it. text: Raw text or markdown content (alternative to file). url: URL to fetch document from (alternative to file).
    Connector
  • Built-in product help — ask a natural-language "how do I…" question about Fastio and get a grounded, product-aware answer (or a short clarifying question) back in one call. EXPLAIN-ONLY / ADVISORY: it returns GUIDANCE TEXT and performs NO platform action (it will not create shares, move files, or change anything) — read the guidance, then act with the other tools. Answers are grounded in Fastio's own how-to knowledge AND phrased in terms of these MCP tools — they name the concrete `<tool> action="…"` calls to make — so prefer this over guessing endpoints or burning exploratory calls. For Q&A over YOUR uploaded files (RAG) use the `ai` tool instead — `how-to` answers questions about Fastio ITSELF. FREE and requires only an authenticated user (no org, no plan gate, no billing). Call action='describe' for the full action/param reference.
    Connector
  • Send structured feedback to the Kifly team. **Call after a confusing response, a dead-end, or a successful workaround you had to invent** — it's how we improve the agent surface. Fire-and-forget: returns 202 immediately, no blocking, safe to skip if it would add latency to a user-facing flow. `category` and `severity` are required enums (don't free-form them). Include `context` with what you were doing (tool called, query used, response shape, what you expected). Add `suggested_fix` only if you have a concrete idea. Rate-limited to 10/min per agent token; everything is reviewed before influencing anything.
    Connector
  • Orientation for wiring a redu.cloud capability (backups, DNS, extra storage, a managed DB, ...) INTO an app already deployed on redu, e.g. 'add a backup feature to the Supabase I deployed on redu'. Explains the pattern: mint a LEAST-PRIVILEGE scoped API key (with the user's approval via create_api_key), inject it into the app, and call the redu API from the app. Call this when a user asks to add/integrate a redu feature into a running deployment and you are unsure how.
    Connector