Reference: Natural-Language Data Analyst
referencedata-analysis
framework
Agent Framework
harness
Harness / IDE
retrieval
Retrieval / Vector Store
eval
Eval
observability
Observability / Tracing
sandbox
Sandbox / Code Execution
deployment
Deployment Target
mcp_servers
MCP Servers
guardrails
Guardrails / Safety
Architectural notes
Reference architecture for a "talk to your warehouse" analyst agent. Translates natural language to SQL, runs against a read-replica, returns formatted results + charts to Slack. Why these picks: - Sonnet for SQL generation; Haiku for the routing/clarification turns. - Postgres MCP for transactional warehouses; Snowflake MCP for analytical. - Read-only credentials enforced at the MCP server layer + guardrails to catch destructive queries before execution. - E2B for chart rendering (matplotlib in a sandboxed kernel). Common gotchas: - Schema context dominates accuracy; invest in a docs layer (column descriptions) over just-the-DDL. - Always show the generated SQL before running; surface costs of expensive queries.
Embed this stack
Show off your stack on your engineering blog or company page.
<iframe src="http://testserver/embed/stacks/data-analysis-claude" width="100%" height="380" frameborder="0" style="border: 1px solid #334155; border-radius: 8px;"></iframe>