com.sketchxflow/mcp

Insert an image into an existing design — a poster, creative, or any page. Either AI-GENERATE one from `prompt` (costs coins, respects the project's AI-image toggle) OR drop in an existing image by `image_url` (a public http(s) URL). Optional `placement` positions it ('top right', 'center', 'bottom left', …) — it goes in as a movable overlay you can reposition/resize afterward with sketchxflow_edit. Then view the result with sketchxflow_get_image.

List the brand kits (saved brand identities — name, palette, fonts, voice) in your account, to attach to a launch kit via brand_kit_id.

Pick up a generation that was still running when the tool call returned. Pass the job_id from a '⏳ Still …' reply; this waits for it and returns the finished result, or reports how far along it is. Safe to call repeatedly — it only reads, so it never charges again and never starts a second run. This is the RIGHT response to a '⏳ Still …' reply; re-sending the original request is not, because that starts a second job and charges for it.

Use BEFORE designing when the brief is thin. Send the user's latest message (and the running `vision` + `history` from prior turns); get back a reply to relay, the updated `vision` board, `ready` (true when there's enough to design), and `missing` topics. When ready, the response includes `design_prompt` — pass that to sketchxflow_design_page. Free. Loop this with the user one question at a time.

Generate a motion-graphics ANIMATION from a brief — a branded intro / logo reveal / kinetic-typography sting, or a product demo. It becomes a self-contained, auto-playing motion page (timeline JSX). Optionally GROUND it on an existing project (`source_project_id` — its pages render to REAL screenshots that animate into the video), a logo (`source_logo_id`), and/or a live URL. Async (~1–4 min); the result preview_url plays the animation. MP4 export is coming; for now share the preview URL.

Design a brand LOGO from a name + brief — a symbol mark plus wordmark, lockups, and favicons. Optionally ground it on an existing project so it inherits that brand's palette/fonts. Async; streams progress (~1–3 min). Returns a displayable logo image URL you can drop into a design with sketchxflow_add_image(image_url=…).

Generate a fixed-canvas graphic — a flyer, poster, social post/story, or an AD creative for Meta / Instagram / Google (feed, story, reel, leaderboard, rectangle, skyscraper, mobile banner, billboard…) — from a brief. Pick the placement via `format`. Returns a preview URL and a rendered PNG. This is for STATIC creatives, distinct from sketchxflow_design_page (which builds websites/app screens). Takes ~1–3 min; streams progress. Refine it with sketchxflow_edit and pull markup with sketchxflow_get_code (slug 'home').

Generate a responsive, client-safe HTML email — newsletter, welcome, promotional, announcement, transactional, or event invite — from a brief. Uses email-safe rules (table layout, inline CSS, 600px column) so it renders in Gmail / Apple Mail / Outlook. Returns a preview URL and a rendered PNG; pull the HTML with sketchxflow_get_code (slug 'home'). Distinct from sketchxflow_design_page (websites) and sketchxflow_design_creative (static graphics). Takes ~1–3 min; streams progress.

Generate ONE polished page. Omit project_id to start a NEW project (creates the project + its first page). Pass an existing project_id to ADD a page to that project (brand-consistent). IMPORTANT: if the user wants a MOBILE app or phone screen (iOS/Android/app UI), you MUST set platform='mobile' — it defaults to a web/desktop design otherwise. Returns a preview URL; call sketchxflow_get_code to pull the HTML to implement. Takes 1–9 min; streams progress.

Apply a natural-language change to one page — e.g. 'make the hero darker', 'tighten the pricing section', 'swap the testimonial for a logo wall'. Brand-locked: edits stay on-palette/on-type. Returns the updated page; call sketchxflow_get_code for the new HTML.

One turn with the art director WITHOUT applying anything: pass what the user said and get back a revised proposal for the next layer. Use it when they want to change direction, ask a question, or think out loud before committing — 'warmer than that', 'what would you do instead?', 'can we skip the imagery for now?'. Free, instant, no coins. Loop this with the user, then apply with sketchxflow_experimental_layer. WHEN TO USE: for ONE surface (a page or a screen) the user wants to shape WITH you section by section rather than receive finished — 'let's design this together', 'I want to iterate on the look', 'build it up and show me'. For a page they just want generated, sketchxflow_design_page is one call and is the right tool; for a multi-page site, use sketchxflow_plan. This is a CONVERSATION: relay the director's reply to the user, get their answer, and pass it back — do not run the whole stack unless they have said to.

