com.sketchxflow/mcp
NPM · @SKETCHXFLOW/MCP · 2 COMPONENTS
Design websites, apps and logos with SketchXFlow — and brief its development team.
Available components
Last scanned (12 hours ago)
Scores higher than 41% of npm servers
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 33 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 11911 tokens (~350/item across 34 items; 34 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage97
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 91% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 34 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 34 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Nov 26 0
- Stability: 0.97 → pass security
- 18 Nov 26 0
- Stability: pass → 0.97 functional
- 12 Nov 26 0
- Stability: 0.97 → pass security
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Nov 26 −3
- Stability: pass → 0.77 functional
- 24 Oct 26 −6
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@sketchxflow/mcp@0.26.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 33 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
sketchxflow_add_image Add an image to a design (poster / creative / page) ~482
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.
| Name | Type | Req | Description |
|---|---|---|---|
| alt | string | – | Alt text for the image. |
| height | number | – | Generated image height in px (default 600). Only used with prompt. |
| image_model | string | – | Optional. Pin which model generates this design's AI images — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific image model: omitting uses the account's default (g… |
| image_url | string | – | Public http(s) URL of an existing image to insert. Provide this OR prompt. |
| placement | string | – | Where to place it: top left / top right / bottom left / bottom right / top / bottom / left / right / center. Default center. |
| project_id | string | yes | The project to add the image to. |
| prompt | string | – | Describe an image to AI-generate (costs coins). Provide this OR image_url. |
| slug | string | – | Page slug. Default 'home' (the main page / creative). |
| width | number | – | Generated image width in px (default 800). Only used with prompt. |
No output schema declared.
No examples provided.
sketchxflow_brand_kits List your saved brand kits ~45
List the brand kits (saved brand identities — name, palette, fonts, voice) in your account, to attach to a launch kit via brand_kit_id.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sketchxflow_check_job Collect a design that was still building ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| job_id | string | yes | The job_id from a '⏳ Still building' reply. |
No output schema declared.
No examples provided.
sketchxflow_cinematic_hero Film a page's hero into a scroll video ~203
Film a designed page so scrolling plays it like a 3D film: the camera ORBITS the hero subject (AI video from the photo itself, so people, styling and set stay the same), then flies into up to two later sections' photographs; each film is held full-screen while the scroll plays it, with depth on the text and sections tilting into place. Photos stay as the fallback (reduced motion, frames loading). Web pages only; paid (~80 coins for the hero + ~60 per scene transition, charged on the real video cost; transitions are skipped when the balance is short). Takes a few minutes. Use it when the user wants the site to feel cinematic or 'like the TikTok/Awwwards sites'. For a new design, pass cinematic_hero=true to sketchxflow_design_page instead.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The design. |
| slug | string | – | Which page (default 'home'). |
No output schema declared.
No examples provided.
sketchxflow_clarify Ask the user design questions ~390
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.
| Name | Type | Req | Description |
|---|---|---|---|
| history | array | – | Prior turns (echo back what you got last call). |
| message | string | yes | The user's latest answer / the initial idea. |
| model | string | – | Optional. Pin which LLM generates this — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific model: omitting uses the account's default (gemini-3-flash-preview) and… |
| platform | string | – | – |
| vision | – | – | The `vision` object returned last call — pass it back each turn. |
No output schema declared.
No examples provided.
sketchxflow_create_animation Generate an animation / product-demo video ~1,129
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. Pick the canvas with `format` (YouTube 16:9, Reels/Shorts/TikTok 9:16, square, 4:5). A DEMO can add production layers, each ON DEMAND and billed at its real cost — leave them off unless the user asks: `voiceover` (a narrated script; scenes are timed to it), `music: "generated"` (a composed track instead of the free ambient bed) and `ai_clip` (Veo or Omni b-roll under the hook — by far the costliest, ~60–120 coins, and adds minutes). Async (~1–4 min, up to ~10 with an AI clip); the result preview_url plays it, and the preview page's Export menu downloads an MP4 in any format.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_clip | string | – | DEMO only, on demand and EXPENSIVE (~60–120 coins, adds minutes): generate cinematic b-roll under the opening hook with Google Veo or Gemini Omni. Default none — only set it when the user explicitly… |
| brand_kit_id | string | – | Attach a saved brand kit (see sketchxflow_brand_kits). |
| captions | boolean | – | DEMO with voiceover: burn the narration in as captions (default true). |
| demo | boolean | – | Set true for a PRODUCT DEMO VIDEO: the attached screenshots (from source_project_id pages / source_url / images) are VISION-UNDERSTOOD and turned into a multi-scene demo (hook → feature scenes with r… |
| duration | number | – | Length in seconds (3–15, default 6; a demo allows up to 20 and defaults to 12). |
| format | string | – | Canvas. 16x9 = YouTube/web (default); 9x16 = Reels, Shorts, TikTok; 1x1 = square feed post; 4x5 = Instagram/Facebook feed portrait. |
| model | string | – | Optional. Pin which LLM generates this — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific model: omitting uses the account's default (gemini-3-flash-preview) and… |
| music | string | – | DEMO only. ambient (default) = a free procedural bed that plays in the browser only; generated = a composed instrumental track, on demand (extra cost), also mixed into MP4 exports; none = silent. |
| prompt | string | yes | The animation brief — what it's for, the message/vibe, what to highlight. |
| source_logo_id | string | – | Feature one of your created logos in the animation. |
| source_project_id | string | – | Ground on this existing project — its pages render to real screenshots that animate in (great for product demos). |
| source_url | string | – | A live product URL to screenshot and feature. |
| style | string | – | DEMO feel. calm (default) = a confident, unhurried keynote. hype = a supercharged launch trailer — punchy 2-3 beat script, fast cuts, flashes and punch-ins, a driving track — for energy-drink-style o… |
| video_model | string | – | DEMO with ai_clip: which video model films the clip. veo-fast (default, ~120 coins/8s), veo (highest quality, ~320), omni (~80), veo-lite (cheapest, ~40). Only set when the user asks for a specific m… |
| voice | string | – | DEMO with voiceover: the narrator voice — one of Sulafat (warm), Algieba (smooth), Charon (informative), Kore (firm), Puck (upbeat), Fenrir (excitable), Achernar (soft), Leda (youthful). Default: mat… |
| voiceover | boolean | – | DEMO only, on demand (small extra cost): narrate the video with a script written for the product. Scenes are timed to the voice, so the final length follows the narration. |
No output schema declared.
No examples provided.
sketchxflow_create_logo Generate a brand logo ~619
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=…).
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | What the brand does — one or two sentences. Grounds the symbol concept. |
| image_model | string | – | Optional. Pin which model generates this design's AI images — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific image model: omitting uses the account's default (g… |
| model | string | – | Optional. Pin which LLM generates this — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific model: omitting uses the account's default (gemini-3-flash-preview) and… |
| name | string | yes | The brand name to put on the logo (required). |
| source_project_id | string | – | Ground the logo on this existing project's palette/fonts/brand so it matches the site you already designed. |
| vibes | array | – | Visual vibe chips, e.g. ['minimal','bold','technical','warm','playful','refined','premium','earthy']. |
| website | string | – | Brand website to research for grounding (optional). |
No output schema declared.
No examples provided.
sketchxflow_design_creative Design a creative (flyer / poster / social) ~805
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').
| Name | Type | Req | Description |
|---|---|---|---|
| ai_images | boolean | – | Generate AI imagery (default true). false = type/color/shape only. |
| format | string | – | Canvas format. Default instagram_post (1080×1080). General: instagram_story 1080×1920, poster_a4 print, flyer, x_post/linkedin_post/youtube_thumbnail landscape. AD FORMATS — Meta: meta_feed_landscape… |
| image_model | string | – | Optional. Pin which model generates this design's AI images — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific image model: omitting uses the account's default (g… |
| model | string | – | Optional. Pin which LLM generates this — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific model: omitting uses the account's default (gemini-3-flash-preview) and… |
| prompt | string | yes | The creative brief — what it's for, the message/headline, the vibe, any details (date, price, handle, URL). |
No output schema declared.
No examples provided.
sketchxflow_design_email Design an email template (HTML email) ~623
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_images | boolean | – | Generate AI imagery (default true). false = type/color/layout only. |
| email_type | string | – | Email type. Default newsletter. welcome = onboarding; promotional = offer/sale; transactional = receipt/confirmation; event = invite. |
| image_model | string | – | Optional. Pin which model generates this design's AI images — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific image model: omitting uses the account's default (g… |
| model | string | – | Optional. Pin which LLM generates this — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific model: omitting uses the account's default (gemini-3-flash-preview) and… |
| prompt | string | yes | The email brief — purpose, subject/headline, key message, CTA, and any details (offer, dates, links). |
No output schema declared.
No examples provided.
sketchxflow_design_page Design a page (new project or add to one) ~854
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_images | boolean | – | – |
| build_3d | boolean | – | Commission a bespoke 3D model in the user's OWN Blender instead of casting one from the stock library. Requires enable_3d AND a machine paired via Account -> Machines with the SketchXFlow bridge runn… |
| cinematic_hero | boolean | – | Web only, paid (AI video: ~80 coins for the hero + ~60 per scene transition). Once the page is built it is filmed so scrolling plays it like a 3D film: the camera orbits the hero subject, then flies… |
| enable_3d | boolean | – | – |
| image_model | string | – | Optional. Pin which model generates this design's AI images — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific image model: omitting uses the account's default (g… |
| model | string | – | Optional. Pin which LLM generates this — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific model: omitting uses the account's default (gemini-3-flash-preview) and… |
| name | string | – | Page name/title (used when adding to a project, e.g. 'Pricing'). Defaults from the prompt. |
| platform | string | – | Target surface for a NEW project. Set 'mobile' for a mobile app / phone screen / iOS / Android / app UI; 'web' for websites and desktop. Defaults to web — so if the user asked for anything mobile, yo… |
| project_id | string | – | Existing project to add this page to. Omit to create a new project. |
| prompt | string | yes | What this page is — the brief. |
No output schema declared.
No examples provided.
sketchxflow_edit Edit a page section/component ~336
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.
| Name | Type | Req | Description |
|---|---|---|---|
| instruction | string | yes | The change to make. |
| model | string | – | Optional. Pin which LLM generates this — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific model: omitting uses the account's default (gemini-3-flash-preview) and… |
| project_id | string | yes | – |
| slug | string | yes | Which page (e.g. 'home', 'pricing'). |
No output schema declared.
No examples provided.
sketchxflow_experimental_discuss Talk over the next layer (Experimental) ~526
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.
| Name | Type | Req | Description |
|---|---|---|---|
| auto | boolean | – | Turn auto-pilot on or off. Only set true if the user explicitly asked for the rest to be filled in without being asked each time. |
| message | string | yes | What the user just said, in their words. |
| model | string | – | Optional. Pin which LLM generates this — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific model: omitting uses the account's default (gemini-3-flash-preview) and… |
| project_id | string | yes | The layered session (from sketchxflow_experimental_start). |
No output schema declared.
No examples provided.
sketchxflow_experimental_layer Apply the next layer (Experimental) ~1,026
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.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Apply this many layers in one run without stopping to ask. Requires the user's explicit go-ahead — every layer in the run is charged. Defaults to 1. |
| image_model | string | – | Optional. Pin which model generates this design's AI images — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific image model: omitting uses the account's default (g… |
| instruction | string | – | Replace the director's proposal with your own brief for this layer. Be specific — hexes, geometry, placement in the stack. Changes exactly what it names and nothing else. |
| model | string | – | Optional. Pin which LLM generates this — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific model: omitting uses the account's default (gemini-3-flash-preview) and… |
| project_id | string | yes | The layered session (from sketchxflow_experimental_start). |
| role | string | – | What KIND of layer this is. Only with `instruction`. SECTION roles: backdrop=the ground plane, shape=geometry over it, content=the copy, media=imagery, effect=grain/glass/glow. PAGE passes: palette,… |
| scope | string | – | 'section' (default) stacks a layer inside ONE section. 'page' runs a whole-page finishing pass — only worth doing once every section is built. |
| section_id | string | – | Which section to stack into, e.g. 'hero'. Required when you pass `instruction` with scope='section'. Read the ids from sketchxflow_experimental_stack. |
| steer | string | – | The user's steer on the pending layer, folded into its brief — 'warmer, less orange', 'push the panel further left'. |
| title | string | – | A short name for the layer, when you're specifying it yourself. |
No output schema declared.
No examples provided.
sketchxflow_experimental_revert Peel layers back off (Experimental) ~242
PEEL LAYERS BACK OFF a layered design — `to_layer=3` keeps the first three layers and discards everything above them, restoring the canvas to exactly how it looked then (`to_layer=0` clears it entirely). Free and instant, because each layer was snapshotted when it was applied — but the discarded layers are gone, so confirm with the user first. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The layered session. |
| to_layer | integer | yes | Keep this many layers and discard the rest. |
No output schema declared.
No examples provided.
sketchxflow_experimental_stack Read the layer stack (Experimental) ~209
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. Read-only — to peel layers back off, use sketchxflow_experimental_revert. 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.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | The layered session. |
No output schema declared.
No examples provided.
sketchxflow_experimental_start Start a layered design (Experimental) ~615
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.
| Name | Type | Req | Description |
|---|---|---|---|
| auto | boolean | – | Put the director on auto-pilot from the start — it stops asking and fills the layers in itself. Set this ONLY if the user has said they want it built without being asked each time. |
| model | string | – | Optional. Pin which LLM generates this — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific model: omitting uses the account's default (gemini-3-flash-preview) and… |
| platform | string | – | Target surface. 'mobile' for a phone screen / app UI; defaults to web. |
| project_id | string | – | Layer on top of an EXISTING project instead of creating one. Omit for a new design. |
| prompt | string | yes | The brief — what this design is, who it's for, and any direction the user has already given. |
| slug | string | – | Which page of the project to build. Defaults to 'home'. |
No output schema declared.
No examples provided.
sketchxflow_generate_from_plan Build the site from its saved plan ~693
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.
| Name | Type | Req | Description |
|---|---|---|---|
| image_model | string | – | Optional. Pin which model generates this design's AI images — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific image model: omitting uses the account's default (g… |
| model | string | – | Optional. Pin which LLM generates this — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific model: omitting uses the account's default (gemini-3-flash-preview) and… |
| project_id | string | yes | The project whose saved plan should be built. |
No output schema declared.
No examples provided.
sketchxflow_get_code Get a page's HTML to implement ~83
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
| slug | string | yes | Page slug, e.g. 'home'. |
No output schema declared.
No examples provided.
sketchxflow_get_image See a page's rendered design ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
| slug | string | – | Page slug. Default 'home'. |
No output schema declared.
No examples provided.
sketchxflow_get_project Get a project's status ~31
Project status: preview URL + page list (slug/name).
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
No output schema declared.
No examples provided.
sketchxflow_launch_kit Generate a launch kit (landing + email + socials + poster) ~594
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').
| Name | Type | Req | Description |
|---|---|---|---|
| ai_images | boolean | – | Generate AI imagery (default true). false = type/color/layout only. |
| brand_kit_id | string | – | Attach a saved brand kit (see sketchxflow_brand_kits). Omit to auto-create + save a brand from the brief. |
| image_model | string | – | Optional. Pin which model generates this design's AI images — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific image model: omitting uses the account's default (g… |
| model | string | – | Optional. Pin which LLM generates this — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific model: omitting uses the account's default (gemini-3-flash-preview) and… |
| prompt | string | yes | The launch brief — what's launching, who it's for, the message, and any details (date, offer, link). |
No output schema declared.
No examples provided.
sketchxflow_list_logos List your logos ~58
List the logos in your SketchXFlow account (newest first) with each one's id, current colours in slot order (most dominant first) and image URL. Use the id with sketchxflow_recolor_logo. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sketchxflow_list_models List the LLM models you can pick ~150
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?'.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sketchxflow_list_projects List your projects ~25
List the projects in your SketchXFlow account (most recent first).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sketchxflow_plan Plan a multi-page site (before generating) ~526
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.
| Name | Type | Req | Description |
|---|---|---|---|
| model | string | – | Optional. Pin which LLM generates this — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific model: omitting uses the account's default (gemini-3-flash-preview) and… |
| platform | string | – | Target surface. 'mobile' for a mobile app / phone screens; defaults to web. |
| prompt | string | yes | The brief for the whole site — what it is, who it's for, and any pages you already know it needs. |
No output schema declared.
No examples provided.
sketchxflow_recolor_logo Change a logo's colours ~298
Change the COLOURS of an existing logo without redesigning it: the symbol's shape, the wordmark and the lockups stay exactly as they are; only the colours change. Instant, free, and no AI involved. Either give `replace` — {old: new} hex swaps, e.g. {"#ff5500": "#0a7d4f"} changes just that colour — or a whole new `palette` in the logo's slot order (most dominant first; at most as many colours as the logo was made with). Get the current colours from sketchxflow_list_logos. Pass `project_id` when a design shows this logo, so its copies switch to the new colours too. The previous colours are kept as one step of history in the logo page's Revert. For a genuinely new logo, use sketchxflow_create_logo instead.
| Name | Type | Req | Description |
|---|---|---|---|
| logo_id | string | yes | The logo's id (from sketchxflow_list_logos or sketchxflow_create_logo). |
| palette | array | – | A whole new set of #RRGGBB colours in slot order (most dominant first). Use this OR replace. |
| project_id | string | – | A design that shows this logo — its logo images move to the new colours. |
| replace | object | – | Colour swaps, {"#old": "#new"}, applied to the logo's current colours. Colours not named stay. |
No output schema declared.
No examples provided.
sketchxflow_refine_plan Refine a saved site plan ~533
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.
| Name | Type | Req | Description |
|---|---|---|---|
| instruction | string | yes | The change to make to the plan (pages, their purpose, or their sections). |
| model | string | – | Optional. Pin which LLM generates this — a PAID-PLAN feature (Starter and above). OMIT IT unless the user asked for a specific model: omitting uses the account's default (gemini-3-flash-preview) and… |
| project_id | string | yes | The project returned by sketchxflow_plan. |
No output schema declared.
No examples provided.
sketchxflow_services_finalise Approve your build's requirements and get the proposal ~63
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).
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
No output schema declared.
No examples provided.
sketchxflow_services_invoices Your invoices and payment links for a build ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
No output schema declared.
No examples provided.
sketchxflow_services_projects List what you've asked SketchXFlow to build ~38
Your projects with SketchXFlow's development services — the ones you've asked the team to build — with their state and links. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sketchxflow_services_requirements Read the requirements drafted for your build ~78
For the CLIENT of a build: the requirements document SketchXFlow's consultant is writing for a project you asked the team to build (sections, numbered requirements, modules), plus whether it can be finalised. Free. The developers who build it work from a separate, team-only server.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
No output schema declared.
No examples provided.
sketchxflow_services_say Answer the consultant about your build ~97
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.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | What the client said, or the option they picked. |
| project_id | string | yes | – |
No output schema declared.
No examples provided.
sketchxflow_services_start Ask SketchXFlow's team to build something for you ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| brief | string | – | What you need built, in your own words — who it's for and what it should do. Paste an existing brief if you have one. |
| persona | string | – | Who you are, so the consultant talks your language: non_technical_founder, business_owner, developer (technical founder too), product_manager, agency (building for a client), or other. |
| title | string | – | A short working title, e.g. 'Clinic booking site'. |
No output schema declared.
No examples provided.
sketchxflow_version Check the SketchXFlow MCP version and API key ~83
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the com.sketchxflow/mcp server?
com.sketchxflow/mcp runs locally as an npm package, launched with npx -y @sketchxflow/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @sketchxflow/mcp
claude mcp add com-sketchxflow-mcp -- npx -y @sketchxflow/mcp
What is the com.sketchxflow/mcp server?
com.sketchxflow/mcp is listed in the public MCP registry as com.sketchxflow/mcp. Design websites, apps and logos with SketchXFlow, and brief its development team. This page covers its npm package (@sketchxflow/mcp).
Is the com.sketchxflow/mcp server safe to use?
com.sketchxflow/mcp scores 70 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.sketchxflow/mcp server expose?
com.sketchxflow/mcp exposes 34 tools: sketchxflow_version, sketchxflow_list_models, sketchxflow_clarify, sketchxflow_design_page, sketchxflow_cinematic_hero, and 29 more. Their descriptions and schemas cost roughly 11,911 tokens of context every time the server is loaded.
Is the com.sketchxflow/mcp server still maintained?
com.sketchxflow/mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.sketchxflow/mcp server under?
com.sketchxflow/mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the com.sketchxflow/mcp server?
VerifyMCP ran 15 checks on com.sketchxflow/mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about com.sketchxflow/mcp: Security disclosure. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.