Connect any MCP client to three.ws in one command. three-ws signs you in, writes the hosted three.ws MCP servers into every client it finds (Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, IBM Bob, Codex, Gemini CLI, Hermes), prints the connector fields for Grok Bot, and verifies each one with a live tools/list.
npx @three-ws/cli setupRequires Node.js 20.12 or newer.
The three.ws MCP servers give your assistant 3D generation (text to 3D, image to 3D, rigged avatars), your agents and their wallets, x402 paid services, and Solana token data. The live list is at three.ws/.well-known/mcp.json and every tool is in the catalog.
Using one client that supports remote connectors? three.ws/connect adds three.ws to Claude, Cursor or VS Code in one click, with no terminal.
npx @three-ws/cli --claude # also --cursor --codex --vscode --windsurf --gemini --bob --hermesSigns in, writes the servers, verifies them, and installs the three.ws skill for Claude Code, with no prompts. The config gets a three-ws proxy launcher, never a token: credentials stay in ~/.config/three-ws/credentials.json (mode 600). Running it again changes nothing. Then: claude "launch my agent".
Hosted installers: curl -fsSL https://three.ws/cli/install | sh and curl -fsSL https://three.ws/cli/claude | sh. Every script ships with a .sha256 checksum and an ed25519 .sig; download, read and verify before running: three.ws/docs/cli#verify-before-you-run.
npx @three-ws/cli doctor # bad config, expired sign-in, unreachable server, with the fix for each
npx @three-ws/cli agent status # agents, wallets and balances
npx @three-ws/cli team # your teams; `team status <id>` for onetests/container/run.sh packs this package and, for each client, starts a fresh node:22 container, runs the hosted installer against a local stand-in platform, and asserts the config is written without a key, a second run changes nothing, doctor passes and the credential file is mode 600. Needs Docker.
bash packages/three-ws-cli/tests/container/run.shnpx @three-ws/cli setup --clients cursor,vscode --yes # specific clients, no prompts
npx @three-ws/cli setup --project # project-scoped config in this directory
npx @three-ws/cli login --device # sign in over SSH
npx @three-ws/cli link BCDF-GHJK # link this terminal with a code from /dashboard/account
npx @three-ws/cli mcp list --available # every server and its name
npx @three-ws/cli tools --server three-ws-main --enable financial
npx @three-ws/cli status
npx @three-ws/cli create "Nova" --description "A deep-space guide." # an agent with its own Solana wallet
npx @three-ws/cli launch --agent <id> --name Nova --symbol NOVA # prefilled, you sign on three.ws/launchGrok Bot's MCP configuration lives in xAI's cloud, so there is no file to write. setup handles the rest: it picks the Grok connector (https://three.ws/api/mcp-grok), copies the URL to your clipboard when a clipboard tool exists, prints the exact fields for Grok Bot's custom MCP connector, and runs a real tools/list against the public URL to prove it answers from outside.
npx @three-ws/cli setup --client grok-bot # free 3D studio, no account, no key
npx @three-ws/cli setup --client grok-bot --connector-key # also mint a key so Grok Bot can use your agents
npx @three-ws/cli setup --clients cursor,grok-bot --yes # local clients and Grok Bot in one runGrok Bot (cloud connector, nothing to write locally)
Name three-ws
Transport Streamable HTTP
Server URL https://three.ws/api/mcp-grok
Authentication None
--connector-key signs you in, mints one key with the connector preset (read, generate and edit agents, never spend), stores it in the credential file, and reuses it on later runs. Paste it as a Bot secret. --no-copy skips the clipboard. A localhost origin is flagged, because Grok Bot connects from xAI's cloud. Full walkthrough: three.ws/docs/grok.
Sign-in is a browser OAuth flow by default. --device approves a code from any browser, and --key sk_live_... (or THREE_WS_API_KEY) uses an API key from Dashboard → API. Tools that move funds are off unless you sign in with --financial and enable them.
The package exports its building blocks (server directory, client detection, config writers, OAuth helpers) for tools that want to reuse them. List every hosted server and the name clients store it under:
import { loadDirectory, hostedServers } from 'three-ws';
const origin = 'https://three.ws';
const directory = await loadDirectory(origin);
for (const server of hostedServers(directory, origin)) console.log(server.slug, server.url);
// three-ws-main https://three.ws/api/mcp
// three-ws-studio https://three.ws/api/mcp-studio
// ...Full reference, client config paths and troubleshooting: three.ws/docs/cli.
Apache-2.0
If three-ws-cli saves you time, star it on GitHub. Stars are how other developers and AI agents find the repositories worth trusting, and they cost you one click.
Know someone who would use it? Post on X · Share on Bluesky · Share on LinkedIn · Submit to Hacker News · Share on Reddit
Coding agents and LLM tooling can read this repo directly: AGENTS.md, llms.txt, llms-full.txt. Point an agent at https://github.com/nirholas/three-ws-cli and it has the context it needs.
- All repositories by nirholas: the full catalog, grouped by topic
- three.ws: the platform for 3D AI agents with Solana wallets, a skill marketplace and x402 payments
- Questions or ideas: open an issue or start a discussion
three.ws is a platform for 3D AI agents with Solana wallets: avatars, a skill marketplace, x402 payments and more than seventy MCP servers. @three-ws/cli is one package from it.
- Documentation site: https://nirholas.github.io/three-ws-cli/
- npm: https://www.npmjs.com/package/@three-ws/cli
- Canonical source: https://github.com/nirholas/three.ws (this repository is a generated mirror of
packages/three-ws-cli) - Agent-readable summary: llms.txt and AGENTS.md
- Issues and ideas: https://github.com/nirholas/three-ws-cli/issues