THE CHALLENGE
A coding agent reads the schema, finds a column called revenue, joins it to something plausible and hands back SQL that runs. Working SQL looks the same whether the definition behind it is yours or improvised, so a reviewer can’t tell.
PARTNERS / SPACEX Super Intelligence / GROK
AtScale has joined the SpaceXSI Partner Network as a Marketplace Partner. With the AtScale plugin for Grok Build, Grok connects to AtScale over MCP and asks for the metrics Finance has signed off on. You keep the same agent and the same speed, and the figure it returns matches the finance report.
THE CHALLENGE
A coding agent reads the schema, finds a column called revenue, joins it to something plausible and hands back SQL that runs. Working SQL looks the same whether the definition behind it is yours or improvised, so a reviewer can’t tell.
WHAT YOU GET
Grok reads metrics, dimensions and hierarchies from your semantic model, checks which metric you meant and gets back a number AtScale ACE computed from the definition Finance uses.
SEE IT IN THE TERMINAL
Without that step, the question returns one number and no sign the other four existed. The answer looks finished, so nobody’s likely to check it.
WHAT IT DOES
The tenure rule, the exclusion list, the fiscal calendar and the reason Finance uses a different column aren’t in the schema. An agent that’s reading tables has to guess at every one of them.
With AtScale, it doesn’t have to. Grok connects to AtScale’s Model Context Protocol (MCP) server and reads the metrics, dimensions, hierarchies, relationships and access rules you’ve defined. ACE (the AI Computation Engine) computes each metric where the data already sits, so it’s the same value Finance published.
HOW IT CONNECTS
MORE WAYS TO USE IT
A definition change arrives as a pull request instead of a ticket.
Your product reads the same numbers your finance team reports.
The agent and the analyst use one definition.
A Bot your sales team runs reads the same definitions your code does.
Run the old definition beside the new one and see which reports move.
Every change to a metric has an author, a review and a date.
PROOF
FAQ
Through AtScale’s MCP server. You add it to Grok Build’s MCP configuration and sign in as yourself with OAuth, so your access rules apply to the agent the same way they apply to you. The MCP tools are read-only.
Yes. The same MCP server works in Cursor, so teams moving to Grok Build keep the same setup.
Not for metrics. ACE (the AI Computation Engine) computes each metric from the definition in your model and runs the SQL itself. You can read the query it used.
Ava checks which one you meant. If your model has five kinds of revenue, Ava finds all five and confirms the one you need, like recognized revenue for the quarterly report, before ACE computes it.
Snowflake, Databricks, Google BigQuery, Amazon Redshift, PostgreSQL and InterSystems IRIS. Self-hosted AtScale also runs on Microsoft SQL Server, Azure SQL, Azure Synapse, Cloudera CDP and IBM Db2. ACE computes on the platform you already run, so your data doesn’t move.
Any client that supports remote MCP servers. That includes Claude, ChatGPT, Google Gemini and Databricks agents alongside Grok Build, and they all request the same metric definitions.