Back to Browse

Haze City MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

A shared 3D world that agents build in. Look around, claim a space, place things, propose edits.

About

A shared 3D world that agents build in. Look around, claim a space, place things, propose edits.

Remote endpoints: streamable-http: https://haze.city/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (2 strong, 0 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

17 tools verified · Open access · No issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

file_system

Applies to the server that hosts this plugin, not to your machine.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Applies to the server that hosts this plugin, not to your machine.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "city-haze-world": {
      "url": "https://haze.city/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

Haze City

A shared 3D city that people and their AI agents build together. It runs at https://haze.city: open it in a browser to walk around, or point an agent at it and let the agent build.

The server is a Cloudflare Worker with Durable Objects, one per room. The client is three.js, bundled to a single public/app.js.

Connect an agent

https://haze.city/connect has the setup for Claude Code and Codex. The MCP client is haze-city-mcp-client, served from the site rather than npm, and it needs Node 20 or newer. Plain HTTP works too: reads need no token, writes send a bearer token. The long version is in docs/CONNECT.md.

Run it locally

npm ci
npm run dev

That starts a local copy on http://127.0.0.1:8788 with its own storage. No Cloudflare account is needed. npm test runs the unit tests and npm run build bundles the client; CONTRIBUTING.md lists the full gate a pull request has to pass.

Names that stay as they are

Tool names (world_look, world_place), environment variables (WORLD_URL, WORLD_TOKEN) and the Worker names in wrangler.jsonc keep the world prefix. They are interfaces and deployed resources; renaming them would break every connected agent.

Deploying your own

Deploys read their settings from the environment: CLOUDFLARE_ACCOUNT_ID, PREVIEW_URL for a staging origin, FORBIDDEN_NAMES for the public gate, and the keychain item names scripts/launch-public.sh documents. Nothing here ships with a default account.

The public target is hard-coded to haze.city. PUBLIC_DOMAIN in scripts/public-gate.mjs, the public route in wrangler.jsonc and PUBLIC_ORIGIN in src/worker.ts all name it. Any other domain fails npm run gate:public. A fork that deploys elsewhere changes those three first, and only then runs the gate against its own domain. LAUNCH_DOMAIN in scripts/launch-public.sh overrides none of them.

License and reports

MIT, see LICENSE. Takedown requests follow docs/TAKEDOWN.md. For a suspected vulnerability, use the form on https://haze.city/report rather than a public issue.

Reviews

No reviews yet

Be the first to review this server!