--- title: Connect your agents to Materialize with built-in MCP servers description: Materialize now ships two MCP (Model Context Protocol) servers built directly into the database: an agent server (/api/mcp/agent) for querying live data... canonical: https://daily.dev/posts/connect-your-agents-to-materialize-with-built-in-mcp-servers-3ymxljhyl twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Connect your agents to Materialize with built-in MCP servers | daily.dev og:description: Materialize now ships two MCP (Model Context Protocol) servers built directly into the database: an agent server (/api/mcp/agent) for querying live data... og:url: https://daily.dev/posts/connect-your-agents-to-materialize-with-built-in-mcp-servers-3ymxljhyl og:image: https://api.daily.dev/og/posts/3ymXljhyl.png og:image:alt: Connect your agents to Materialize with built-in MCP servers og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Connect your agents to Materialize with built-in MCP servers **[Materialize](https://daily.dev/sources/materialize)** · 8 min read · 1 upvotes · 1 comments ## Summary 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. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I connect Claude Code or Cursor to Materialize using MCP? Materialize exposes two MCP endpoints, /api/mcp/agent and /api/mcp/developer, reachable via OAuth sign-in on Cloud or via an Authorization: Basic header with a Base64-encoded user:password app password for service accounts. Claude Code, Claude Desktop, and Cursor all accept the same URL and header in their JSON config, and any HTTP client can POST to the endpoint directly. _daily.dev surfaces setup details like these for developers wiring agents into live databases._ ### What is the difference between the Materialize agent MCP server and the developer MCP server? The agent server (/api/mcp/agent) exposes data products—materialized views or indexed plain views—so application agents can discover, read, and join live business data such as customers and orders. The developer server (/api/mcp/developer) gives read-only access to system catalog (mz_*) tables via query_system_catalog and query tools, letting a coding agent answer operational questions like why a view is stale or how much memory a cluster uses. _daily.dev helps developers evaluating agent tooling compare how database platforms split these responsibilities._ ### How does Materialize control what an MCP-connected agent is allowed to access? Access is governed entirely by existing SQL grants and RBAC: an agent can only see data products it has SELECT on and only reach clusters it has USAGE on, exactly as with any psql connection. Every MCP tool call runs through the same SQL adapter execution path as a regular statement, so it inherits timestamp selection, strict serializability, and permission errors identical to those returned over psql. _daily.dev tracks security and access-control patterns developers need before granting agents database access._ ## Similar posts on daily.dev - [Building the Live Context Graph for Agents, 28 Weekly Releases Later](https://daily.dev/posts/building-the-live-context-graph-for-agents-28-weekly-releases-later-8loqsdfvj) · Materialize · 1 upvotes · 0 comments - [Playing with Snowflake-managed MCP](https://daily.dev/posts/playing-with-snowflake-managed-mcp-tn6no5rel) · Snowflake Community · 1 upvotes · 0 comments - [Build AI agents faster with GCS \(Google Cloud Storage\) MCP server](https://daily.dev/posts/build-ai-agents-faster-with-gcs-google-cloud-storage-mcp-server-ysjglamng) · Google Cloud · 1 upvotes · 0 comments - [How To Convert Any API to MCP with Zero Code and Zero Deployments Using APIAgent](https://daily.dev/posts/how-to-convert-any-api-to-mcp-with-zero-code-and-zero-deployments-using-apiagent-cafah9jow) · agoda · 1 upvotes · 0 comments --- Tags: [#ai-agents](https://daily.dev/tags/ai-agents), [#backend](https://daily.dev/tags/backend), [#mcp](https://daily.dev/tags/mcp), [#materialize](https://daily.dev/tags/materialize) [View this post on daily.dev](https://daily.dev/posts/connect-your-agents-to-materialize-with-built-in-mcp-servers-3ymxljhyl) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Connect your agents to Materialize with built-in MCP servers","url":"https://daily.dev/posts/connect-your-agents-to-materialize-with-built-in-mcp-servers-3ymxljhyl","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/connect-your-agents-to-materialize-with-built-in-mcp-servers-3ymxljhyl"},"datePublished":"2026-07-22T15:13:46.103Z","dateModified":"2026-09-14T08:03:27.309Z","description":"Materialize now ships two MCP (Model Context Protocol) servers built directly into the database: an agent server (/api/mcp/agent) for querying live data...","image":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","thumbnailUrl":"https://media.daily.dev/image/upload/s--2-1xRawN--/f_auto/v1722860399/public/Placeholder%2011","isAccessibleForFree":true,"articleSection":"Materialize","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Materialize","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/e7a5fc43b12349288c893b502adf599e","url":"https://daily.dev/sources/materialize"},"commentCount":1,"discussionUrl":"https://daily.dev/posts/connect-your-agents-to-materialize-with-built-in-mcp-servers-3ymxljhyl","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":1},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":1}],"keywords":"ai-agents,backend,mcp,materialize","timeRequired":"PT8M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Materialize","item":"https://daily.dev/sources/materialize"},{"@type":"ListItem","position":3,"name":"Connect your agents to Materialize with built-in MCP servers"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/connect-your-agents-to-materialize-with-built-in-mcp-servers-3ymxljhyl#faq","mainEntity":[{"@type":"Question","name":"How do I connect Claude Code or Cursor to Materialize using MCP?","acceptedAnswer":{"@type":"Answer","text":"Materialize exposes two MCP endpoints, /api/mcp/agent and /api/mcp/developer, reachable via OAuth sign-in on Cloud or via an Authorization: Basic header with a Base64-encoded user:password app password for service accounts. Claude Code, Claude Desktop, and Cursor all accept the same URL and header in their JSON config, and any HTTP client can POST to the endpoint directly. daily.dev surfaces setup details like these for developers wiring agents into live databases."}},{"@type":"Question","name":"What is the difference between the Materialize agent MCP server and the developer MCP server?","acceptedAnswer":{"@type":"Answer","text":"The agent server (/api/mcp/agent) exposes data products—materialized views or indexed plain views—so application agents can discover, read, and join live business data such as customers and orders. The developer server (/api/mcp/developer) gives read-only access to system catalog (mz_*) tables via query_system_catalog and query tools, letting a coding agent answer operational questions like why a view is stale or how much memory a cluster uses. daily.dev helps developers evaluating agent tooling compare how database platforms split these responsibilities."}},{"@type":"Question","name":"How does Materialize control what an MCP-connected agent is allowed to access?","acceptedAnswer":{"@type":"Answer","text":"Access is governed entirely by existing SQL grants and RBAC: an agent can only see data products it has SELECT on and only reach clusters it has USAGE on, exactly as with any psql connection. Every MCP tool call runs through the same SQL adapter execution path as a regular statement, so it inherits timestamp selection, strict serializability, and permission errors identical to those returned over psql. daily.dev tracks security and access-control patterns developers need before granting agents database access."}}]} ```