Talos3D

Authored 3D platform

Toward AI-readable design models.

Talos3D keeps authored entities, commands, relationships, and capability metadata visible in the model. Recent work adds first steps toward semantic assemblies and typed relations, so structures such as rooms, storeys, or houses can be described directly instead of reconstructed from meshes alone.

Authored model Semantic assemblies MCP model API
Explore the repo Read the model API 
cargo run --features model-api

# MCP over HTTP
http://127.0.0.1:24842/mcp

# current semantic tools
list_vocabulary
create_assembly
query_relations
Rust + Bevy + MCP

Source of truth

Authored geometry first

Meshes, previews, highlights, and caches are derived artifacts. The actual model keeps domain meaning visible to both users and tooling.

First semantic step

Assemblies and relations

The model now has a first layer for higher-order structure: authored assemblies, typed relations, and capability-defined vocabulary for domain concepts above individual solids.

Extension boundary

Capabilities, not silos

Modeling, architecture, terrain, and future domains compose on the same platform contracts, which keeps open, private, and domain-specific extensions on the same basic footing.

Current interface

MCP is a public interface.

Talos3D exposes a structured Model Context Protocol endpoint so external clients can inspect authored entities, discover capability vocabulary, capture summaries, and apply authored edits through the same command/history pipeline used by the UI.

Discover

  • list_vocabulary
  • list_entities
  • model_summary

Structure

  • list_assemblies
  • get_assembly
  • query_relations

Write

  • create_entity
  • create_assembly
  • set_entity_property

Current state

A public platform taking some good first steps.

The public codebase already includes a Rust + Bevy core, capability-based setup registration, modeling primitives, architectural elements, terrain workflows, semantic summaries, and an MCP-backed model API. Recent work adds a first semantic assembly layer. We think it is a fruitful direction, but it is still early.

Current scope

Primitives, transforms, groups, face editing, walls, openings, terrain, semantic assemblies, and typed relations.

Integration story

HTTP or stdio MCP, capability vocabulary, public docs, and one shared command/history substrate.

Project posture

Open platform core with room for private and domain-specific extensions. The direction is broader than the current implementation.