Stack ONE layer onto the design and return what it put down plus the director's next proposal. This is the step that costs coins. A SECTION layer is small and quick (a few seconds, ~3 coins) because it rewrites only that section; a whole-page finishing pass rewrites the document and costs more. The very first call always STAGES the page (the section shells) whatever else you pass. Pass `steer` to fold the user's words into the pending layer, or `kind` + `instruction` to say exactly what this layer is. `count` runs several layers back to back WITHOUT stopping to ask: only pass it when the user has explicitly said to keep going (e.g. 'just build the rest'), because each layer in the run is charged. After it returns, relay the next proposal to the user. WHEN TO USE: for ONE surface (a page or a screen) the user wants to shape WITH you section by section rather than receive finished — 'let's design this together', 'I want to iterate on the look', 'build it up and show me'. For a page they just want generated, sketchxflow_design_page is one call and is the right tool; for a multi-page site, use sketchxflow_plan. This is a CONVERSATION: relay the director's reply to the user, get their answer, and pass it back — do not run the whole stack unless they have said to.

Read a layered design's build: which sections exist, what is stacked inside each one, which whole-page passes have run, and what the director proposes next. Use it to get the section ids before targeting a layer. Pass `revert_to` to PEEL LAYERS BACK OFF — `revert_to=3` keeps the first three and discards everything above them, restoring the canvas to exactly how it looked then (`revert_to=0` clears it entirely). Reverting is free and instant, because each layer was snapshotted when it was applied — but it DISCARDS those layers, so confirm with the user before passing it. Omit it to just read. WHEN TO USE: for ONE surface (a page or a screen) the user wants to shape WITH you section by section rather than receive finished — 'let's design this together', 'I want to iterate on the look', 'build it up and show me'. For a page they just want generated, sketchxflow_design_page is one call and is the right tool; for a multi-page site, use sketchxflow_plan. This is a CONVERSATION: relay the director's reply to the user, get their answer, and pass it back — do not run the whole stack unless they have said to.

Open an EXPERIMENTAL DESIGN session: one surface, built the way a designer builds one — a SECTION at a time, each section STACKED up a layer at a time (a ground plane, shapes over it, the copy, imagery, effects), then whole-page passes at the end to make the sections agree. Returns the SECTION PLAN plus the art director's opening reply and the first layer proposal, for you to relay to the user. Free and instant; nothing is rendered and no coins are spent until sketchxflow_experimental_layer. WHEN TO USE: for ONE surface (a page or a screen) the user wants to shape WITH you section by section rather than receive finished — 'let's design this together', 'I want to iterate on the look', 'build it up and show me'. For a page they just want generated, sketchxflow_design_page is one call and is the right tool; for a multi-page site, use sketchxflow_plan. This is a CONVERSATION: relay the director's reply to the user, get their answer, and pass it back — do not run the whole stack unless they have said to.

Generate every page of a project's saved site plan, in one consistent pass. This is the step that costs coins and takes time (a few minutes, scaling with the page count); streams progress. Call it once the user is happy with the plan from sketchxflow_plan / sketchxflow_refine_plan — building is where changes get expensive, so settle the plan first. Then pull each page's HTML with sketchxflow_get_code. WHEN TO USE: only for MULTI-PAGE sites (roughly 3+ pages). Planning first produces markedly better multi-page results — the model gets the whole site map before it writes any page, so navigation, tone and structure stay consistent across them. For a SINGLE page it is the wrong call: it is two extra round trips and an extra coin charge for no gain, and sketchxflow_design_page alone is the right tool. NOT a substitute for sketchxflow_clarify, and not an alternative to it: clarify INTERVIEWS THE USER to build a brief and produces no plan; these tools take a finished brief and produce a site map. The full sequence when the brief is thin is clarify (loop with the user) → plan → refine_plan → generate_from_plan.

Return the full HTML (Tailwind inline) of a generated page so you can re-implement or adapt it into the user's codebase (React/Next/Vue/plain HTML). Call after sketchxflow_design_page / sketchxflow_edit.

