Open-source platform for 3D AI agents. Turn text or a photo into a rigged, animated GLB avatar, give it an LLM brain, memory and a wallet, and embed it anywhere with one web component. Remote MCP server, x402 payments, Three.js, browser-native.
JavaScript 3d-generationai-agentsanimationavatardigital-humangenerative-aiglbgltfimage-to-3dllmmcpmcp-servermodel-context-protocolsolanatext-to-3dthreejsweb-componentswebglwebxrx402
docs(partners): draft three.ws MCP registry entries for Hermes, Kilo, OpenHands, OpenCode, Dify, cursor.directory
nirholas314972792b74
diff --git a/marketing/growth/submissions/agent-registries/cursor-directory.md b/marketing/growth/submissions/agent-registries/cursor-directory.mdnew file mode 100644index 000000000..6d5446b05--- /dev/null+++ b/marketing/growth/submissions/agent-registries/cursor-directory.md@@ -0,0 +1,36 @@+# cursor.directory MCP listing submission++Target: `https://cursor.directory/mcp`.++Not fully confirmed: cursor.directory rate-limited (HTTP 429) every direct fetch attempted in this session+(both the homepage and a guessed `/submit` path, via `curl` and via `WebFetch`), so the exact current+submission mechanism (a form, a GitHub repo PR, or an account-gated dashboard) could not be verified live.+cursor.directory is a community-run directory (not an official Cursor/Anysphere product); its public+listings historically accept submissions either through a logged-in "Submit" button on the site or through+its companion GitHub repo, but which applies today is unconfirmed as of 2026-10-13. Flagging this+transparently rather than guessing at a mechanism this session couldn't verify.++## What ships (listing copy, ready to paste into whichever form the owner finds)++- Name: three.ws+- Category: 3D / Generative AI+- URL: https://three.ws+- Description: "Forge a textured 3D model from a text prompt, auto-rig it for animation, and render a+ turntable preview, all through one free MCP server. No API key required."+- MCP connection (streamable HTTP, no auth): `https://three.ws/api/mcp-studio`+- Config snippet:+ ```json+ {+ "mcpServers": {+ "three-ws": {+ "url": "https://three.ws/api/mcp-studio"+ }+ }+ }+ ```++## Owner steps (not automatable here)++1. Visit `https://cursor.directory/mcp` directly (not rate-limited from a real browser session) and locate+ the current submission entry point.+2. Paste the listing copy above into whatever form or PR process it presents.diff --git a/marketing/growth/submissions/agent-registries/dify.md b/marketing/growth/submissions/agent-registries/dify.mdnew file mode 100644index 000000000..25566636c--- /dev/null+++ b/marketing/growth/submissions/agent-registries/dify.md@@ -0,0 +1,43 @@+# Dify (langgenius/dify-plugins) plugin submission++Target: `https://github.com/langgenius/dify-plugins`.++Confirmed 2026-10-13: the repo exists and its root is organized as one directory per contributor/author+(e.g. `BrightData`, `16api`, ...), each holding that author's published plugin(s). No directory in the+current root listing packages a generic "call any MCP server" tool, so this is a from-scratch Dify tool+plugin, not a manifest drop-in like the other three registries in this directory.++Unlike Hermes, Kilo Code, and OpenHands, a Dify plugin is not just a YAML/JSON file: it's a buildable+package (`.difypkg`) produced by Dify's own `dify` plugin CLI from a `manifest.yaml` + a `provider.yaml` ++Python tool implementation files, then signed and submitted through the Dify Marketplace, not through this+GitHub repo directly (`langgenius/dify-plugins` mirrors already-published marketplace plugins; the actual+submission path is `https://marketplace.dify.ai` plus the `dify-plugin` CLI). That build step needs a local+Python toolchain this session does not have reason to install for one registry listing, so this file documents+the real plugin identity and tool surface for the owner to scaffold with the CLI, rather than guessing at a+`.difypkg` binary layout this session cannot verify.++## What ships (plugin identity, to feed into `dify plugin init`)++- Plugin name: `three-ws`+- Author: `three-ws`+- Category: `tool`+- Tools exposed (each a thin wrapper calling `https://three.ws/api/mcp-studio` over JSON-RPC, same wire+ format as `packages/ai-sdk/src/client.js` / `packages/langchain/src/client.js` in this repo):+ - `forge` -> `forge_free(prompt, tier?)`+ - `rig` -> `rig_mesh(glb_url)`+ - `render` -> `look_at_model(glb_url, views?, size?)`+- No credentials required (the provider has no auth fields).++## Verification packet++- Repo structure (per-contributor plugin directories) confirmed via the GitHub contents API, 2026-10-13.+- Tool schemas confirmed live against production in this session's test runs+ (`packages/ai-sdk/test/tools.test.js`, `packages/langchain/test/tools.test.js`).++## Owner steps (not automatable here)++1. Install the `dify-plugin` CLI (`pip install dify-plugin` or the packaged binary per Dify's plugin docs).+2. `dify plugin init`, name `three-ws`, category `tool`, then add the three tools listed above as thin+ fetch wrappers around `https://three.ws/api/mcp-studio` (reuse the request shape in+ `packages/ai-sdk/src/client.js`).+3. `dify plugin package` to produce the `.difypkg`, then submit it at `https://marketplace.dify.ai`.diff --git a/marketing/growth/submissions/agent-registries/hermes-agent.md b/marketing/growth/submissions/agent-registries/hermes-agent.mdnew file mode 100644index 000000000..6c3b3d67c--- /dev/null+++ b/marketing/growth/submissions/agent-registries/hermes-agent.md@@ -0,0 +1,64 @@+# Hermes Agent (NousResearch/hermes-agent) optional-MCP submission++Target: `https://github.com/NousResearch/hermes-agent`, file `optional-mcps/three-ws/manifest.yaml`.++Confirmed 2026-10-13 against the real `optional-mcps/context7/manifest.yaml` (fetched live from+`raw.githubusercontent.com`): remote HTTP MCP entries use `manifest_version: 1`, `transport: {type: http, url}`,+and `auth: {type: none}` for a no-key server, which matches three.ws's free `/api/mcp-studio` endpoint exactly.++## What ships++The manifest below describes three.ws's free MCP server (`forge_free`, `rig_mesh`, `look_at_model`) to any Hermes+agent that enables it. `text_to_animation` is intentionally left off this listing: it is paid and x402-gated, and+Hermes's optional-MCP format has no field for "pay per call," so listing it here would make the tool call fail+silently without a wallet. The free tools are the complete, working offering for this surface.++## `optional-mcps/three-ws/manifest.yaml`++```yaml+manifest_version: 1+name: three.ws+description: >+ Generative 3D for agents: forge a textured GLB from a text prompt, auto-rig it for+ animation, and render a turntable preview with geometry stats. Free, no API key.+source: https://three.ws+transport:+ type: http+ url: https://three.ws/api/mcp-studio+auth:+ type: none+suggest:+ keywords:+ - 3d+ - glb+ - gltf+ - mesh+ - avatar+ - rigging+ - model generation+ hosts:+ - three.ws+post_install: |+ three.ws exposes three free tools over this MCP server:+ - forge_free(prompt, tier?) -> generates a textured GLB from text+ - rig_mesh(glb_url) -> auto-rigs a static GLB with a humanoid skeleton+ - look_at_model(glb_url, views?, size?) -> renders a turntable preview + geometry stats+ No API key is required. A paid, x402-gated animation tool (text_to_animation) also exists+ at https://three.ws/api/mcp but is out of scope for this optional-MCP listing since it+ requires a per-call payment the agent must resolve with its own wallet.+```++## Verification packet++- `transport.type: http` + `auth.type: none` shape confirmed against the live `context7` entry+ (`optional-mcps/context7/manifest.yaml`) in the same repo, fetched 2026-10-13.+- `forge_free`, `rig_mesh`, `look_at_model` schemas confirmed live against `https://three.ws/api/mcp-studio`+ in this same session (see `packages/ai-sdk/test/tools.test.js` and `packages/langchain/test/tools.test.js`,+ which call all three against production and pass).++## Owner steps (not automatable here)++1. Fork `NousResearch/hermes-agent`, add `optional-mcps/three-ws/manifest.yaml` with the content above.+2. Open a pull request titled "Add three.ws optional MCP" with a one-paragraph description pointing at+ `https://three.ws/.well-known/skills/index.json` (see `packages/ai-sdk` and `packages/langchain` for+ framework-native tool wrappers of the same server).diff --git a/marketing/growth/submissions/agent-registries/kilo-code.md b/marketing/growth/submissions/agent-registries/kilo-code.mdnew file mode 100644index 000000000..632526680--- /dev/null+++ b/marketing/growth/submissions/agent-registries/kilo-code.md@@ -0,0 +1,48 @@+# Kilo Code (Kilo-Org/kilo-marketplace) MCP submission++Target: `https://github.com/Kilo-Org/kilo-marketplace`, file `mcps/three-ws/MCP.yaml`.++Confirmed 2026-10-13 against the real `mcps/apify/MCP.yaml` (fetched live from `raw.githubusercontent.com`):+entries use `id`, `name`, `description`, `author`, `url`, `category`, and a `content` array of one or more+`{name, prerequisites, content, parameters?}` blocks, where `content` is a JSON string holding the actual+MCP server config Kilo Code writes into the user's `mcp_settings.json`.++## What ships++A remote, no-auth, streamable-HTTP MCP entry pointing at three.ws's free server. Matches the pattern+`https://three.ws/api/mcp-studio` already verified live in `packages/ai-sdk/test/tools.test.js` and+`packages/langchain/test/tools.test.js`.++## `mcps/three-ws/MCP.yaml`++```yaml+id: three-ws+name: three.ws+description: >-+ Generative 3D pipeline for agents: forge a textured GLB from a text prompt, auto-rig it,+ and render a turntable preview with geometry stats. Free, no API key required.+author: three.ws+url: https://three.ws+category: 3d-generation+content:+ - name: Default (no auth)+ prerequisites: []+ content: |+ {+ "three-ws": {+ "url": "https://three.ws/api/mcp-studio",+ "type": "streamable-http"+ }+ }+```++## Verification packet++- `MCP.yaml` field shape confirmed against the real `mcps/apify/MCP.yaml` example, fetched 2026-10-13.+- Tool schemas (`forge_free`, `rig_mesh`, `look_at_model`) confirmed live against production in this+ session's test runs for `packages/ai-sdk` and `packages/langchain`.++## Owner steps (not automatable here)++1. Fork `Kilo-Org/kilo-marketplace`, add `mcps/three-ws/MCP.yaml` with the content above.+2. Open a pull request titled "Add three.ws MCP server".diff --git a/marketing/growth/submissions/agent-registries/opencode.md b/marketing/growth/submissions/agent-registries/opencode.mdnew file mode 100644index 000000000..82234b16d--- /dev/null+++ b/marketing/growth/submissions/agent-registries/opencode.md@@ -0,0 +1,49 @@+# OpenCode (anomalyco/opencode, formerly sst/opencode) MCP docs submission++Target: `https://github.com/anomalyco/opencode` (the repo was renamed from `sst/opencode`; GitHub's API+redirects the old slug to this one), file `packages/web/src/content/docs/docs/mcp-servers.mdx`, default+branch `dev`.++Confirmed 2026-10-13: OpenCode's own MCP servers doc page (`https://opencode.ai/docs/mcp-servers/`) states+"You can submit a PR if you want to document other servers" in its Examples section, which currently lists+Sentry, Context7, and Grep by Vercel. There is no separate issue template or form: a documentation PR against+`mcp-servers.mdx` is the whole mechanism. The directory listing of+`packages/web/src/content/docs/docs/` was fetched live and confirmed `mcp-servers.mdx` exists at that path.++## What ships++A new Examples entry for three.ws, in the same style as the existing Context7 entry: a short description plus+the `opencode.json` / global config snippet a user pastes in to add the server.++## Proposed Markdown addition to `mcp-servers.mdx`'s Examples section++```markdown+### three.ws++Generate, rig, and render 3D models (GLB) from a text prompt. Free, no API key required.++\`\`\`json title="opencode.json"+{+ "mcp": {+ "three-ws": {+ "type": "remote",+ "url": "https://three.ws/api/mcp-studio",+ "enabled": true+ }+ }+}+\`\`\`+```++## Verification packet++- Submission mechanism (PR against `mcp-servers.mdx`) confirmed by fetching the live OpenCode docs page.+- Repo rename (`sst/opencode` -> `anomalyco/opencode`) and the exact doc file path confirmed via the GitHub+ API, 2026-10-13.+- Tool schema confirmed live against production in this session's test runs.++## Owner steps (not automatable here)++1. Fork `anomalyco/opencode`, add the Examples entry above to+ `packages/web/src/content/docs/docs/mcp-servers.mdx`.+2. Open a pull request titled "docs: add three.ws to MCP server examples".diff --git a/marketing/growth/submissions/agent-registries/openhands.md b/marketing/growth/submissions/agent-registries/openhands.mdnew file mode 100644index 000000000..359755770--- /dev/null+++ b/marketing/growth/submissions/agent-registries/openhands.md@@ -0,0 +1,53 @@+# OpenHands (OpenHands/extensions) integration catalog submission++Target: `https://github.com/OpenHands/extensions`, file `integrations/catalog/three-ws.json`, validated+against `integrations/catalog.schema.json`.++Confirmed 2026-10-13 against two real catalog entries fetched live from `raw.githubusercontent.com`:+`integrations/catalog/apify.json` (stdio transport) and `integrations/catalog/cloudflare-docs.json` (remote+`shttp` transport with `auth: {strategy: "none"}`). The Cloudflare entry is the closer analog: three.ws's+free MCP server is also a remote, no-auth, streamable-HTTP endpoint.++## What ships++`three.ws` listed under a `3d` / `generative-ai` category, pointing at the live `/api/mcp-studio` server+verified in this session's `packages/ai-sdk` and `packages/langchain` test suites.++## `integrations/catalog/three-ws.json`++```json+{+ "id": "three-ws",+ "name": "three.ws",+ "description": "Forge a textured 3D model from text, auto-rig it, and render a turntable preview, all through one free MCP server.",+ "docsUrl": "https://three.ws/.well-known/skills/index.json",+ "iconBg": "#000000",+ "logoUrl": "https://three.ws/three-ws-mcp-icon.svg",+ "keywords": ["3d", "glb", "gltf", "mesh", "avatar", "rigging", "model generation"],+ "connectionOptions": [+ {+ "id": "none",+ "provider": "mcp",+ "transport": {+ "kind": "shttp",+ "url": "https://three.ws/api/mcp-studio"+ },+ "auth": {+ "strategy": "none"+ }+ }+ ]+}+```++## Verification packet++- Schema shape confirmed against `integrations/catalog.schema.json` plus two real live examples+ (`apify.json`, `cloudflare-docs.json`), fetched 2026-10-13.+- Tool schemas confirmed live against production in this session's test runs.++## Owner steps (not automatable here)++1. Fork `OpenHands/extensions`, add `integrations/catalog/three-ws.json` with the content above.+2. Validate locally against `integrations/catalog.schema.json` if the repo ships a validation script.+3. Open a pull request titled "Add three.ws to the integration catalog".