MCP layers
Understand the data and transport layers used by Data Product MCP.
MCP separates message meaning from message transport.
The two layers
Data layer
The JSON-RPC message model, lifecycle, capability negotiation, requests, responses, notifications, errors, tools, resources, and prompts.
The client sends a tools/call request with structured arguments for the selected tool. The server returns a structured result or error.
Transport layer
The communication channel that carries MCP messages between the client and server.
A desktop assistant may connect to a local MCP process. A hosted assistant may connect to Data Product MCP over HTTP.
The data layer defines what the client and server are saying. The transport layer defines how those messages move.
Why this separation matters
This split keeps protocol behavior stable across different connection types.
It also lets Data Product MCP support different host environments without changing tool semantics. A local assistant and a hosted assistant can call the same tools and receive the same response shape, even if they connect differently.
Last updated
Was this helpful?