Connector
One URL. Your AI gets three.ws.
Add three.ws to Claude, ChatGPT, Grok Bot, Cursor, VS Code or Claude Code and your assistant can generate 3D models and avatars, run your agents, read their wallets and pay for services over x402. Sign in once in your browser: there is no API key to copy. Every tool is listed in the MCP tool catalog.
Pick a server
Start with three.ws. Add others later; each is its own connector.
https://three.ws/api/mcp
Connector URL for cloud agents
Grok Bot and other hosted agents reach three.ws from one shared IP, so every user of that agent shares one free quota. A free install token gives your connector a quota of its own. Making a model still needs a free three.ws account.
Add it to your client
Links open your client with the server filled in. You still review it and confirm.
Works on claude.ai and the Claude desktop app, on every plan. Free accounts can add one custom connector. On Team and Enterprise, only owners can add one.
- Click the button above, check the name and URL, then click Add. Adding it by hand instead: Customize → Connectors (Settings → Connectors on some accounts), Add custom connector, paste the URL.
- Click Connect and sign in to three.ws with Google, your wallet, or your email. The permissions screen groups what Claude asked for into Read, Manage, Trade, Spend and Launch: untick any group you do not want it to have, then approve.
- In a chat, open the + menu, then Connectors, and switch three.ws on for that conversation.
Steps follow Claude's own guide. Its menus move: if these drift, tell us.
ChatGPT adds custom MCP servers through Developer mode, on the plans where OpenAI offers it. There is no pre-filled link, so copy the URL first.
- In Settings → Apps & Connectors → Advanced settings, turn on Developer mode.
- Back in Apps & Connectors, click Create. Name it
three.ws, paste the URL, choose OAuth, and create it. - Sign in to three.ws when ChatGPT asks, with Google, your wallet, or your email, and approve the permissions. If Claude is already connected it stays connected: each client has its own grant.
- In a new chat, open the + menu, choose Developer mode, and tick three.ws.
Steps follow OpenAI's developer mode guide. Its labels change often: if these drift, tell us.
One command adds the server. The first time a tool needs your account, Claude Code opens three.ws sign-in in your browser.
claude mcp add --transport http three-ws-main https://three.ws/api/mcp
- Run the command. Add
--scope projectto share it with your team through.mcp.json. - In Claude Code, type
/mcp, pick the server you just added and choose Authenticate.
Or let one command do all of it: it signs you in, writes the server and the three.ws skill, and keeps every key out of your config file. Read the script and check its signature first.
npx three-ws --claude
The button opens Cursor's install prompt with the server filled in. Cursor then runs the three.ws sign-in.
{
"mcpServers": {
"three-ws-main": { "url": "https://three.ws/api/mcp" }
}
}
Link format from Cursor's install-link docs.
For GitHub Copilot agent mode in VS Code. The button opens VS Code's install prompt; the server signs you in on first use.
{
"servers": {
"three-ws-main": { "type": "http", "url": "https://three.ws/api/mcp" }
}
}
Link format from VS Code's MCP developer guide.
IBM Bob reads MCP servers from .bob/mcp.json in your project, or ~/.bob/settings/mcp.json for every workspace. Pick 3D Studio (free) above. It connects with no sign-in for catalog search; to make models, add ?auth=oauth to its URL and Bob's built-in OAuth flow signs you in to your free three.ws account on first connect.
{
"mcpServers": {
"three-ws-main": { "type": "streamable-http", "url": "https://three.ws/api/mcp" }
}
}
- In the Bob panel, open Settings → MCP and click Edit Project MCP (or Edit Global MCP), paste the entry, and save.
- Using Bob Shell? It reads the same files but names the URL key
httpURL, so renameurltohttpURL. Or let the CLI write it:npx three-ws setup --clients bob.
Config format from IBM Bob's MCP docs.
Any client that speaks Streamable HTTP MCP can connect. Clients with OAuth support sign you in automatically from the server's WWW-Authenticate header. Clients without it can send an API key from Dashboard → API as Authorization: Bearer.
{
"mcpServers": {
"three-ws-main": { "type": "http", "url": "https://three.ws/api/mcp" }
}
}
Every hosted server, with its auth and resources, is listed machine-readably at /.well-known/mcp.json.
Worth knowing
You never copy a key
Signing in gives your client its own token for your three.ws account, with the permissions you approved on the consent screen. Tools act on the agents and wallets of the account you sign in with.
Revoke it any time
Every client you connect appears under Dashboard → Settings → Connected apps. Revoking one stops that client on its very next request. Your other clients, your agents and your balances are untouched.
Permissions come in groups
The consent screen groups what a client asked for into Read, Manage, Trade, Spend and Launch, says what each can do and which actions will still ask you first, and lets you untick any group but Read. A client you connect for reading can never trade or move funds. What each group covers.
Every tool is labelled
Each tool declares whether it only reads, writes, or does something irreversible, so your client knows what to ask you about. The tool catalog has a ready-made trust policy to paste in.
Free with an account
The 3D Studio (free) server costs nothing: text to 3D, image to 3D and rigged avatars. Searching the catalog needs no sign-in; making a model needs a free three.ws account, so every model has an owner. New models stay unlisted until you publish them.