Materialize now ships two MCP (Model Context Protocol) servers built directly into the database: an agent server (/api/mcp/agent) for querying live data products, and a developer server (/api/mcp/developer) for inspecting the system catalog. Both run inside the database's HTTP layer, speak JSON-RPC 2.0, and enforce the same RBAC and strict serializability as regular SQL connections. The agent server exposes materialized views and indexed views as discoverable data products with schema metadata, enabling AI agents to query consistent, live business state. The developer server provides read-only access to mz_* catalog tables for operational queries about cluster memory, view staleness, and resource usage. Authentication supports OAuth and token-based Basic auth. The servers are available on Cloud, Self-Managed, and the local Emulator.
Table of contents
Two servers, two jobsWhat the agent server exposesWhat the developer server answersConnecting a clientSelf-managed and the EmulatorGet started1.4K Impressions1 Comment