World Builder ONE

AI Automation with Model Context Protocol (MCP)

Written by

World Builder ONE Team

in

World Builder Pro introduces native support for the Model Context Protocol (MCP)—an open standard created by Anthropic that allows AI assistants to safely interact with local development applications.

How MCP Works in World Builder

World Builder runs a lightweight, local MCP server. When you connect an external AI assistant (such as Claude Desktop, Antigravity, or Cursor), the assistant gains the ability to call World Builder’s internal authoring tools on your command.

Connecting Claude Desktop to World Builder

To connect Claude Desktop to your local World Builder session, add the following configuration to your claude_desktop_config.json file:

{
  "mcpServers": {
    "world-builder": {
      "command": "/Applications/World Builder.app/Contents/MacOS/World Builder",
      "args": ["--mcp-server"]
    }
  }
}

Core MCP Tool Actions

Once connected, your AI assistant can execute commands across all major studio subsystems:

  • create_landmark: Procedurally generates a textured 3D OBJ8 model from architectural parameters and inserts it into your DSF overlay.
  • download_osm & build_osm_overlays: Queries OpenStreetMap boundaries, extracts building footprints and road networks, and compiles autogen town zones.
  • audit_airport: Scans runways, taxiways, and ramp starts for coordinate disconnects and Gateway compliance.
  • build_pack: Triggers the incremental build pipeline, validates textures, and produces an exportable pack.

Creating Custom Reusable Skills

Advanced developers can chain multiple MCP tools into repeatable scripts or “skills” (for example, automating an entire regional island scenery pipeline). The AI executes the steps sequentially, reporting progress and handling validation errors automatically.

More posts