Serve
Agents & MCP
Give agents the context they need to act correctly — and nothing else. The MCP server reads from the context layer; the warehouse is never in the loop.
No direct warehouse access
Agents never run DDL discovery against production. They ask the MCP server, which answers from the last sync.
Business meaning included
Answers carry annotations — grain, partition keys, PII flags, owners — not just column names and types.
Freshness you can verify
Every response includes a last-synced timestamp. If the context is stale, the agent knows, and so do you.
Works with your clients
Claude, Cursor, Copilot, your own agents.
Anything that speaks MCP can connect. Point your client at the AZ Data server, grant it the projects it should see, and it can answer "what changed in this table and why" against real DDL history.
- Per-project scoping — an agent sees only the schemas you allow
- Structured tool results, not pasted Markdown
- Audit log of every question an agent asked
Connect an agent in the demo.
We'll wire Claude Code to the MCP server live and ask it about a table that changed a minute earlier.