Game Development

polyfork.dev

Searches and retrieves low-poly 3D assets, with options to find matching assets, generate variants, and preview scenes.

1 endpoint11 known toolsFirst detected August 15, 2026Last detected August 15, 2026

ENDPOINT 1

https://polyfork.dev/mcp

No auth detected

MCP server metadata

Name: polyfork
Version: 1.0.0

Capabilities

tools

Server instructions

Read https://polyfork.dev/prompt.txt at the start of a session: it is this catalogue as working instructions (picking assets that go together, assembling a kit on its grid, animating what is riggable) and it is kept current, unlike anything pasted into a project. Fetch it first if you are assembling a scene rather than looking up one asset. Polyfork is a library of low-poly 3D assets for three.js, glTF and game engines, described well enough to place without guessing. Sizes are real metres and the origin sits on the ground, so never rescale an asset to fake a fit: pick a right-sized one instead. A kit publishes the contract its parts agree on (the grid they snap to and the knobs whose value must match across a scene), so read get_kit before placing anything from one. Assets carry has_rig (animatable parts), remixable (createAsset knobs) and has_night (lights up after dark). Prefer preview_scene over pasting three.js the user cannot run, and find_matching over guessing what goes together from palettes. When the catalogue has nothing suitable, say so and offer report_need: an honest no is worth more than a vaguely similar rock.

Known tools 11

search_assets

Search the Polyfork catalogue of low-poly 3D assets for three.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

get_variant

Turn a plain-words request ("oak cask", "taller", "five sails") into a ready call.

Inferred read-only

preview_scene

Compose assets into a scene and return a URL the user can OPEN and orbit.

Inferred read-only

list_kits

Kits are coherent sets built to one palette and one grid.

Inferred read-only

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.

Inferred read-only

get_terrain

AT WHAT HEIGHT DO I PLACE THIS, and where can I build.

Inferred read-only

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.

Inferred read-only

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.

Inferred read-only

report_need

Report a gap.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.polyfork]
url = "https://polyfork.dev/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "polyfork": {
      "type": "http",
      "url": "https://polyfork.dev/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: polyfork
Remote MCP URL: https://polyfork.dev/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "polyfork": {
      "url": "https://polyfork.dev/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "polyfork": {
      "type": "http",
      "url": "https://polyfork.dev/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "polyfork",
  "transport": "streamable-http",
  "url": "https://polyfork.dev/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Trust Data Available

BuiltWith Trust API v2 evidence for polyfork.dev was fetched 2026-08-25T17:33:38.733Z.

Trust status Neutral

polyfork.dev is assessed as Neutral: No suspicious signals found, but no strong positive signal either

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.