mcpField
T
three.ws Loom

three.ws Loom

Local
three.wsMedia & Design255Updated today

About three.ws Loom

Loom is a three.ws MCP server for the community 3D creation gallery. It lets agents browse public GLB creations, fetch one with its viewer link, and submit a new model. It suits users who want to preview or share 3D models from within an agent.

Key features

  1. 01Browse public creations, newest first
  2. 02Page through the gallery with a cursor
  3. 03Fetch creation details and a viewer URL
  4. 04Provide an iframe snippet for embedding
  5. 05Submit a GLB model to the public gallery

Use cases

  1. 01Browsing community 3D model work from an agent
  2. 02Embedding a creation in a web page for preview
  3. 03Publishing a locally generated GLB to the public gallery

MCP support

The server exposes get_loom_feed, get_creation and submit_creation as MCP tools, with submit_creation as the only write operation. Reads need no key or account, and submissions are limited by a server-side IP rate limit.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"nirholas-loom": {
"command": "npx",
"args": [
"-y",
"@three-ws/loom-mcp"
],
"env": {
"THREE_WS_BASE": "<THREE_WS_BASE>",
"THREE_WS_TIMEOUT_MS": "<THREE_WS_TIMEOUT_MS>"
}
}
}
}
Run commandnpx -y @three-ws/loom-mcp
Environment variables to set
THREE_WS_BASEBase URL of the three.ws API that serves the Loom gallery (/api/loom). Override only when self-hosting or targeting a preview deployment.
THREE_WS_TIMEOUT_MSPer-request timeout in milliseconds for the live Loom reads and submissions.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@three-ws/loom-mcp0.1.3

Tools

3

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
limitintegerNoHow many creations to return (1–120, default 60).
beforeintegerNoPagination cursor (ms epoch): return only creations older than this. Pass the prior page's nextBefore.

Details

From the project README

three.ws

@three-ws/loom-mcp

Loom — the three.ws community 3D-creation gallery, from any AI agent. Browse the public feed of community-forged GLB creations, fetch one with its viewer URL, and submit your own.

npm license node MCP Registry three.ws


A Model Context Protocol server that exposes Loom, the three.ws community 3D-creation gallery, over stdio. Browse what others have forged, pull any creation with a ready-to-embed viewer URL, and contribute your own GLB to the public feed.

Loom closes the loop with the rest of the three.ws 3D suite: forge a model with @three-ws/avatar-agent or compose a world with @three-ws/scene-mcp, then publish it here for the whole platform to see. Every read is live and public; submitting needs no key or account — it is gated server-side only by an IP rate limit.

Install

npm install @three-ws/loom-mcp

Or run with npx (no install):

npx @three-ws/loom-mcp

Quick start

Claude Code, one line:

claude mcp add loom -- npx -y @three-ws/loom-mcp

Claude Desktop / Cursor (claude_desktop_config.json or mcp.json):

{
	"mcpServers": {
		"loom": {
			"command": "npx",
			"args": ["-y", "@three-ws/loom-mcp"]
		}
	}
}

Inspect the surface with the MCP Inspector:

npx -y @modelcontextprotocol/inspector npx @three-ws/loom-mcp

Tools

ToolTypeWhat it does
get_loom_feedread-onlyBrowse the public gallery of community-forged 3D creations, newest-first, paginated via a nextBefore cursor.
get_creationread-onlyFetch one creation by id, with its full metadata and an inline-previewable viewer URL + iframe.
submit_creationwriteContribute a forged GLB to the public gallery. No key required; rate-limited (~20/hour per IP).

Each read returns the creation's glbUrl plus a viewer_url (the /forge/embed orbit + AR viewer), an og_image_url (social card), and a paste-ready iframe_snippet, so any MCP client can preview the model inline.

Input parameters

get_loom_feed — limit (1–120, default 60), before (ms-epoch cursor; pass the prior page's nextBefore to page backwards).

get_creation — id (required — the creation UUID).

submit_creation — prompt (required, ≤1000 chars), glbUrl (required — see allowed hosts below), author (optional attribution, ≤40 chars, defaults to anon), previewImageUrl, tier, backend (all optional).

Submitting a creation

submit_creation posts to the public, world-readable gallery — only submit models you intend to share. There is no account, key, or signer: the endpoint is open and gated server-side by an IP rate limit (~20 submissions/hour) plus strict input sanitization. author is free-text attribution, not an authenticated identity.

The glbUrl must be an https URL hosted on one of these domains (enforced both client-side here and server-side):

three.ws · r2.dev · cloudflarestorage.com · replicate.delivery · githubusercontent.com

Re-submitting the exact same glbUrl returns the existing creation instead of duplicating it. The dedupe is best-effort by design: it scans only the newest few entries, which is where an accidental re-POST lands. Re-submitting a GLB that has since scrolled down the feed creates a second record.

get_creation answers an id that no longer exists with a typed not_found error rather than an empty creation, so a stale id in a saved reference is unambiguous.

Example

// submit_creation
> {
    "prompt": "a cowboy hat, low-poly",
    "glbUrl": "https://three.ws/accessories/hat-cowboy.glb",
    "author": "nova",
    "backend": "hunyuan"
  }
{
  "ok": true,
  "creation": {
    "id": "f295398e-2d25-410d-a82f-c8725295a1b3",
    "prompt": "a cowboy hat, low-poly",
    "glbUrl": "https://three.ws/accessories/hat-cowboy.glb",
    "author": "nova",
    "createdAt": 1750000000000,
    "viewer_url": "https://three.ws/forge/embed?src=https%3A%2F%2Fthree.ws%2Faccessories%2Fhat-cowboy.glb&title=a+cowboy+hat%2C+low-poly",
    "og_image_url": "https://three.ws/api/avatar-og?src=https%3A%2F%2Fthree.ws%2Faccessories%2Fhat-cowboy.glb",
    "iframe_snippet": "<iframe src=\"https://three.ws/forge/embed?src=…\" width=\"640\" height=\"360\" …></iframe>"
  }
}
// get_loom_feed
> { "limit": 2 }
{ "ok": true, "count": 2, "nextBefore": 1749999000000, "has_more": true,
  "creations": [ { "id": "…", "prompt": "…", "glbUrl": "…", "viewer_url": "…", "iframe_snippet": "…" } ] }

Drop a creation's iframe_snippet onto any web page, or open its viewer_url to orbit the model (with AR on supported devices).

Examples

Runnable examples live in examples/:

node examples/list-tools.mjs     # every tool with its full input schema
node examples/browse-loom.mjs    # a page of the gallery + one creation's embed, live

Both spawn this server over stdio and read the live public gallery. They are deliberately read-only: submit_creation posts to a world-readable feed, so no example writes on your behalf. See examples/README.md for expected output.

Requirements

  • Node.js >= 20.
  • Network access to https://three.ws (or your own THREE_WS_BASE).
Environment variables
VariableRequiredDefault
THREE_WS_BASEnohttps://three.ws
THREE_WS_TIMEOUT_MSno20000

No API key, signer, or account is needed for any tool.

Links


Part of the three.ws SDK suite — 3D AI agents, on-chain identity, and agent payments.
Website · Changelog · GitHub

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.