Integrations¶
dbt Charts provides integrations for embedding rendered boards and charts directly in external documentation and publishing tools.
Available Integrations¶
| Integration | Status | Description |
|---|---|---|
| Markdown | Supported | Draw charts fences, with hover tooltips, in any Python-Markdown site (MkDocs, Pelican) with one line of config |
| Static sites | Supported | Hugo, Jekyll, Astro, Docusaurus and GitHub READMEs: dct render --format md swaps each fence for an SVG image; dct runtime-js adds hover to inline SVG |
| Streamlit | Supported | Embed a board in a Streamlit app. Streamlit in Snowflake is not yet verified |
| Sphinx | Planned | Directive for reStructuredText / Sphinx projects |
Fivetran Agent Context¶
An agent that authors boards through the dbt Charts MCP server knows the board language, not what your warehouse means. Fivetran Agent Context, a separate MCP server that is in Public Preview and needs access from your Fivetran account admin, can give the agent that warehouse context. You add it to your client beside the dbt Charts server; dbt Charts does not install or configure it. See Add Fivetran Agent Context beside dbt Charts for the setup command.
Architecture¶
Integrations render through the same project session API
(dbt_charts.agent_api.ProjectSession). ProjectSession.render_board()
handles the full compile-execute-render pipeline and returns a typed
envelope carrying embeddable output (SVG, HTML, PNG, or PDF). Each
integration is a thin adapter that:
- Detects embed blocks or directives in the host tool's source format
- Resolves the board file (or its raw YAML) relative to the project
- Opens a
ProjectSessionand callsrender_board()to get rendered output - Injects the output into the host tool's build pipeline
This keeps the core dbt Charts architecture undistorted by any single platform's conventions. See Markdown for a worked example.