Integrations / Technical

Integrations / Technical

AMBA is the structured hub. Providers feed it. Product APIs and adapters send content to Wanderer's Guide, Owlbear, publishing, and agents. Each system keeps its specialty; AMBA owns IDs, validation, and the adventure graph.

Open Adventure Maker Where it fits

Architecture

Independent systems connected by HTTPS APIs — not shared databases

AMBA's UI is one client of a structured API. Content is normalized into typed artifacts on a module → act → scene → encounter graph, then late-bound to the target ruleset and client. Wanderer's Guide runs as a separate Linux platform (Kong, GoTrue, PostgREST, PostgreSQL). Owlbear is a VTT adapter that translates encounters into a live scene. MCP is a curated hands layer for agents — not raw database access.

AMBA is the structured hub
AMBA is the structured hubBuild from anything. Keep it structured. Send it anywhere.
API-first + late binding
API-first + late bindingProviders normalize into AMBA artifacts; clients consume a stable graph and IDs.
Wanderer's Guide is a separate platform
Wanderer's Guide is a separate platformAMBA integrates with WG over HTTPS/API. Multiple clients share the same WG backend.
WGUI changes the human interaction model
WGUI changes the human interaction modelSame WG rules foundation; WGUI reorganizes play around workspaces.
Owlbear is a VTT adapter
Owlbear is a VTT adapterAMBA owns content; Owlbear owns the live scene; the extension translates between them.
AMBA MCP server — agent control plane
AMBA MCP server — agent control planeAgents use named tools. AMBA remains the source of truth.
Data flow, deployment, and shared identity
Data flow, deployment, and shared identityIdeas to table; three systems over TLS; WG auth and permissions propagate to AMBA.
Round-trip play and data ownership
Round-trip play and data ownershipGenerate, assemble, run, capture state, publish — each platform keeps its specialty.
Adventure graph, lifecycle, and hosting
Adventure graph, lifecycle, and hostingTyped structure, round-trip feedback, Node/Express + WG Supabase stack over HTTPS.

MCP is the curated hands layer

Agents operate AMBA through product APIs. AMBA still owns IDs, validation, persistence, and publishing safety. The same contract feeds Wanderer's Guide, Owlbear, PDF, and syndication.

Stable IDs. API contracts. No shared database.

Open Adventure Maker