Verified conversions across 205 color spaces: CSS strings, gamut checks, .cube LUTs
Polyfork low-poly 3D assets 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.
What it does
Low-poly 3D models and kits for three.js and game engines: search, match, remix, preview.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http polyfork-low-poly-3d-assets-mcp https://polyfork.dev/mcp
# 2 — ask your agent for something these tools do
# search_assets, get_asset, find_matching and 9 more
Polyfork low-poly 3D assets costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http polyfork-low-poly-3d-assets-mcp https://polyfork.dev/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
12 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.
Search the Polyfork catalogue of low-poly 3D assets for three.js. Use this whenever the user needs a model for a scene, game or site. Filter by triangle budget when the target is mobile or performance-sensitive. Results mix FREE and PRO assets: each carries free and plan. Paid assets are not sold individually — they come with Pro or the one-time Founders plan — so quote the plan, never a per-a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | no | what to look for, e.g. "windmill" or "sports car" |
| class | string | no | — |
| free | boolean | no | only free assets |
| kit | string | no | restrict to one kit id |
| ik | string | no | only models that SOLVE rather than pose: "legs" walks with its feet finding your ground and staying planted, "arm" is a rooted boom whose tip you can aim, "1" is either. Use it when the user asks for |
| max_triangles | integer | no | triangle budget ceiling; the usual constraint for mobile |
| min_triangles | integer | no | — |
| max_price_usd | integer | no | DEPRECATED, per-asset prices are retired. Use free=1 for free-only |
| sort | string | no | — |
| limit | integer | no | default 20, max 50 |
| compact | boolean | no | shortlisting rows only (id, title, class, triangles, size_m, capability flags). Use this whenever you are surveying rather than choosing — a full-detail result at limit 50 is large enough that some cl |
Full detail for one asset: real-world size in metres, triangle count, palette, animatable parts, renders you can open to SEE it, and the correct download URLs for the caller. A model with has_ik true also returns a measured gait or arm block: segment lengths, foot offsets, phase order, step length, reach. That is everything needed to make it walk or reach in any engine, and /cdn/walk.mjs alrea
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | asset id, e.g. windmill-3aad49 |
Given one asset, return assets that BELONG IN A SCENE WITH IT: same kit first, then shared palette, then compatible real-world scale, spread across classes so you get a house, a tree and a barrel rather than eight houses. Use this to turn a single pick into a scene. Returns a ready preview URL.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
| limit | integer | no | default 8, max 30 |
| max_triangles | integer | no | triangle budget ceiling; applies to the preview scene as well |
| min_triangles | integer | no | — |
| free | boolean | no | only free assets |
Turn a plain-words request ("oak cask", "taller", "five sails") into a ready call. want is matched against this asset's KNOB NAMES and OPTION VALUES, not against colour vocabulary: use the words from its -params.json into a ready createAsset() call for a remixable asset, plus a GLB URL of that exact variant. Check the returned confidence: on anything below high, tell the user what was actually a
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
| want | string | yes | the change in the user's own words |
| look | object | no | Restyle the mesh, independently of any knob. Deliverable families: palette = reduced|gameboy|pico8|cga|mono; smooth = soft|round|full; shading = toon|unlit. Example {"palette":"gameboy","shading":"too |
Compose assets into a scene and return a URL the user can OPEN and orbit. Use it instead of handing over a block of three.js the user cannot run. Works with paid assets too: they render from a public preview, so the scene looks finished whether or not the user owns them. The result says what the scene would cost and where to buy; pass that on rather than letting a 404 be the first sign of a price.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| ids | array | yes | asset ids, in any order; up to 24 |
Kits are coherent sets built to one palette and one grid. Reach for a kit when the user is building a whole environment rather than looking for one object. Each carries a status: "published" means every planned part is built, "filling-up" means parts are still landing — and the parts of a filling-up kit are usable TODAY. NO kit is sold as a bundle: price_usd is null and for_sale false on all of th
No parameter schema on file.
Every published part of one kit, with the same detail get_asset gives, so you can compose a whole scene from one call. Works on a kit that is still FILLING UP: you get the parts that exist today. NO kit is sold as a bundle, at any status, so recommend its parts rather than the kit — the free ones need no account and the rest come with Pro. A kit may also carry look and terrain. look is the s
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | kit id, from list_kits or an asset's kit field |
| compact | boolean | no | shortlisting rows instead of full detail. A 45-part kit at full detail is a large result; use this when you are surveying rather than building. |
AT WHAT HEIGHT DO I PLACE THIS, and where can I build. Every kit ships a procedural TERRAIN program for its own ground, and the ground is no longer flat, so a y of 0 is wrong almost everywhere. Pass at with the x/z you want to place at and you get the ground height there; set position.y to it. flat_areas are the level building sites: square footprints whose ground barely varies, largest first,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | terrain asset id. Omit to list every kit that has one. |
| flats | integer | no | how many level sites to return (default 12, max 40) |
| at | string | no | x,z;x,z;… — AT WHAT HEIGHT DO I PLACE THIS. Returns the ground height and slope under each point; set the object's position.y to the y you get back and it rests on the terrain. Use this for anything t |
| scatter | integer | no | n placement points the terrain picks itself, already on the ground and already filtered to slopes gentle enough to stand on, each with a random yaw. For rocks, trees and dressing. |
| profile | string | no | x0,z0,x1,z1[,steps] — the ground along a straight line, for a road, a wall or a bridge |
| span | integer | no | block size in 64m chunks, 1 to 4. Bigger blocks have more room and more sites. |
| erosion | number | no | 0 to 1. Weathers the landforms: valleys smooth out, crests stay sharp. Changes where the level sites are, so ask with the same value you intend to build with. |
| flatten | number | no | 0 to 1. Clears a level area in the MIDDLE of the block for a settlement, leaving the landscape around it. Raise it when the natural sites are too small for what you are placing. |
What this connection can currently do: whether a key is attached, which assets and kits it owns, and therefore which downloads will work. Call it before promising the user a paid file, and when a download 404s, rather than guessing whether the problem is the key or the asset.
No parameter schema on file.
Buy a Polyfork plan: Pro (monthly or yearly) or a one-payment lifetime seat. This tool NEVER charges anything itself. It returns a Stripe Checkout link and the exact amount; the payment happens on that page (cards and Link), and only with the user's approval of the amount. Call it with no arguments to see what is on sale and at what price. Use it when a download needs a plan the user does not have
| Parameter | Type | Required | Notes |
|---|---|---|---|
| plan | string | no | what to buy; omit to list what is on sale, with prices |
| confirm | string | no | the checkout_id from an earlier call, WHOLE (starts with cs_, and may carry a second part after a dot): reports whether it has been paid and activates the plan if so |
How to use this server: what the metadata means, the rules that are easy to get wrong (real-world metres, one material, never rescale to fake a fit), and worked recipes for building a scene. Call it when a tool did not behave as you expected, or before a multi-step build, instead of guessing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | omit for the overview |
Report a gap. Four kinds, and the last three are about THIS SERVER rather than the catalogue: kind=asset, we do not model what the user asked for (offer this whenever a search is empty or thin); kind=capability, you needed the server to do something it cannot; kind=output, a tool answered but not with what you needed; kind=docs, a tool description did not tell you how to use it. Do not stay quiet
| Parameter | Type | Required | Notes |
|---|---|---|---|
| need | string | yes | what was missing, in plain words (max 500 characters; put the detail in context, which takes 1000) |
| kind | string | no | defaults to asset |
| tool | string | no | which tool this is about, for capability/output/docs |
| context | string | no | what the user was building, or what you expected instead |
| string | no | only if the user offers it |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- 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 Polyfork low-poly 3D assets or to call it, at any volume.
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.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
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.
Any signed-in account that does not publish Polyfork low-poly 3D assets can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
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.