mcp-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.
Connecting an MCP client to materialize-developer
If the user is asking how to configure, connect, or set up an MCP
client (Claude Code, Cursor, VS Code, Zed, Continue, Windsurf, Claude Desktop)
to talk to the materialize-developer server — including how to control which
user or role the connection uses, or how to switch between identities — see
mcp-client-connect.md. It covers the Emulator,
Materialize Cloud, and self-managed deployments, with per-client snippets,
authentication patterns, and verification recipes.
The rest of this SKILL.md covers what to do once you are connected and want
to analyze the environment.
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.
134mz-developer-analysis
Analyze a Materialize environment for health, performance, and optimization opportunities using the MCP Developer endpoint. Use this skill when someone wants to check environment health, investigate performance issues, troubleshoot stale materialized views, diagnose memory pressure, audit resource utilization, or get optimization recommendations. Trigger this even if the user just says "check my environment", "why is my MV stale", "why is my cluster slow", or "what can I optimize".
5