MCP Clients have their own set of primitives:
- Sampling
- Elicitation
- Logging
MCP Client Primitive Sampling
I need to test this out but it seems there is a sampling/complete method that a server can send to a client, which essentially asks the client to complete a LLM request. The reason for this is seemingly when the MCP server itself doesn’t want to handle a LLM itself … so it passes it off to the client.
MCP Client Primitive Elicitation
There’s also a straightforward elicitation/request method where the server will ask the client for further information from the user.
MCP Client Primitive Logging
Involving debugging and monitoring, servers can send logs to the clients.
Notifications
The protocol also has facility for real-time updates from server to client, in the form of JSON-RPC 2.0 notifications. Nothing super new there.
Leave a Reply