Skip to main content
Community Hub
TL;DR

Assemble, test, and ship the business context every AI agent needs to produce accurate, trustworthy answers.

Your AI can read this via Docs MCPInstall MCP →Connect

Context Engineering Studio

Context Engineering Studio is where you build context repositories. A context repository is the canonical definition of what your data means, scoped to one use case: a portable semantic layer (the metrics, dimensions, relationships, and rules that define your data) that references the Atlan assets it's built from and publishes to each engine in the format that engine expects.

  • Deterministic and governed. Every linked asset points back to its governed source rather than being copied, so the same context produces the same repository and stays governed at its source.
  • Tested before it ships. Run a generated question set against the repository and read the per-question failures before business users see them.
  • One repository, many engines. Snowflake Cortex Analyst, Databricks Genie, dbt, and Claude each read the same model, generated on demand with a review step before you ship.
SALES_PIPELINE
Context repository
Active
Semantic modelStructuredRaw
sales_pipeline

Deal-level pipeline snapshot, one row per opportunity per day.

Dimensions10
Time dimensions3
Facts3
Derived metrics57 not emitted10
Linked assets 4
SALES_PIPELINETable · SALES_DB · PIPELINEReference
OpportunityTerm · Sales glossaryReference
PipelineTerm · Sales glossaryReference
Sales PipelineTerm · Sales glossaryReference
4 linked assets10 derived metrics4 targets