MCP Servers and agent skills
View as MarkdownAgent skills
Materialize provides open-source agent skills that give coding agents like Claude Code, Codex, and Cursor access to Materialize documentation and reference material. For the list of available skills and installation instructions, see Agent Skills.
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 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, and run queries on your objects. For details, see MCP Server for developer. Available starting in v26.20 |
Protocol versions
The MCP servers support MCP protocol versions 2025-11-25 and 2026-07-28, and pick the version for each request:
- 2025-11-25: The client starts with
initialize. Requests need no extra headers. A request without anMCP-Protocol-Versionheader is served as 2025-11-25. - 2026-07-28: Available starting in v26.48, on by default starting in
v26.50. There is no
initializestep. Each request carries the protocol version, and the client can callserver/discoverto see the supported versions. Atools/callrequest also needs anMcp-Nameheader that matches the tool name. See the specification for the required headers.
MCP clients pick the version. A client that supports both can try 2026-07-28
first and fall back to 2025-11-25. For example, a 2026-07-28 tools/list
request:
curl -X POST http://localhost:6876/api/mcp/developer \
-H "Content-Type: application/json" \
-H "MCP-Protocol-Version: 2026-07-28" \
-H "Mcp-Method: tools/list" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/list",
"params": {
"_meta": {
"io.modelcontextprotocol/protocolVersion": "2026-07-28",
"io.modelcontextprotocol/clientCapabilities": {}
}
}
}'
See also
- Use an ontology table to curate join
relationships that agents query through the
querytool before writing multi-table SQL. - MCP Server Troubleshooting