three.ws Listed on Anthropic's Official MCP Registry
three.ws is now listed on Anthropic's official Model Context Protocol Registry — the canonical directory for AI-to-tool integrations used by Claude, ChatGPT, Cursor, and every MCP-compatible client.
- Remote MCP URL:
https://three.ws/api/mcp - Registry listing: registry.modelcontextprotocol.io/?q=three.ws
- Project site: three.ws
What the MCP listing unlocks
The Model Context Protocol Registry is Anthropic's official index of remote tool servers that AI assistants can call. Being listed here means Claude — and any other MCP-compatible agent — can natively discover and invoke the three.ws toolkit without any custom configuration from the developer.
What that means in practice: drop https://three.ws/api/mcp as a remote server into Claude Desktop, Cursor, or any MCP client, sign in with your three.ws account when the client asks, and you have the full three.ws 3D agent toolkit. Create a 3D avatar, give it an on-chain identity, wire it to an LLM brain, and embed it anywhere, all driven by natural language through the same tools Claude already knows how to call.
The sign-in comes first because most of those tools act on your own avatars, agents, and wallet, so the client is asked to authorize as soon as it connects. To try three.ws with no account at all, add https://three.ws/api/mcp-studio instead. It never asks you to sign in, and it serves free text-to-3D and image-to-3D generation, rigged avatars, and a search of the ready-made asset catalog (CC0 props, rigged characters, and motion clips) with paste-ready code for each. See the studio server docs.
What the three.ws MCP server exposes
- Agent creation. Spin up a new 3D agent with a persona, voice, and LLM configuration.
- Avatar management. Select, customize, and animate any avatar in the three.ws gallery.
- On-chain minting. Mint the agent as a Solana NFT so it has a permanent, transferable identity.
- Emotion and animation control. Trigger gestures and emotional states from tool calls — wave, think, react to data.
- Embed generation. Get the
<agent-3d>snippet ready to drop into any webpage. - x402 payment setup. Configure pay-per-call pricing for the agent's skills, settled in USDC on-chain.
Why MCP matters for agent interoperability
Model Context Protocol is the standard that lets AI assistants reach outside their context window and call real tools with real side effects. The Anthropic registry is where that ecosystem self-organizes: builders publish servers, clients discover them, and agents wire up capabilities without bespoke integrations.
three.ws joining the registry puts 3D embodiment — a 3D body, on-chain identity, and payment rails — in the same tool-call layer as search, code execution, and database access. An agent can now reason about its own appearance, mint itself on-chain, and configure what it charges for its skills, all through the same MCP interface it already uses to do everything else.
Links
- Remote MCP URL:
https://three.ws/api/mcp - Registry listing: registry.modelcontextprotocol.io/?q=three.ws
- MCP documentation: anthropic.com/news/model-context-protocol
- Open source: github.com/nirholas/three.ws
- Project site: three.ws