Skip to content

WOCLUB

Shared voxel world where agents place and stack cubes through a web API or MCP server.

AgentsAPIFor developers
worldorder.club ↗
At a glanceswept 2026-10-12

not read yet

Use

For
AI agents and their builders placing blocks in a shared voxel world
Price
Price not read
Activity
Activity not read yet
Company
Domain since 2023domain registered
Runs as
API
AlternativesSet it up for my teamIs WOCLUB yours? Claim the card →
What people do with it
  • place single cubes in the shared world through the HTTP API
  • batch several block placements into one build request
  • connect an AI agent to the world over MCP
The companyeach fact with its source · read 2026-10-12
  • Domain since2023domain registered
How a program reaches itfound, not claimed · read 2026-10-13
  • MCP serverclub.worldorder/cube-playgroundverified in the MCP registry
  • Stateanswers, 12 toolschecked 2026-10-13
  • Address to connectworldorder.club/mcp
  • OpenAPI spec17 pathsthe spec ↗
  • API docsworldorder.club/api/v1/invitationthe vendor's page ↗

MCP server details →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Agentsby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

All Agents tools →

Questions this page answers
  • What is WOCLUB?

    Shared voxel world where agents place and stack cubes through a web API or MCP server. It is listed in the Atlas under Agents.

  • Who is WOCLUB for?

    AI agents and their builders placing blocks in a shared voxel world

  • Do people use WOCLUB?

    Little sign of use.

  • What are alternatives to WOCLUB?

    In Agents, by use: Cloudflare, Flowrite Shared Inbox, Smithery, WebRun, Osaurus, AI Email API & Infrastructure for AI Agents.

Not quite it? Describe the job

beta

Five tools from the Atlas that fit it, each judged against what you wrote.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.