Return a rendered screenshot (PNG) of a page so you can SEE how the design actually looks. Use it to visually verify or critique a design after sketchxflow_design_page / sketchxflow_design_creative / sketchxflow_edit, before implementing or iterating. slug 'home' is the main page / creative.

Project status: preview URL + page list (slug/name).

Generate a complete, on-brand LAUNCH KIT from one brief — a landing page + launch email + social posts + poster, all consistent. Auto-creates a brand (palette/fonts) if none is attached. Returns the set of preview URLs + project IDs. Takes ~3–8 min; streams progress. Pull any asset's code with sketchxflow_get_code (slug 'home').

List the models you can pick — BOTH catalogs, kept separate: the LLM TEXT models for the `model` parameter (the model that writes the page) and the IMAGE models for `image_model` (the model that renders the pictures in it). Each entry carries a description, speed, relative cost, coin rates, and whether YOUR plan can actually use it. Also reports your plan, the defaults used when the parameters are omitted, and how to unlock selection if it's locked. The two id lists do not overlap and are not interchangeable. Free, instant, no coins. Call this before passing `model` or `image_model`, or to answer 'which models can I use?'.

List the projects in your SketchXFlow account (most recent first).

Create the project and produce its SITE PLAN — the page list (slug, name, purpose) and each page's section breakdown — for review BEFORE any HTML is generated. Fast and synchronous; the plan is saved server-side against the returned project_id. Show it to the user, adjust with sketchxflow_refine_plan, then build with sketchxflow_generate_from_plan. WHEN TO USE: only for MULTI-PAGE sites (roughly 3+ pages). Planning first produces markedly better multi-page results — the model gets the whole site map before it writes any page, so navigation, tone and structure stay consistent across them. For a SINGLE page it is the wrong call: it is two extra round trips and an extra coin charge for no gain, and sketchxflow_design_page alone is the right tool. NOT a substitute for sketchxflow_clarify, and not an alternative to it: clarify INTERVIEWS THE USER to build a brief and produces no plan; these tools take a finished brief and produce a site map. The full sequence when the brief is thin is clarify (loop with the user) → plan → refine_plan → generate_from_plan.

Apply one natural-language change to a project's saved site plan and return the updated plan — 'add a careers page', 'drop the blog', 'the pricing page needs a comparison table', 'reorder so About comes before Pricing'. Fast and synchronous; nothing is built yet, so this is the cheap place to iterate. Loop it with the user until the page list is right, then call sketchxflow_generate_from_plan. Requires a plan created by sketchxflow_plan. WHEN TO USE: only for MULTI-PAGE sites (roughly 3+ pages). Planning first produces markedly better multi-page results — the model gets the whole site map before it writes any page, so navigation, tone and structure stay consistent across them. For a SINGLE page it is the wrong call: it is two extra round trips and an extra coin charge for no gain, and sketchxflow_design_page alone is the right tool. NOT a substitute for sketchxflow_clarify, and not an alternative to it: clarify INTERVIEWS THE USER to build a brief and produces no plan; these tools take a finished brief and produce a site map. The full sequence when the brief is thin is clarify (loop with the user) → plan → refine_plan → generate_from_plan.

Freeze the requirements and price them from the price list. Only with the client's explicit go-ahead. Returns whether the proposal issued and the link to read, accept and pay it on the website (sign-in needed).

Every invoice on a project with its status and, for an open one, the page to pay it (UPI, cards, EMI, net banking or bank transfer; sign-in needed). Free.

Your projects with SketchXFlow's development services — the ones you've asked the team to build — with their state and links. Free.

The requirements document the consultant is writing (sections, numbered requirements, modules), plus whether it can be finalised. Free.

One turn of the requirements interview: send what the client said, get the consultant's reply, the question they should answer next (with options if any) and the live estimate from the price list. Free. Keep going until can_finalise is true, then call sketchxflow_services_finalise.

Ask SketchXFlow to BUILD something for real (a website, web app or mobile app) at a fixed price from the public price list. Opens a project and returns the AI consultant's first question. Free; nothing is committed until a proposal is accepted on the website.

Report which version of the SketchXFlow MCP server is running, whether a newer one is published, and whether the SketchXFlow API accepts your SKETCHXFLOW_API_KEY (shown only by its sk_live_ab12cd… prefix). Free, instant, no coins. Call it when another tool fails with an API-key error, or to check for updates.