mz-developer-analysis
Materialize Developer Analysis
Analyze a Materialize environment by querying system catalog tables via the MCP
Developer endpoint (query_system_catalog tool), and produce a structured
report with health status, performance findings, and optimization recommendations.
Discovering Tables and Columns
Do NOT guess column names. Before writing queries, check if the mz_ontology
schema is available by running:
SHOW TABLES FROM mz_ontology
If mz_ontology is available
Use it to discover the correct tables, columns, join paths, and ID types:
More from materializeinc/agent-skills
materialize-docs
Materialize documentation for SQL syntax, data ingestion, concepts, and best practices. Use when users ask about Materialize queries, sources, sinks, views, or clusters.
134mcp-developer-analysis
Analyze a Materialize environment via the MCP Developer endpoint, and/or configure an MCP client (Claude Code, Cursor, VS Code, Zed, Continue, Windsurf, Claude Desktop) to connect to the materialize-developer server. For analysis: check environment health, investigate performance, troubleshoot stale materialized views, diagnose memory pressure, audit resource utilization, get optimization recommendations. For client connection: configure/connect/set-up an MCP client to materialize-developer (Emulator, Cloud, or self-managed), control which user/role is used, switch between identities. Trigger even if user just says "check my environment", "why is my MV stale", "why is my cluster slow", "what can I optimize", "how do I connect Claude Code to materialize-developer", or "configure Cursor for the Materialize MCP".
25