Skip to content
LLM Semantic Layer Engine

Put a governed semantic engine between AI and business data.

Foggy Data MCP turns AI analysis requests into model-aware, permission-aware, executable query workflows using TM/QM semantic models, JSON Query DSL, MCP tools, and query evidence.

Semantic ModelsStructured DSLPermission InjectionQuery Evidence
Foggy Data MCP logoSemantic Query Consolegoverned
MODELSalesAnalysisQM

customer · product · orderDate · salesAmount

fieldvisibilitycustomer$captionallowedgrossMarginallowedraw_cost_colhidden
DSL
{ "model": "SalesAnalysisQM", "columns": ["brand", "sum(salesAmount)"], "filters": [{"field": "orderDate", "op": ">=", "value": "2026-01-01"}], "orderBy": [{"field": "salesAmount", "dir": "DESC"}]}
list_modelsdescribe_modelquery_modelevidence
TM/QMSemantic model boundary
JSON DSLStructured query contract
MCPAI tool access layer
Java / PythonTwo implementation paths

The issue is not whether an LLM can write SQL. It is whether SQL is the right AI contract.

Raw SQL prompts expose schema details, blur permission boundaries, and force business metrics into fragile prompt text. Foggy moves those responsibilities into semantic models and the query engine, so AI works through governed business fields instead of ad hoc database internals.

Direct SQL Promptschema leakage, dialect fragility, permission drift, ambiguous metrics
Foggy Contractmodel discovery, field validation, permission injection, engine-generated SQL, query evidence

A governed analysis workflow from AI request to query evidence.

The v1.0 whitepaper is frozen as the current public contract.

The current public release documents implemented and verified semantic modeling, DSL query, compose analysis, governance, and evidence capabilities. Future capabilities stay in later versions and roadmap documents.