Get Started
Bardo Documentation
Start with local install, client connection, MCP surface, runtime skills, and workspace-driven mechanics.
Bardo keeps the public docs intentionally product-focused. This section exists to help you install the bridge, connect a client, understand where campaign truth lives, and see how the current MCP surface, runtime skills, and ruleset mechanics fit together without turning the docs into a second dashboard.
What Bardo covers
- Install the local bridge with the published shell scripts.
- Connect an MCP-capable client to your local workspace.
- Understand where campaign truth lives and where it does not.
- Discover the trusted-copilot MCP surface, including mechanics and planning tools.
- Understand how uploaded rulesets, runtime skills, and table-decision nodes shape behavior.
Recommended path
- Install the bridge on the machine where your campaign files live.
- Connect your preferred AI client and approve the browser session.
- Use the campaign truth model as the mental boundary for local versus hosted behavior.
- Review the MCP surface and ruleset mechanics pages before designing a workflow around custom rules.
- Open the billing page only when you need subscription or usage details.
What stays outside docs
The dashboard, Clerk authentication flows, bridge approval polling, billing actions, and API routes stay server-backed. The docs remain static on purpose so they load fast, stay searchable, and describe the stable public product boundary rather than every internal implementation detail.