Blender integration through the Model Context Protocol
Nothing to run from here
LogoLab is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
94/100
trust score
216
downloads a day
local
runs on your machine
2k
downloads in 30d
What it does
Trace an image to a clean SVG and export a full app-icon set, locally, from your coding agent.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user logolab-mcp '--' npx -y logolab
# 2 — ask your agent for something these tools do
# inspect_icon, trace_icon, export_icons and 2 more
LogoLab costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
PublisherVerified · since 2026
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts LogoLab as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user logolab-mcp '--' npx -y logolabReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Report what an image is (size, format, transparency) and what the tracer WOULD do with it — colour vs mono, gradients on or off, the mono cut, the resolution it would trace at — without tracing. Fast. Use it to sanity-check a source, or to explain a choice before overriding it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| image | string | yes | Path to a PNG, JPEG, WebP, GIF, BMP or SVG file. Relative paths resolve against the working directory. |
Vectorize a raster image into a clean, editable SVG: colour regions become real shapes with fitted curves, not a traced outline of pixels. Decides colour vs mono, gradient fitting and trace resolution automatically (override with the options). Writes the .svg and reports path count, node count and…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| image | string | yes | Path to the image to trace (PNG, JPEG, WebP, GIF, BMP, or an SVG to re-trace). |
| out | string | no | Where to write the SVG. Default: next to the source, same name, .svg extension (<name>.traced.svg when the source is itself that .svg, so it is never overwritten). |
| inline | boolean | no | Also return the SVG markup in the response (only do this for small icons). |
Render a logo (SVG or raster) into a complete icon collection on disk. Presets: … An SVG source is rendered analytically at every size, so a 16px favicon is drawn, not downsampled. Maskable/adaptive icons get the platform safe zone automatically (Android keeps only the centre 66% circle). Also…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| image | string | yes | Path to the logo: an SVG (best — rendered crisply at every size) or a raster image. |
| outDir | string | yes | Directory to write into. Files land in the layout each preset expects (public/, src-tauri/icons/, res/, …). |
| presets | array | no | Which collections to write. Default ["pwa"]. Several may be combined. |
| sizes | array | no | Extra arbitrary sizes, written to icons/icon-<n>.png. |
| appName | string | no | Name used in the webmanifest and the logolab-icons.md notes. Default "App". |
| appearance | object | no | How the logo sits in the icon. Defaults keep the source art full-bleed and transparent; the icons that must be opaque take opaque. |
The whole pipeline in one call: trace the image to a clean SVG, then render that SVG into the icon collections asked for. This is the tool to use on an AI-generated icon. Presets: …
| Parameter | Type | Required | Notes |
|---|---|---|---|
| image | string | yes | Path to the generated or drawn icon image. |
| outDir | string | yes | Directory to write the icon set into. |
| presets | array | no | Collections to write. Default ["pwa"]. |
| sizes | array | no | Extra arbitrary PNG sizes. |
| appName | string | no | Name used in the webmanifest and the logolab-icons.md notes. |
| appearance | object | no | How the logo sits in the icon. Default: full-bleed, transparent; the icons that must be opaque take opaque. |
| keepSvg | string | no | Also write the traced SVG here (a copy is placed inside the collection anyway). |
Cut a CONTACT SHEET — a grid of many icons on one canvas, which is what image models usually return for "a set of icons" — into individual traced SVGs. Detects the tiles (grid or free layout; pass grid when you know the layout, which also keeps an icon drawn as separate pieces whole), crops each…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sheet | string | yes | Path to the sheet image. |
| outDir | string | yes | Directory to write one SVG per detected icon into. |
| prefix | string | no | File-name stem: <prefix>-01.svg. Default: the sheet file name. |
| names | array | no | File names for the icons in READING order (row-major, top-left first): ["home", "search", …] writes home.svg, search.svg, …. Icons past the end of the list keep <prefix>-nn. |
| grid | object | no | The layout, when you know it: { rows, cols }. Everything inside one cell is one icon, however far apart its pieces are (a dashed curve, four corner brackets, a dashboard of four rectangles) — the case |
| mode | string | no | Per-tile colour decision. Default auto. |
| gradients | string | no | Default auto. |
| strokes | yes | — | |
| strokesOnly | yes | — | |
| layering | yes | — | |
| removeBackground | boolean | no | Default TRUE on a sheet: tiles come back transparent. Pass false to keep each tile's paper as a rectangle under the ink. |
| detail | yes | — | |
| smoothing | yes | — | |
| despeckle | yes | — | |
| fidelity | yes | — | |
| keepCrops | boolean | no | Also write each tile as a PNG next to its SVG. |
| limit | integer | no | Trace at most this many tiles (tracing is the slow part). A limited run is a preview: it removes nothing. |
| padding | number | no | Padding around each icon as a fraction of its long side. Default 0.08. |
| threshold | number | no | How far from the paper colour a pixel counts as ink. Default 24. |
| gap | number | no | Force the grouping gap in source px. Omit to detect it; prefer grid when the layout is known. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install LogoLab or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 94 / 100
Release 0.7.0 · scanned 13 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score94
Findings1 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digestd14c046853ca43e7b9c238f869de2326a10b993d17c083af55a80e9349dda58d
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (5 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| inspect_icon | no tags | |
| trace_icon | no tags | |
| export_icons | no tags | |
| make_app_icons | no tags | |
| split_icon_sheet | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestd14c046853ca43e7
Scanned2026-10-13
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.7.0. Pin a release below and the command asks for exactly that one.
0.7.0
12 Oct 2026
latestNo release note was published with this version.
0.4.0
6 Oct 2026
No release note was published with this version.
0.3.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish LogoLab can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.