Polyfork low-poly 3D assets
by polyfork.dev in Search & web
Low-poly 3D models and kits for three.js and game engines: search, match, remix, preview.
https://polyfork.dev/mcp- Tools
- 12
- open to any client
- Uptime
- 100%
- last 30 days
- Response time
- 252 ms
- 439 ms slowest 5%
- Last check
- Passed
- 11 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to connect
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"polyfork-low-poly-3d-assets": {
"type": "http",
"url": "https://polyfork.dev/mcp"
}
}
}12 tools
- search_assets
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`…
- get_asset
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…
- find_matching
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…
- get_variant
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…
- preview_scene
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…
- list_kits
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…
- get_kit
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…
- get_terrain
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…
- who_am_i
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.
- buy_plan
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…
- get_help
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…
- report_need
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…
Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 11 h ago | Passed | 200 | 193 ms |
| 22 h ago | Passed | 200 | 211 ms |
| 33 h ago | Passed | 200 | 204 ms |
| 44 h ago | Passed | 200 | 179 ms |
| 2 days ago | Passed | 200 | 191 ms |
Show 10 older checks
| 3 days ago | Passed | 200 | 285 ms |
| 3 days ago | Passed | 200 | 338 ms |
| 4 days ago | Passed | 200 | 196 ms |
| 4 days ago | Passed | 200 | 169 ms |
| 4 days ago | Passed | 200 | 139 ms |
| 5 days ago | Passed | 200 | 170 ms |
| 5 days ago | Passed | 200 | 252 ms |
| 6 days ago | Passed | 200 | 370 ms |
| 6 days ago | Passed | 200 | 354 ms |
| 6 days ago | Passed | 200 | 353 ms |