Home  /  Tools and integrations

MCP Servers and agent skills

View as Markdown

Agent skills

Materialize provides the following open-source agent skills to help developers build with Materialize.

Skill Description
mcp-developer-analysis Use for operational introspection and troubleshooting via the materialize-developer server. Covers exact catalog schemas, diagnostic workflows, remediation runbooks, and guardrails for known pitfalls (cluster-scoped queries, uint8 ID mismatches, etc.).

Examples: “why is my materialized view stale?”, “what can I optimize to save costs?”, “is my source healthy?”
materialize-docs Use for authoring view definitions, learning concepts, and looking up patterns; useful with either MCP server. Covers comprehensive Materialize documentation, including SQL syntax, idiomatic patterns, data ingestion, concepts, and best practices (400+ reference files).

Examples: “show me how to deduplicate a stream”, “what’s the idiomatic top-K pattern?”, “how do I create a Kafka source?”
materialize-dbt Use for managing Materialize pipelines with dbt. Covers dbt-materialize adapter usage: materializations, profile configuration, index creation, blue/green deployments, and testing.

Examples: “write a dbt model for a materialized view”, “how do I do a blue/green deployment with dbt?”
materialize-terraform-provider Use for managing Materialize resources declaratively with Terraform. Covers provider configuration for Cloud and self-managed, navigation into the provider’s auto-generated resource reference, cross-resource patterns, import workflows, and gotchas.

Examples: “create a Kafka source with Terraform”, “import my existing clusters into Terraform state”, “set up RBAC grants in Terraform”
materialize-terraform-self-managed Use for deploying or operating self-managed Materialize infrastructure with Terraform. Covers module layout and variables for deploying on AWS, Azure, and GCP: networking, Kubernetes, backend URL formats, instance sizing, upgrades, and gotchas.

Examples: “deploy Materialize on EKS”, “what instance types should Materialize nodes use?”, “upgrade my self-managed Materialize”

MCP servers

Materialize provides built-in Model Context Protocol (MCP) servers that AI agents can use. The MCP interface is served directly by the database; no sidecar process or external server is required. These endpoints use JSON-RPC 2.0 over HTTP POST (default port 6876) and support the MCP initialize, tools/list, and tools/call methods.

Endpoint Path Description
Agent /api/mcp/agent Discover and query your real-time data products over HTTP.
For details, see MCP Server for agents.
Available starting in v26.24
Developer /api/mcp/developer Read mz_* system catalog tables for troubleshooting and observability.
For details, see MCP Server for developer.

See also

Back to top ↑