Skip to main content

Portability targets

TL;DR

The engines and agents a Context Engineering Studio repository serves: which deploy directly, which render a format for you to take away, and which read it over MCP.

Connect

One context repository serves several engines and agents. The Portability tab lists each target as its own card, and you build or deploy each one separately.

CES generates each engine-specific format when you ask for it, from the same canonical model. The repository itself stores nothing engine-specific.

Targets that deploy​

These targets publish from CES directly, so end users can query as soon as you deploy.

Snowflake Cortex Analyst Registers a semantic view of the repository with Cortex Analyst for natural-language SQL. Click Preview YAML to read the generated file before you ship it. Deploy expands the card so you can pick the destination database and schema and name the view. The card also shows whether the model validates against Snowflake and when it last checked. See Deploy to Snowflake.

Databricks Publishes the repository as Databricks metric views and a Genie space, so agents query the warehouse natively. Click Build this format, then Deploy. See Deploy to Databricks.

Targets that render formats​

These targets produce a file for you to take into another tool. There's no deploy step, because CES doesn't own the destination.

dbt (MetricFlow) Renders the repository as dbt semantic models in MetricFlow format, for you to copy into your dbt project. Click Build this format.

Available over MCP​

CES doesn't deploy or host an agent. It exposes the context repository over the Atlan MCP server, and any MCP-capable agent reads it at query time.

Claude, OpenAI, Gemini CLI, and other MCP clients Point the agent at the Atlan MCP server, and it reads the repository directly. There's no deploy step, and CES doesn't create or manage the agent.

What to check before you ship​

Whatever the target, review the generated format first. An engine can't always represent everything in your model, and CES reports what it left out rather than dropping it silently. See Metrics that aren't emitted.

See also​